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

Connect with an AI agent

Let Claude Code, Codex or any MCP agent connect your sites to Ulika. You approve once in the browser; the agent does the rest, within a 24-hour site cap.

Last updated October 14, 2026

If your site was built with an AI coding agent, the same agent can connect it to Ulika. You tell it "Connect my site to Ulika", open one link, click approve, and it does the rest. This page explains how that works, what the agent is and is not allowed to do, and how to take the approval back.

The tools behind it are the Ulika CLI and its MCP server. Setup guides for each agent: Claude Code, Codex and any MCP agent.

Two ways an agent can connect a site#

WayHow it worksBest when
Run the CLIThe agent runs ulika connect https://your-site.com --json in a terminal and reads the result.The agent has a terminal (Claude Code, Codex). Nothing needs to be registered.
Use MCP toolsThe agent calls the connect_sites, approval_status and batch_status tools from the Ulika MCP server.You want structured results instead of terminal text, or the agent has no terminal.

Either way, the agent is told never to ask you for a project name, a repository, a token or a pairing code, and never to ask you for local files. It needs one thing from you: your website's address.

What you do#

  1. Ask your agent: Connect my site to Ulika. If it does not know your site, give it the address, for example https://your-site.com.

  2. The agent shows you one link and one code. Open the link. The approval page is on Ulika (the page lives at ulika.co/connect).

  3. Sign in if asked, check that the code matches what the agent showed, and click Approve this agent.

  4. Go back to the agent. It follows the progress and reports which sites are live, with editor links, and what, if anything, needs you.

That single approval is all that is needed. The work runs on Ulika's servers, so it keeps going even if the agent's session ends.

The approval flow in detail#

The agent asks Ulika to open a device request. That is the same pattern gh auth login uses:

  1. The request. Ulika returns a short code (like ABCD-EFGH) and a link to the approval page. The code lasts about 15 minutes.

  2. The link. The agent relays the link and code to you. In a terminal the CLI also opens the browser by itself on a normal desktop session; it does not on CI, over SSH, or when ULIKA_NO_BROWSER=1 is set or --no-browser is passed.

  3. The page. It is titled Approve this agent. It shows which agent asked, when and from what address, your workspace, and your connected GitHub accounts, and lists what the agent will be able to do:

    • Connect up to 50 sites at a time from repositories in your connected GitHub 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.

    It also states what the agent cannot do: publish content, read drafts, invite people or manage tokens.

  4. The consent. The page tells you what approving means: Ulika adds its connector to each repository it connects (a small folder and 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.

  5. The choice. A checkbox, Merge automatically once the build passes, starts unticked, so review first is the default: each site waits for one Activate link. Tick it if you want Ulika to merge by itself. If the agent was started with --auto-merge, it starts ticked, and you can still untick it.

  6. The click. Approve this agent creates the agent token; Deny refuses and nothing is created. After approving the page tells you to return to your terminal.

If you are not signed in, the page leads with Continue with GitHub (which creates your account the first time) and offers email second, and it keeps your code. Ulika checks your GitHub accounts live, because an agent can only connect repositories your GitHub account has shared with Ulika; if the App is not installed yet, you install it once and come back. If your role cannot create projects, the page tells you to ask an owner. Too many wrong codes in a row from one network show Too many codes tried; wait fifteen minutes and use the link the agent printed.

Warning

Only approve a code you just saw your own agent print. The page tells you the same thing. A link that arrived any other way belongs to someone else's request.

What the agent token can and cannot do#

CanConnect sites from repositories in the GitHub accounts you have shared with Ulika, and read the progress of its own batches.
CannotPublish content, read drafts, invite people, manage tokens, or use any other part of your workspace.
Lifetime30 days from approval, and revoked after 14 days unused.
Revoked alsoWhen the person who approved it leaves the workspace, or when GitHub access is removed.
Limit50 sites in any rolling 24 hours.

The token is stored on the computer that asked, in ~/.ulika/config.json, readable only by you. It is shown once and Ulika keeps only a hash. You can see every approved agent under Agents in your workspace settings, with when it was approved and last used, and click Revoke. A person who approved an agent can revoke it, and so can a workspace manager.

The 24-hour site cap#

Each agent can take on at most 50 sites in any rolling 24 hours, counted across all its batches. Asking again for a site it already has is not new work. When the cap is spent the agent gets a site_cap answer: the CLI exits with code 24, and the MCP tool reports an error saying how many sites remain. Nothing is retried. Wait for earlier sites to age out of the 24 hours, or approve a new agent.

Weekly re-approval for organisations#

For repositories owned by a GitHub organisation, an approval is only good for writing for seven days, because Ulika cannot see someone leave an organisation. After seven days those sites stop with the reason reapproval-required. Run the same command with --reapprove (the CLI) or ask the agent to start again (MCP), and approve again. Repositories owned by a personal account, and reading progress, are not affected.

--all: you see the list first#

If the agent connects "all my sites", Ulika first lists the sites it found, and nothing is written until a person has agreed. The agent must show you the list and only then confirm. With the CLI this is exit code 23 and a confirmation_required line; with MCP it is batch_status returning confirmation_required, then a second connect_sites call with all and confirm both true. Lists you typed yourself (specific addresses or repositories) start at once.

When a site needs you#

By default Ulika opens the pull request and waits for you. If you ticked automatic merge there is no further click: Ulika merges the connector, checks your live site and undoes its own merge if the production build fails. A site stops for a person when it needs one (you left automatic merge off, branch protection wants a human review, or Ulika cannot see your host's builds). The agent then gives you one link and one sentence: Open this link and click Activate to put Ulika on your live site. It never sends you to the GitHub pull request, because a browser that is not signed in to GitHub shows a 404 for a private pull request; the pull request is offered only as a second option. Click Activate, and the agent keeps checking until the site is live, then gives you its editor link. The reasons a site can stop are explained in Connect attention reasons.

Guard rails#

  • Ulika is never its own customer. The CLI and the server both refuse Ulika's own address and repository with the reason this-is-ulika. If you did not name a site, the agent is told to ask which website you mean.

  • It never guesses. An address is tied to a repository only when Ulika is certain. Otherwise the site is marked ambiguous-repository and you choose. See Connect with the CLI.

  • The code stays on your computer. The scan runs locally; only the derived content manifest travels, never your source code.

  • Nothing is published for you. Connecting a site sets it up for editing. Publishing is a separate step that a person takes in the editor.

A recipe for agents without MCP#

An agent whose tool calls time out should not hold the approval wait open. This is the sequence the CLI is designed for:

bash
ulika connect https://your-site.com --json --no-wait   # 1. exit 22 + an approval_required event (find it by name, not by line number): relay url and code, once
ulika connect https://your-site.com --json             # 2. after the person approved: connects and streams events
ulika connect --resume bat_123 --json                  # 3. if the process died, pick the same batch back up

For many sites replace the address with --all, then expect exit 23 and the list first, and re-run with --yes only after a person agreed (see above). Read the exit code, then the last line: report (exit 0, 20 or 21) or error (with code and hint). Present every report.live[].editorUrl, and for every report.attention[] its reason and its one action.label and action.url. Details of every line are in the CLI reference.

Customising the site's code#

Besides connecting, the MCP server can let an agent change your site's source files on your computer. These tools can list, read and write website source files, but only in the folder where the MCP server started, and every change is a local draft: they never commit, deploy or publish. See MCP tools.

If something goes wrong#

Start with CLI errors and exit codes, which explains each exit code and each reason a site can stop, and Connect attention reasons.

Was this page helpful?

PreviousConnect with the CLINext Approving a connection

On this page

  • Two ways an agent can connect a site
  • What you do
  • The approval flow in detail
  • What the agent token can and cannot do
  • The 24-hour site cap
  • Weekly re-approval for organisations
  • --all: you see the list first
  • When a site needs you
  • Guard rails
  • A recipe for agents without MCP
  • Customising the site's code
  • If something goes wrong
Ulika documentationFAQ · CLI reference · Terms · Privacy