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

Connect a site

Approving a connection

What you agree to when you approve Ulika, how automatic activation and automatic undo work, and how to review every change first.

Last updated October 14, 2026

Connecting a site asks for a few approvals, and each one has a precise meaning. This page explains what you agree to when you click Turn on live editing, when you approve a command-line machine, and when you approve an AI agent. It also explains the safety net, the automatic undo, and how to choose automatic merge instead of the review-first default.

The short version#

When you approve Ulika, you agree that it will:

  1. Add its connector to your repository (a small folder plus one build setting) on a new branch.

  2. Merge that change into your default branch once your host has built it.

  3. Check your live site to confirm the connector is really being served.

  4. Undo the change automatically if the live build fails.

By default Ulika opens a pull request and merges nothing until you activate it. Nothing reaches your live site until you click Activate on the live site or merge the pull request on GitHub. With automatic merge, Ulika merges the connector once your host's build passes, checks your live site, and undoes its own merge if the production build fails. You choose automatic merge with the box Merge automatically once the build passes, which starts unticked.

What the approval text says#

The exact sentence you see next to the approval is:

Ulika will add its connector to owner/repository (a small folder + one build setting) in a pull request. By default Ulika opens a pull request and merges nothing until you activate it. With automatic merge, Ulika merges the connector once your host's build passes, checks your live site, and undoes its own merge if the production build fails. If your host keeps previews private, Ulika merges (on its own, or when you activate) once the host reports a successful build, and checks your live site right after.

In the dashboard, the repository is named. In the agent approval, it says "each repository it connects".

Approving in the dashboard#

The approval is the button Turn on live editing. Above it you choose between two modes.

Automatic (you opt in)#

Check Merge automatically once the build passes. The reason beside the button reads: "Ulika opens a pull request, builds a preview, then goes live by itself once the build passes. If the production build fails, it undoes its own merge."

What happens, in order:

  1. Ulika creates the branch ulika/setup with one commit and opens a pull request.

  2. Your host builds a preview. Ulika waits until it can confirm the build (see Private previews).

  3. Ulika merges the pull request. It merges only the exact commit it wrote.

  4. Ulika checks your live site until it serves the connector. You see Waiting for production to serve the connector, while Ulika checks every few seconds for up to two minutes. If it is still waiting after that, the page says where to look; reload it to see the result.

  5. You see Live editing is on.

In a batch from the CLI or an agent, Ulika does not stop to ask when your host reports a successful build to GitHub but offers no preview address Ulika can read (a private preview). It merges on the host's word, because the live check and the automatic undo that follow are the safety net, and it records that reason (host-success) on the connector. The connector counts as live only once your production site serves it, and Ulika reverts its own merge if the live build fails.

Review first (default)#

Leave Merge automatically once the build passes unchecked. The reason beside the button reads: "Ulika opens a pull request and builds a preview. Nothing on your live site changes until you activate it."

Ulika then stops after step 2 and shows Activate live editing. You can:

  • Click Activate on the live site, which merges the pull request for you, or

  • Click Prefer GitHub? Review and merge PR #N and merge it in GitHub yourself, or

  • Click See the exact diff to read the change first.

Ulika offers Activate on the live site only after it has confirmed the preview. Until then, you can still merge the pull request yourself on GitHub whenever you are ready.

Note

Merging is the first moment anything reaches your live site, and even then it arrives only when your host next deploys the default branch. Your host builds the merged commit the same way it builds any other push.

Approving a command-line machine#

When you run the CLI for the first time, it prints a link and a code such as ABCD-EFGH. The page it opens is Authorise Ulika CLI. It shows the code, what is asking (name, version and transport), the folder it was run in, and when and from where the request came.

It tells you what the machine will be able to do: create projects in your workspace and import content from repositories you run it in. It cannot read your source code, only the content manifest that the scan produces on your machine.

  • Compare the code with the one in your terminal, then click Approve (or Deny).

  • The page warns: Only approve if you just started this from your own terminal.

  • A code expires within 15 minutes. After several wrong guesses from one network, you see Too many codes tried and must wait fifteen minutes.

  • You must be signed in and a workspace owner. Other roles see that they cannot authorize a machine and are told whom to ask.

After approval, later runs on that machine do not ask again.

Approving an AI agent#

When an agent runs connect, the approval page is titled Approve this agent. It shows the code, the agent and machine name, when it asked, the workspace, and the GitHub accounts it may use.

Signed out, the page leads with Continue with GitHub, which creates your account the first time, and offers email second. See Connect with the CLI for the whole path.

The GitHub accounts line comes from a live check. When you open the page, Ulika asks GitHub which accounts you can reach and lets the agent connect only those. Ulika does not keep your GitHub token. If nothing has been checked yet, the page offers Continue with GitHub to do it. If the Ulika app was suspended or removed, it offers Install the Ulika app on GitHub. If GitHub does not answer, it says Could not check right now with a Try again button, and nothing is approved.

When Ulika cannot tell which repository serves the site, the page lists the likely ones for you to choose from, or you can choose None of these. A repository found only because its name matches the site address is offered the same way: it is never preselected, and you must click it to confirm it. The command never asks again: the site ends in the attention list as ambiguous-repository, with the exact command to run, ulika connect <url> --repo owner/name. If Ulika's own budget for these checks runs out, the page says to wait and adds You can still approve. A repository in another account or organisation needs the App installed there, then the command run again with --reapprove.

Note

A self-hosted Ulika can switch the GitHub-first page off with ULIKA_GITHUB_FIRST_APPROVAL=off. The page then shows plain sign-in and sign-up buttons. The fixes for owner-request and declined notices stay on.

Under This agent will be able to you see:

  • Connect up to 50 sites at a time from repositories in your connected GitHub account or accounts.

  • Open a pull request that adds the connector to each repository, and report progress. It merges only if you tick the automatic merge box.

The page adds the limits: It cannot publish content, read drafts, invite people or manage tokens. It stops working after 30 days, or after 14 days unused, and you can revoke it in Settings, in the Agents section, with the Revoke button.

Above the buttons is a sentence that starts with Approving means: and repeats the consent text, followed by the checkbox Merge automatically once the build passes, with the note "Off by default. Leave it unchecked to review the pull request and activate it yourself." It starts ticked only when the command was run with --auto-merge. Then click Approve this agent or Deny.

Read more in Connect with AI agents.

Review first with the CLI#

Run the CLI as usual (--review-first is the default and does nothing). Ulika does not merge by itself. For each site you get one Ulika link and one sentence: "Open this link and click Activate to put Ulika on your live site." The GitHub pull request is shown after it as a second option (Prefer GitHub? Review and merge PR #N).

The command waits and prints a short status every 30 seconds. It gives up after 15 minutes (set it with --wait-timeout <min>) and exits with code 20. --no-wait skips the wait and exits with code 20 at once; so does a run without a terminal, which also skips the wait for the first approval (pass --wait to keep waiting). Passing --auto-merge to a batch pre-ticks the box on the agent approval page; you can still untick it. A single-site ulika connect <url> refuses --auto-merge: it opens a pull request, and you run it again with --activate after reviewing. See the CLI reference.

What happens if the live build fails#

This is the safety net behind the words "Ulika undoes it automatically".

  1. After Ulika merges the connector, your host builds the default branch.

  2. If your host reports that this production build failed, Ulika opens a pull request named Revert the Ulika connector (production build failed) on a branch called ulika/revert.

  3. Ulika merges that pull request, or asks GitHub to merge it automatically once required checks pass. If your repository needs a review, it waits for a person.

  4. Your live site keeps serving the previous deployment the whole time, because hosts generally keep the last successful deployment live until a new build succeeds (check your host's documentation for how it behaves). The revert restores your build, not your site.

  5. In Ulika you see: "Your host's production build failed after Ulika merged the connector, so Ulika reverted its own change. Your live site kept serving the previous deployment. Check the build log on your host, then create a new connector pull request."

The revert is deliberately narrow:

  • It touches only the connector's own files, and puts each back to what it was before (files Ulika created are removed).

  • It is one new commit. There is no force push, no history rewrite and no branch deletion.

  • If someone edited any of those files after the merge, nothing is written and Ulika asks a person, because restoring the files would discard their work.

  • A merge a person made is never reverted by Ulika. It is only flagged.

Warning

Ulika only learns that a production build failed from a production deployment reported to GitHub (or through the Vercel connection). Netlify reports production builds as commit statuses and Cloudflare Pages as check runs, which do not say which environment they were for. On those hosts, Ulika does not see a failed production build today. It waits for the connector to appear on your live site and does not revert on a host's word. If you use one of them, leave automatic merge off and activate yourself.

What always needs a person#

Even in automatic mode, some sites cannot be finished without you. Ulika sets these aside, never guesses, and tells you the one thing to do. Common examples are a branch protected by rules Ulika cannot satisfy, a repository Ulika cannot write to, a Vercel project deployed outside Git, and a preview that stays unreadable. Each reason and its fix is listed in Connection problems.

Organization installations need a fresh approval every 7 days before Ulika writes to them again. When that happens, run the same command with --reapprove. Personal accounts and reading are not affected.

What approval never allows#

  • Writing to your default branch other than the merge you approved, a revert of it, and the one content file written on Publish. See Publish.

  • Force pushes, history rewrites or deleting branches.

  • Merging a commit Ulika did not write. If someone pushes onto the ulika/setup branch, Ulika stops and says The connector branch changed after Ulika wrote it.

  • Storing your source code.

See the security overview.

Was this page helpful?

PreviousConnect with an AI agentNext Private previews

On this page

  • The short version
  • What the approval text says
  • Approving in the dashboard
  • Automatic (you opt in)
  • Review first (default)
  • Approving a command-line machine
  • Approving an AI agent
  • Review first with the CLI
  • What happens if the live build fails
  • What always needs a person
  • What approval never allows
Ulika documentationFAQ · CLI reference · Terms · Privacy