UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

CLI

CLI changelog

What changed in each release of the Ulika CLI, newest first, from 0.7.1 back to 0.1.0.

Last updated November 5, 2026

Release notes for the Ulika CLI, newest first. Each version is the one in the CLI's own package.json; ulika --version prints it. Dates are when the release was committed. The CLI is served by Ulika itself, so a new version is available as soon as it ships; use the versioned address (https://ulika.co/cli/ulika-cli-<version>.tgz) to pin one, and see the CLI reference for everything it can do now. Versions 0.4.x, 0.5.0 and 0.5.1 were never released: the number went from 0.3.1 straight to 0.5.2.

0.7.1 (2026-11-05)#

  • Every connect mode ends on one mapping from the final summary status to the exit code: 0 live, 20 needs a person or still verifying, 21 failed, 26 framework refused. A command that returned no exit code at all now exits 1 instead of a silent 0. The one outcome that used to end 0 without anything connected, the "finish in your browser" handoff (Ulika could not resolve the site's source on this machine), now exits 20 in the terminal and with --json. No new exit code was added.

  • A production build that fails after the connector is merged is worded by what happened. When Ulika reverted its change the attention is production-build-failed and links the revert pull request. When no revert exists (Ulika could not make one, a connector file was edited after the merge, or a person made the merge) it is production-revert-failed: it says Ulika could not revert the connector, that production builds keep failing until it is removed, and links the install pull request as the install pull request, never as a revert. production-proof-missing is no longer used for a failed production build.

  • Before you activate, connect warns when the Production environment has variables the Preview environment lacks, naming them (names only, never values), because then the preview build cannot prove the production build. It is a warning, not a block. With --auto-merge it rides on the preview built event (envWarning in --json), before Ulika merges. It is not shown on the dashboard Activate button.

0.7.0 (2026-11-04)#

Behavior change. connect no longer waits when nobody can click: with no terminal on stdout or stdin (a pipe, an agent harness, CI) it does not wait for the first approval and it does not wait for Activate. Before, such a run sat for up to 15 minutes and looked hung. Scripts that relied on that wait must pass the new --wait.

  • Without a terminal, connect prints the approval link and exits 22 at once (it used to poll for 15 minutes), and once approved it prints the state and the Ulika Activate link (including reusing PR #N (connector X, ...)) and exits by the report: 0 when a site is live, 20 while a person has to act or while a merged site is still being verified, 21 or 26 as before. Exit 20 also covers "still verifying": the report says nothing is needed from you and to run the same command again in a few minutes. No new exit code was added.

  • New --wait keeps both waits without a terminal. --no-wait still never waits, and --wait together with --no-wait is a usage error (exit 2). Single-site connect refuses --wait, like --no-wait, because it never waits.

  • --no-browser only stops the approval page from opening. It does not change whether the run waits, so someone at a real terminal over SSH still waits for Activate.

  • When Ulika cannot tell which repository builds a site, each repository it names now says why: homepage is <host>, description names the site, ulika.config.json declares <host>, its production deployment is on <host>, or index.html declares <host> as its address when the repository's entry page declares the site's address (canonical link, og:url or twitter:url). A plain link to the site never counts. Candidates are ordered by strength of evidence (config or deployment, then homepage, then description, then address in the code) before the list is cut to four. A repository is never named for how it is called: a name alone is not evidence, so another client's similarly named repository is no longer offered. Reading entry pages is bounded (at most 15 repositories, four reads at a time, remembered for five minutes, never a clone) and only used to suggest, never to choose.

0.6.17 (2026-10-31)#

  • connect now delivers the source-build connector's latest build runtime to sites that already have it installed. The build summary line and the public/cms cleanup shipped in 0.6.16 never reached an installed site, because no recorded connector version moved: connect kept reporting reusing PR #2 (connector 1.2.0, no changes). Source-build connectors (Vite, Create React App and other Node-built sites) are now version 1.2.2. A connector recorded at 1.2.0 whose open pull request is Ulika's own and untouched is replaced the same way as before (the new pull request opens first, then the old one is closed, nothing is merged); a pull request someone reviewed, commented on or changed is left alone and the output says 1.2.2 was not applied. Next.js runtime connectors stay on 1.2.0 and are not upgraded.

  • A reused pull request that already holds the latest connector now says so: reusing PR #2 (connector 1.2.2, already the latest). The site.pr_open event carries upToDate: true in that case, and an older server that sends no such field keeps no changes.

  • ulika preview no longer ends a run it could not prove with nothing to act on. An unproven or failed preview always prints the pushed branch name and commit SHA (Branch: ulika/preview-2eacd242 at commit <sha>) and the branch page, labels any preview address (not verified), and never claims a pass. When the reason is that Ulika's GitHub app has not been given read access to commit statuses, checks or deployments, it prints the permissions page of that exact installation (your account or your organization) and asks you to run ulika preview again after accepting. --json adds branch, commitSha, previewVerified: false next to a previewUrl, and permissionsUrl with missingPermissions when that applies. Exit codes (0, 30, 31, 32, 2) are unchanged. When Ulika cannot read the host's builds it now names the real cause from the installation's live permissions rather than a generic line: the reads are not yet accepted (with the link above), Ulika's app does not request them, or several Vercel projects report on the commit and none is known to be the site's (connecting Vercel resolves that). Vercel is never presented as required for this, because GitHub's own statuses, checks and deployments are enough.

  • connect no longer says "Previews will not be verified automatically" when Ulika's GitHub app can read commit statuses, checks and deployments. With those reads granted, the missing-Vercel notice says previews are verified through GitHub and Vercel is optional (it only helps Ulika prepare the host, or tell apart several Vercel projects built from one repository). Without them it links to the permissions page of that installation.

  • connect exit code 20 is documented as "waiting for you", not an error: most often Ulika is waiting for you to merge the connector pull request, which the report links. Run the same command again after you act.

0.6.16 (2026-10-31)#

  • New ulika preview <url> --yes: builds the site's current draft on a branch of its own and prints the preview address once Ulika has read the draft back from it. It asks for --yes because the draft is unpublished content: it is committed to a branch of the site's repository and stays in that repository's git history, so if the repository is public anyone can read it. Without --yes it sends nothing, prints what would happen and exits 2. The server refuses a request without acknowledgeDraftPush: true (409), reports whether the repository is public or private, and the command prints a loud warning when it is public. The push also triggers the repository's own push workflows (CI, and any deploy that runs on every branch); the default branch is not touched. It commits the draft content (the same one-file commit a publish makes) to ulika/preview-<id>, one branch per project that is reused on every run, never to the default branch. It opens no pull request, finalizes no draft and creates no release, so nothing it does counts as published. For a site whose connector is still an open pull request the preview is built on top of the connector branch. It works on a site that is already connected and delivers content through git. It uses the sign-in ulika login gives (or ULIKA_TOKEN), never an agent approval, because an agent may connect sites but not read drafts or publish; without that sign-in it exits 11 and starts none. Your role must be allowed to publish and the project must be one you can reach. It reports verified only when the preview serves exactly this draft. A private preview that built, a build nobody can observe (no hosting connection, or no permission to read statuses) and a wait that ran out are reported as not proven, with the branch link and without claiming a pass (exit 30); a failed build exits 31 with the deployment link; a site it cannot preview exits 32, including a draft the editor would not let you publish (for example a collection below its minimum, reported with the editor's own sentence), a connector pull request that was closed or undone, and a base branch that no longer exists. --wait-timeout <min> sets how long to wait for the build (default 10).

  • connect no longer says it saved changes on a branch or opened a pull request when it did neither. A run that walks the steps again over an open, unchanged pull request used to print "changes saved on a branch" and "pull request opened" and then "Review and merge PR #N", with no new branch and no new commit. Each step now says what happened on GitHub: pushed a commit to a new branch, reusing the existing branch, nothing pushed, opened PR #N, reusing PR #N (connector X, no changes), or closed its outdated pull request #N and pushed a new commit. The site.committed and site.pr_open events carry outcome (created, reused or replaced on the first; opened or reused on the second), connectorVersion, and when relevant replacedPull and newerAvailable. An older server that sends no outcome keeps the old generic words.

  • An open connector pull request written at an older connector version is replaced, by connect and by connect --all alike, only when it is the source-build connector's own pull request and nobody has acted on it: Ulika opened it, nobody reviewed or commented, nobody is asked to review or assigned, auto-merge is off and it is not in the merge queue. Ulika writes the new connector and opens the new pull request first, and only then closes the old one (nothing is merged), with a comment that names the new pull request and links to it. If writing the new connector fails, the old pull request stays open, exactly as it was, and the error says so. In every other case (another adapter, someone touched it or is expected to) the old pull request is left as it is and the output says a newer connector was not applied; when the old one cannot be closed after the new one opens, the output names it so you can close it.

  • connect prints the verified preview link of the connector pull request before you run --activate, once Vercel built it and Ulika read the connector proof off it. init and local connect also report it as result.previewUrl in --json.

  • The connector's build now prints one summary line (bindings applied, revision, manifest verdict, sources restored), with no content values, and leaves the working tree as it found it: files and folders the build created under public/ are removed again, and anything that already existed is restored byte for byte. A server-rendered site keeps public/cms because its host serves public/ directly, and the cleanup skips when the output folder is or contains public/.

  • The MCP tool connect_site no longer dead-ends when a machine has an agent approval but no workspace token for the server (the approval connect and connect_sites mint, versus the workspace token that ulika login and an interactive ulika init mint). When the caller passes url, it now connects that site by URL through connect_sites (the local checkout is not used), so the agent can continue with batch_status. A URL inferred from the project is only offered as a suggestion to confirm with the user, never used on its own. It never starts a device flow. Without url, or with importOnly, activate or dryRun, which that path cannot honour, the error says to call connect_sites with the site's URL instead of sending the user to ulika login. With neither credential the instruction stays, and now names the server and the connect_sites alternative.

  • The server description of connect_site named no environment variable ("Defaults to or https://ulika.co."). It now reads Defaults to $ULIKA_SERVER or https://ulika.co.

  • ulika whoami now says which credentials exist for the server (workspace token and agent approval, never their values) and which other servers hold credentials (at most five), and --json adds workspaceToken, agentApproval and otherServers. A machine with only an agent approval is told why local init and the MCP connect_site import are not authorised.

  • connect --dry-run without an approval no longer tells you to run ulika login (that mints a workspace token, not the approval a dry run needs); it says to run connect <url> --no-wait, approve the link, and notes that this is a real connect (approving lets Ulika open the connector pull request).

0.6.15 (2026-10-26)#

  • connect no longer says "preview built" when the preview build failed or could not be seen. A failed build ends with failed: the preview build failed, the deployment link and, in a terminal, the last lines of the build log with secrets masked (never in --json or a pipe), and exit code 21; no Activate link and no request to merge. A build that was canceled or skipped (Vercel's Ignored Build Step, or a newer commit replaced it) is reported as such. When Ulika cannot see the build at all it says so and never merges by itself. Activate is refused by Ulika's server unless the preview is ready.

  • The connector build no longer writes JSX into index.html when two HTML bindings share the same text (for example <title> and og:title), which broke Vite builds. Connector pull requests opened before this release must be opened again.

  • The site review recognises Vite apps and, when a site has no sitemap, counts the pages linked from its home page.

  • connect <url> --dry-run now reports what a real run would do, with the exit code it would end on, and creates nothing. When this machine cannot resolve the site's source (no vercel login, no gh), it used to print a "finish in your browser" handoff and exit 0 without checking anything. It now asks Ulika's server: the same repository resolution and the same install check (read-only), and --repo is honoured. Exit codes: 0 ready, 20 a person has to act (for example a repository to name), 21 the repository could not be read to the end, 26 Ulika cannot install on the site's framework.

  • A dry run needs this machine to be approved already and never starts an approval: without one it exits 22 and tells you to run ulika login first. It sends the site address and the --repo value to Ulika, nothing else.

  • connect --all --dry-run and a dry run over several sites now exit 2 instead of silently running a real batch. A dry run reports on one site at a time.

  • connect exits 26 (it was 21) when nothing is live and every failed site was refused because Ulika cannot install on its framework, the same code init uses. Any other failure still exits 21.

  • Ulika now also finds a site's repository from the Vercel project that lists the address as one of its domains, including a domain that redirects or has not been deployed to yet. It is only used to find the repository, never to open or change a Vercel project.

  • init names the site from the production domain of the linked Vercel project before it falls back to a GitHub Pages address, and a homepage on github.io gives way to it.

  • scan and init no longer bind dead text. The scan follows every import alias the app can use (a Vite resolve.alias before tsconfig paths, in the order the config declares them), so an app whose tsconfig still maps @/* to the repository root no longer falls back to "Could not tell which files the app actually uses" and binds every file.

  • Translation dictionaries (translations.ts, locales/, i18n/) are now kept whole or left out whole; there is no longer any per-key choice. A dictionary is left out, with a note saying so, only when nothing in the app consumes it: every reachable file that imports it, or imports anything its provider, hook or context exports (followed through barrels), is the dictionary itself, a module that only defines or re-exports that provider, hook or context, or the app's entry doing nothing but mounting the provider. Any other file that imports, requires or import()s them keeps the whole dictionary, and so does a .vue, .svelte or .astro file that names one of those modules. Every dictionary is also kept when the nearest package.json lists an i18n library (i18next, react-i18next, next-intl, react-intl, vue-i18n, Lingui, and the like), because the library reads its catalogues without any file importing them by name, and when a dictionary, or a file importing one, hands it to a call such as .init(, createInstance(, createIntl( or <IntlProvider messages=. When the app imports a JSON dictionary, the scan warns that JSON dictionaries are not read.

  • When a site has more editable places than one scan keeps (1000), the order of what survives changed. Before, SEO fields competed with visible copy on confidence alone, and copy read from data came last. Now: visible page copy first, then SEO, then copy read from data, then icon names, with the field's path as the final tie-break so the same site keeps the same fields every time. The scan runs on your machine and is not told which fields a project already bound, so a re-scan cannot keep previously bound fields ahead of others; it ranks by the order above.

  • scan no longer says fields "were sent for review"; only init and connect do.

  • Re-scanning a site that used to fall back to "unknown" now skips files nothing imports. Fields that came from them are no longer found and are marked as missing their binding.

0.6.14 (2026-10-25)#

  • init now checks, right after the scan and before anything else, that Ulika can install on the site. It installs on React sites built with Vite (with its React plugin) or Create React App, and on Next.js App Router sites. For anything else (static HTML, Astro, SvelteKit, Nuxt, Remix, Gatsby, RedwoodJS, Expo or React Native, a React site without a Vite or Create React App build, or Next.js on the Pages Router) it stops with a sentence that names the cause, for example "Ulika can't install on Gatsby sites yet. It supports React and Next.js. Nothing was created in Ulika.", and exit code 26: no approval, login, hosting access, project or ulika.config.json. --dry-run prints the same verdict. Before this, such a site was imported first and the failure came at the end.

  • init --import-only is refused too on a site Ulika cannot install on: importing the content of such a site is no longer possible, because it would leave a project that can never be connected.

  • When a folder has a package.json but no supported framework (a monorepo root, a Vue or Solid app), init says "Ulika didn't find a React (Vite or Create React App) or Next.js App Router project here. If this is a monorepo, run the command inside the app's folder." It says "static HTML" only when there is no package.json and there are .html files.

  • When init clones a repository for a remote site and then refuses it, the clone made for that check is removed, and the message says nothing was created in Ulika.

  • connect reports a site Ulika cannot install on as failed with that same sentence, before any project is created, and no longer suggests ulika init --local for it (which cannot install either).

  • When an install did not finish and --import-only was not used, the next action says to fix the installation error and run ulika init again, instead of "rerun without --import-only".

0.6.13 (2026-10-18)#

  • When Ulika cannot be reached, connect and init now say why (a blocked DNS lookup, a refused or reset connection, a timeout, a certificate or proxy problem) and what to allow, instead of "fetch failed". Starting the approval (connect, init and login) is retried a few times on a dropped connection, a timeout, a refused connection or a temporary DNS failure, and never on a certificate, proxy or unknown-name problem. The hint to check the --server value is only given for a server other than Ulika's own.

  • After you merge the connector pull request yourself, connect keeps following the site until your live site serves the connector (up to 10 minutes), says "merged, verifying the live site", and ends live. A site that is still verifying is named in the report with its next step, not counted as "still in progress".

  • Running connect again after a manual merge follows the same connection and pull request; it no longer opens a second pull request for the same repository.

  • init says the editor is a preview until the connector is activated.

  • connect no longer opens a new connector pull request by itself after a person closed one on GitHub: it stops with pull-request-closed and the one action that starts again, --reopen (or Start a new connector on the connect screen). A pull request Ulika closed itself, such as an outdated one it replaced, still restarts without it, and a connector Ulika reverted is never restarted by itself. When the files a connector binds to changed under an open pull request, Ulika closes its own untouched pull request first and opens the replacement in the same run; if the pull request is not provably Ulika's own and untouched it asks you to close it and opens no second one.

  • When Ulika cannot read a build, the message now says whether the cause is a permission you can accept, a GitHub app that does not request it (nothing to approve), Ulika's own GitHub access being unreadable right now, or simply a host that reported nothing to GitHub; in every case Ulika checks the live site after the merge.

0.6.12 (2026-10-17)#

  • When a site's connector pull request was prepared in the other language, Ulika now closes its own outdated pull request and opens a new one by itself; connect only asks you to close it when someone has changed it.

  • A build that your host reports as finished on GitHub is now read as finished, so connect no longer stops with "could not observe the build" for it, and a missing GitHub App permission is named.

0.6.11 (2026-10-17)#

  • connect and init poll the server less often while waiting (backing off to 30 seconds) and never wait longer than the server asks; nothing else changes for you.

  • The review link that ulika link prints expires after 24 hours. If it has expired, run the command again to get a new one.

0.6.10 (2026-10-17)#

  • Ulika now writes its connector in JavaScript into a Next.js site that does not use TypeScript, so the site keeps building. If an open connector pull request was prepared in the other language, connect stops with connector-language-changed and links the pull request to close first.

  • A preview build that failed is reported as build-failed with a link to the build log, never as "could not observe the build".

  • When Ulika finds a repository named like a vercel.app or netlify.app site, it never connects it on its own: confirm it on the approval page, or run the --repo command it prints.

  • When a repository is already connected in another workspace, connect --check names that workspace if you are a member of it.

  • A merged connector whose live site Ulika cannot verify stops with production-unverifiable and explains why; you can press Activate anyway in the dashboard.

0.6.9 (2026-10-16)#

  • ulika logout now also signs this machine out of init and connect, so you can approve again with another account; ulika whoami says when this machine holds an approval.

0.6.8 (2026-10-14)#

  • A site that needs Vercel now asks for it right after the import, before "changes prepared". If the Vercel account that owns the project is not connected, connect stops with exit code 20, never 21, and names the accounts Ulika searched. The four reasons are vercel-not-connected, vercel-wrong-account, vercel-token-invalid and vercel-unavailable.

  • A workspace can hold several Vercel accounts and teams. Adding one never replaces another, and replacing an account in use lists the sites it serves instead of blocking.

  • When you connect the right Vercel account within 24 hours, the site that was waiting continues by itself and nothing imported is lost. After that, run connect again.

  • connect --check reads the repository's root package.json and says a Next.js site needs Vercel instead of "git alone". If GitHub cannot be read, it warns instead of staying silent.

0.6.7 (2026-10-14)#

  • Before a new approval link, connect prints Checking <site>… and shows what Ulika can already see of each of the first two distinct sites (reachable, pages, hosting), and --json emits a site_preview event before browser_plan. It is anonymous and best-effort: a rate limit prints when to retry, and an older server or an answer slower than 10 seconds skips it without stopping the approval.

  • --json prints a browser_plan event before approval_required when the code is new or the browser opens, and plain output prints the same steps. Read events by name, not by line number. A reused code polled again with --no-wait stays quiet.

  • Running connect again while its approval code is still open reuses the code and opens the browser again, unless --no-browser, --no-wait, ULIKA_NO_BROWSER, CI or SSH say not to. A run for different sites gets a fresh code, so the page never shows the wrong site.

  • The approval page now leads with Continue with GitHub. On first use it creates your account and a workspace named after your site (rename it in workspace settings). Email sign-in and sign-up are the second path, and you name the workspace yourself there.

  • A GitHub account that shares no verified email is asked for one on the same approval page, and no second account is created.

  • The approval code now survives sign-in, sign-up, GitHub and email confirmation. A confirmation email opened in another browser still lands on the approval page, once, from the same network.

  • Approval no longer depends on a GitHub connection made in the last 24 hours: Ulika checks your installations live when the page opens. If GitHub does not answer, the page says so and offers Try again, never "no accounts".

  • When Ulika cannot tell which repository serves a site, the approval page lists likely ones or offers None of these. The CLI uses your pick for that run, --repo always wins, and a pick it sets aside is reported on one line. A repository in another account says to install the App there and run --reapprove.

0.6.6 (2026-10-13)#

  • Connecting no longer fails with "Couldn't locate ... in .ulika/build.mjs": Ulika skips its own generated files when it reads a repository, and projects that already imported those fields recover on the next read.

  • Waiting for approval no longer ends in "Too many polls for this device code": the server allows a full wait, and the CLI asks for a fresh code instead of reusing a dead one.

  • When the connector cannot be prepared, the CLI prints the real reason under the attention line, in plain and --json output, and the advice now says what to do.

  • The timeout message names the approval link and reminds you to install the Ulika GitHub App on the account that owns the repository.

0.6.5 (2026-10-10)#

  • Approving is now the consent. By default Ulika merges the connector once your host builds it, checks your live site, and undoes the change if the live build fails. The approval page and the dashboard say so.

  • --review-first (and the Let me review the change before it goes live checkbox on the approval page) opts out: each site waits for one Activate link instead.

  • --auto-merge still works but does nothing, because merging automatically is the default.

  • A site now stops for a person only when truly needed. Branch protection waits, and the batch resumes after you merge on GitHub.

0.6.4 (2026-10-10)#

  • One Activate step everywhere. A site that waits for you shows one Ulika link and one sentence; the GitHub pull request is only a secondary option.

  • ulika connect now keeps waiting until the site is live: up to 15 minutes (--wait-timeout <min> changes it, --no-wait skips it), with a status line every 30 seconds, then the editor link.

  • The dashboard, connect page, Codex skill and MCP tool descriptions use the same wording.

0.6.3 (2026-10-09)#

  • Vercel deploy hooks no longer pile up: Ulika finds its own by name, removes duplicates and proves a removal by reading the project back.

  • When the ULIKA_BUILD_TOKEN variable is held by another tool Ulika cannot manage, Ulika stores its token as ULIKA_CONNECTOR_TOKEN; the build reads that name first and leaves the old variable alone.

  • Failures that used to say only "unavailable" now say what Vercel actually answered.

0.6.2 (2026-10-09)#

  • A repository that already has the connector installed now continues and verifies production instead of stopping as unsupported or too large.

  • A connector pull request merged by a person now wakes the sites that were waiting for it, so they finish without a re-run.

  • Re-running a site that is already live reports it as live (already connected).

0.6.1 (2026-10-09)#

  • Protected previews are handled: when Vercel protects previews, Ulika creates or adopts a Protection Bypass for Automation secret (and never touches ones you made).

  • A protected preview that cannot be read becomes a preview-protected attention item after three minutes; an unreadable preview becomes preview-unreadable after ten. A build no longer hangs silently.

  • The Vercel step now also runs for sites that publish through git.

0.6.0 (2026-10-09)#

  • Convergent connection: Ulika observes the real state of your repository and Vercel project, applies only the difference, and proves the result. Re-running is safe and changes nothing when the site is already connected.

  • New --check option: a read-only preflight that lists every blocker and warning at once, each with one fix. Problems with fixes also appear in the report.

  • Ulika adopts connector leftovers it owns and refuses anything held by a live project in another workspace.

0.5.5 (2026-10-09)#

  • Repairs a refused build-token write (Vercel's ENV_CONFLICT) by finding and patching the existing variable; git delivery no longer stops on it.

  • A site whose Vercel project is not linked to Git gets a Connect this site to GitHub step you approve in the browser.

  • A repository that looks like a backup, archive or fork is never picked on its own; the repository Vercel deploys from wins.

  • A re-run for an address keeps that address.

0.5.4 (2026-10-08)#

  • A repository whose committed connector belongs to a project that was deleted (or one in the same workspace) is updated in place instead of refused as a conflict. A live project in another workspace is still refused, with a plain message.

  • A site asked for by address keeps that address and a readable name when its repository row already existed.

0.5.3 (2026-10-08)#

  • Connect one domain from any computer with a single command: connect <url> now goes through Ulika's GitHub App, so nothing has to be cloned or installed. The new --local option keeps the checkout, vercel and gh path.

  • The connector build runtime gains the live editing script that lets people edit the real site in place.

  • Released together with the app's instant publish and History restore.

0.5.2 (2026-10-08)#

  • ulika codex install and ulika codex uninstall add and remove Ulika in Codex (the MCP server entry in config.toml, plus a skill). New options --no-skill and --force.

  • MCP code tools: list_code_files, read_code_file and write_code_file let an agent customise website source as a local draft, guarded by a file hash.

  • --repo <owner/name> names the repository for one address.

  • The scanner gains new modules for data literals, icons and section names, used by the editor and style panel.

0.3.1 (2026-10-04)#

  • The CLI never hangs silently without a terminal: the approval link, code and expiry go to standard error, and a heartbeat prints every minute while waiting.

  • On a normal desktop session the approval page opens by itself. It does not on CI or over SSH, with --no-browser or --no-wait.

  • The approval_required event gains browserOpened. Ulika's own address is refused as a site, and --server is validated.

0.3.0 (2026-10-03)#

  • AI-native connect: ulika connect with --all, --urls, --repos and --resume connects many sites with one browser approval, running on Ulika's servers.

  • New agent tokens (scoped to connecting sites and reading progress, expiring) and the --no-wait, --reapprove and --auto-merge options.

  • New MCP tools connect_sites, batch_status and approval_status, and newline-delimited JSON output for batches.

0.2.2 (2026-09-30)#

  • Printed commands use the versioned tarball address, because npx caches a tarball by its address.

  • init warns when the server has a newer CLI and prints the command for it.

0.2.1 (2026-09-30)#

  • ulika init <url> hands off to the browser flow, printing and opening a dashboard link, when the site's code is not on this computer or vercel cannot resolve it. With --json it returns a handoff status and the link.

0.2.0 (2026-09-30)#

  • The package is renamed @ulika/cli and is served from Ulika itself at ulika.co/cli.tgz, with an immutable copy per version and a version.json.

0.1.3 (2026-09-30)#

  • Ulika moved to ulika.co. It is now the CLI's default server, and credentials saved against the old address keep working.

0.1.2 (2026-09-30)#

  • The connector runtime can show a connected site live inside the editor (a framework-agnostic bridge).

0.1.1 (2026-09-30)#

  • Reachability-aware scanning: the scanner now understands which components your site actually uses, so unused code is not offered as editable content.

  • Preview verification through the Vercel CLI is fixed.

  • Installing and verifying connectors from a Vercel domain (init <url> with --import-only, --scope and --activate) arrived between 0.1.0 and this release.

0.1.0 (2026-09-17)#

  • First version, forked from the original CMS core: init, link, scan, status, login, logout, whoami and mcp, with --dir, --url, --server, --dry-run, --yes and --json.

Was this page helpful?

PreviousCLI reference

On this page

  • 0.7.1 (2026-11-05)
  • 0.7.0 (2026-11-04)
  • 0.6.17 (2026-10-31)
  • 0.6.16 (2026-10-31)
  • 0.6.15 (2026-10-26)
  • 0.6.14 (2026-10-25)
  • 0.6.13 (2026-10-18)
  • 0.6.12 (2026-10-17)
  • 0.6.11 (2026-10-17)
  • 0.6.10 (2026-10-17)
  • 0.6.9 (2026-10-16)
  • 0.6.8 (2026-10-14)
  • 0.6.7 (2026-10-14)
  • 0.6.6 (2026-10-13)
  • 0.6.5 (2026-10-10)
  • 0.6.4 (2026-10-10)
  • 0.6.3 (2026-10-09)
  • 0.6.2 (2026-10-09)
  • 0.6.1 (2026-10-09)
  • 0.6.0 (2026-10-09)
  • 0.5.5 (2026-10-09)
  • 0.5.4 (2026-10-08)
  • 0.5.3 (2026-10-08)
  • 0.5.2 (2026-10-08)
  • 0.3.1 (2026-10-04)
  • 0.3.0 (2026-10-03)
  • 0.2.2 (2026-09-30)
  • 0.2.1 (2026-09-30)
  • 0.2.0 (2026-09-30)
  • 0.1.3 (2026-09-30)
  • 0.1.2 (2026-09-30)
  • 0.1.1 (2026-09-30)
  • 0.1.0 (2026-09-17)
Ulika documentationFAQ · CLI reference · Terms · Privacy