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

Getting started

Quickstart

Connect a website with one command or from the browser, turn on live editing and publish your first change, step by step.

Last updated October 14, 2026

This quickstart takes you from a new account to a published edit. There are two ways in: one command in a terminal, or your browser only. You need a website that meets the requirements and a GitHub account that can access the site's repository.

Before you begin#

  • Your site is public and its code is in a GitHub repository.

  • You can install a GitHub App on that repository, or someone who can is available.

  • Your host builds the site when you push to the repository.

Fastest path: one command#

If you use GitHub and have Node.js 20 or newer, one command is enough. You need no Ulika account first.

Run this in any folder, with your own site's address:

bash
npx -y https://ulika.co/cli/ulika-cli-0.7.1.tgz connect https://your-site.com

Then:

  1. The terminal shows what Ulika can see of your site, then prints a link and opens it in your browser.

  2. On that page, click Continue with GitHub. This creates your account and a workspace named after your site. If asked, install Ulika's GitHub App on the account that owns the repository, then come back to the page.

  3. Check that the code matches your terminal, pick the repository if the page asks, and click Approve this agent.

  4. Go back to the terminal. Ulika connects the site and prints a link to the editor. This one command covers steps 1 to 5, so continue at Step 6.

More detail, and what to do without GitHub, is in Connect with the CLI. To stay in the browser, read on.

Step 1: create your account and workspace#

  1. Open the Ulika sign-up page and either enter your Email and Password and click Create account, or click Continue with GitHub.

  2. On the next screen, answer What should we call you? and give your workspace a Workspace name, such as your studio, team or project name. Click Create workspace.

The person who creates a workspace is its owner, which is the role you need to connect a site.

Tip

Want to see what Ulika finds before you sign up? The public check at /start has a Check my site button. It reads your public pages, shows what it detects, and keeps the result for about half an hour so you can continue after you register.

Step 2: start connecting#

  1. On the Projects page, click Connect website.

  2. Under Your website address, type your site's address, for example acme.com, and click Connect.

Ulika now reads your public pages. You see four short steps while it works: reaching the site, reading the page, checking robots.txt and the sitemap, and working out the stack. It runs nothing from your site and stores nothing until you choose to connect.

When it finishes, you see Your site is ready to connect, with the address, the detected framework and the host. If the framework looks wrong, ignore it. The repository scan in the next steps is the real test.

Note

If you see This is a platform site, your site is on a hosted platform such as WordPress or Shopify with no codebase to read. See Requirements.

Step 3: connect GitHub#

Step 2 on the screen is Connect your codebase. It shows a terminal command, which is the fastest path if you have the project on your computer (see Connect with the CLI). To stay in the browser:

  1. Under Prefer another method?, click Connect with GitHub.

  2. Click Continue with GitHub. You go to GitHub in the same tab.

  3. Install the Ulika GitHub App on the account that owns the repository and choose the repository (or repositories) it can see. If you manage the repository through an organization and are not an owner, GitHub sends the owners a request and Ulika shows Your request was sent.

  4. GitHub sends you back to Ulika. If you have more than one GitHub account with Ulika installed, pick the right one with Use this account.

Ulika asks for permission to read your code. Nothing is written to your repository at this point. More on permissions in The GitHub App.

Step 4: pick the repository#

Ulika ranks the repositories it can see against your site's address.

  • If one repository is a clear match, Ulika selects it and continues by itself.

  • If it cannot be sure, you see Which repository builds your site? Choose the right one and click Use this repository. Why this one? shows the evidence for each candidate.

  • If the repository you need is not in the list, click Add a repository on GitHub, select it there, and come back. The list refreshes when you return to the tab (or click Refresh list).

Then Ulika works through four steps and shows each one as it finishes: Selecting the repository, Reading the source, Importing the content and Preparing the connector. Your code is read in memory and never stored.

Step 5: turn on live editing#

You now see Turn on live editing for your site. Ulika tells you how many small files it will add, and you can open See what Ulika adds to read the full diff.

  1. Leave Merge automatically once the build passes unchecked (the default) to review the pull request and activate it yourself, or check it if you want Ulika to finish by itself.

  2. Click Turn on live editing.

What happens next:

  • Ulika creates a branch (ulika/setup) and a pull request, and your host builds a preview.

  • With the box unchecked, Ulika merges the pull request once your host has built it, then checks your live site. If the live build fails, Ulika undoes the change automatically.

  • With the box checked, Ulika stops at Activate live editing. Click Activate on the live site when you are ready, or merge the pull request on GitHub with Prefer GitHub? Review and merge PR #N.

Vercel users may see an optional card, Connect Vercel to verify private previews. You can skip it. See Vercel to learn what it adds.

Read Approving a connection before you click if you want to understand exactly what you are agreeing to.

Step 6: open the editor#

When the connector is live you see Live editing is on. Click Open the editor.

If Ulika is still waiting for your live site, you see Approved. Checking that your site is editable…. Live editing turns on as soon as your site serves the connector. You can open the editor now; it does not need to wait.

Step 7: make and publish your first edit#

  1. Click a headline or a paragraph on your page and change the text.

  2. Click an image or a link to replace it.

  3. When you are happy, click Publish.

Your edit is a draft until you publish. After you publish, your host rebuilds the site, and visitors see the change. On a Vite or React site, the instant-publish script can show the change to visitors while the rebuild is still running.

Learn more in The editor and Publish.

If something stops#

Ulika always tells you what stopped and what to do. The most common stops are:

You seeWhat to do
We couldn't reach this websiteCheck the spelling and that the site is public over https.
Which GitHub account is this website on?Choose the account that owns the repository.
Add a repository to continueAdd the repository on GitHub, then return.
Ulika cannot write to this repository yetAccept Ulika's new permissions on GitHub, then check again.
Connect Vercel firstYour connector needs a Vercel connection. See Vercel.

For the full list, see Connection problems.

Next steps#

  • Learn the editor and the style panel.

  • Invite your team with invitations.

  • Prefer a terminal or an AI agent? Read Connect with the CLI or Connect with AI agents.

Was this page helpful?

PreviousRequirementsNext Connect from the dashboard

On this page

  • Before you begin
  • Fastest path: one command
  • Step 1: create your account and workspace
  • Step 2: start connecting
  • Step 3: connect GitHub
  • Step 4: pick the repository
  • Step 5: turn on live editing
  • Step 6: open the editor
  • Step 7: make and publish your first edit
  • If something stops
  • Next steps
Ulika documentationFAQ · CLI reference · Terms · Privacy