Troubleshooting
Frequently asked questions
Straight answers about what Ulika changes in your code, which frameworks it supports, how fast edits go live, who can publish, and how to leave.
Last updated
Short answers to the questions people ask most, each grounded in how Ulika actually behaves. Where a page has the full story, the answer links to it.
About Ulika#
What is Ulika, in one paragraph?#
Ulika is a visual CMS for websites built with AI tools or code. People edit text, images, links and styles directly on the live page and publish. The site's code stays in your GitHub repository. To make that possible, Ulika adds a small connector to the repository through a pull request. See How Ulika works.
Does Ulika work with my framework?#
Ulika installs its connector on:
Next.js sites that use the App Router, and
sites built with Vite or Create React App, and other sites with a Node build and static output.
Ulika can detect many other frameworks from a public page (Astro, Nuxt, SvelteKit, Remix, Gatsby, WordPress and more), but detecting a framework is not the same as supporting its connector. If a site is built with one of the others (or is plain HTML), Ulika says so before it creates anything: "Ulika can't install on <framework> sites yet. It supports React and Next.js." ulika init --local cannot install on it either (see CLI errors and exit codes). Check Requirements for the current list.
Which hosting do I need?#
Your site is built by your own host, not by Ulika. Ulika has the deepest integration with Vercel (it can set up the build token, deploy hook and preview checks). For other hosts it can follow builds through GitHub when the host reports them there, as Vercel, Netlify and Cloudflare Pages do. If your Vite or React site is not on Vercel, Ulika connects it through Git alone: a publish commits content to your repository and your host rebuilds. See Netlify.
Do I need to be a developer to use it?#
Connecting a site needs someone with access to the GitHub repository and an owner role in Ulika. After that, editors never need repository access: the Team screen says "Invite the people who write the copy. They never need repository access." See Team roles.
Your code and repository#
Does Ulika change my code?#
A little, and always visibly.
Installing the connector adds a few files in a
.ulika/folder, a config file and one edit that makes your host run the Ulika build step (or, for Next.js, a smallulikafolder, two routes and one line in your root layout). This arrives as a pull request on a new branch, with the full diff shown before anything is created. It adds no package dependency and no secret.Publishing (on sites connected with the current connector) commits one file,
.ulika/content.json, to your default branch.
Your own source files are not rewritten in the repository: at build time the adapter applies your published content, builds, and restores the files. Details: Security and privacy.
Does Ulika ever write to my default branch?#
Only for one file: .ulika/content.json, and only when someone clicks Publish. Installing the connector never touches your default branch until you (or an agent you approved) merge the pull request. Ulika never force-pushes, never deletes a branch and never rewrites history.
Will the connector break my build?#
Ulika is built to avoid it. It shows you the change first, builds a preview on your host, and reads the connector back from the preview before it merges. If the preview cannot be read (for example it is private), Ulika asks you to confirm, merges, then checks your live site and reverts its own change automatically if the production build fails. Your host keeps serving the previous deployment while a build fails. See Failed builds.
Can I keep working on my code as usual?#
Yes. Push, branch and deploy as you always do. If you change files the connector reads before the connector is merged, Ulika notices and asks you to re-scan (source-changed). Branch protection rules are respected: if your rules refuse a direct commit, a publish goes through a pull request instead. See GitHub problems.
What if I delete the connector?#
Do not delete only the .ulika/ folder. The connector also edits one build entry (vercel.json, netlify.toml or the build script in package.json) so that your host runs the Ulika build, which then runs your original build. Removing the folder and leaving that edit means your host tries to run a file that no longer exists, and the build fails.
The safe way to remove it is to revert the connector's pull request (revert the merge commit), which restores your original build setup and removes the files together. Then disconnect or delete the project in Ulika.
What does Ulika read in my repository?#
It reads a snapshot at one commit, in memory, only the source and configuration files it needs, within fixed limits. It never clones your repository, never runs your code and never keeps a copy. See Security and privacy.
Connecting#
How long does connecting take?#
The steps Ulika runs itself take a minute or two. The wait is your host building the preview: Ulika waits up to 30 minutes for the preview and up to 30 more after merging for your live site to serve the connector before it asks you to look. When you connect many sites at once, Ulika works on up to three at a time and paces its GitHub writes, so a big batch takes longer.
Do I have to merge the pull request myself?#
It depends on how you connect. By default Ulika opens a pull request and merges nothing until you activate it. Ulika prints one Activate link per site; in the browser you review the diff and click Activate on the live site. Add --auto-merge to a batch ulika connect (and tick the box on the approval page) to let Ulika merge by itself. 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. Single-site ulika connect <url> never merges by itself; run it again with --activate after reviewing.
Why does Ulika ask me which repository serves my site?#
Ulika never guesses. It only connects a URL to a repository when your host reports a production deployment for that address from exactly one repository, or the repository's own ulika.config.json says so. A name or homepage field is not enough, because anyone with write access can type those. A repository named like your address is offered as a candidate you confirm on the approval page. When it is not certain you get the exact command to run, with --repo owner/name. See Needs attention reasons.
Can I connect many sites at once?#
Yes: ulika connect --all, --urls <list> or --repos <list> connect many sites with one approval. --all shows you the list and asks you to confirm before writing anything. An agent can take on 50 sites in 24 hours by default (the approval can set a different number, up to 200).
Can I connect without installing the GitHub App?#
Yes, from the site's checkout on your machine: ulika init --local uses your own gh and vercel logins instead of Ulika's GitHub App. See Connect with the CLI.
Why can only owners and admins connect?#
Connecting installs files in your repository and links your hosting, so it needs the owner or admin role. An editor who opens the connect screen sees "Only owners and admins can connect a website".
Editing and publishing#
How fast do changes go live?#
Ulika shows a publish on your live site within a few seconds, before your host finishes rebuilding. A small script on the page asks Ulika once per page load for the latest published content (the answer is cached for about five seconds) and swaps in text, links, images and styles that have markers. The rebuild that follows (typically 30 to 50 seconds) carries the same values. After publishing you see "Live on your website. Search engines update in about 30 seconds." Some changes (collection items, page search data, fields without a marker) only show after the rebuild. See Publish.
Who can publish?#
Owners and editors. Viewers can preview but cannot publish. The permission table is on Team roles.
What happens to my drafts?#
Edits are saved in Ulika as you type (you see Saving…, then Saved, or Couldn't save with Retry), and they stay drafts until someone with publish access clicks Publish. Drafts never go to your repository: only the snapshot of a published release does. If a publish stops (a protected branch waiting for a merge, a build problem), your drafts stay saved. See Mobile, autosave and drafts.
Can I undo a publish?#
Yes. Open the project's history and restore an earlier version (owners and editors can). On sites that publish through Git, a rollback is a new commit with the older content, never a history rewrite. See Publishing history.
What if Ulika is unreachable when my site builds?#
It depends on how the site was connected. Sites connected with the current connector publish through Git: the published content is committed to your repository as .ulika/content.json, so your builds do not need to reach Ulika at all. Older connections fetch content from Ulika at build time with a token; if Ulika cannot be reached, that build fails with "Ulika content request failed" instead of publishing stale or partial content.
Does Ulika add anything to my visitors' pages?#
The connector's editor bridge does nothing for normal visitors: it only runs when your page is opened inside the Ulika editor. The instant-publish script is the one thing visitors' browsers run. It reads only published content, never drafts. You can turn it off per site with "live": false in .ulika/connector.json.
Team and access#
Can a client or colleague edit without seeing my code?#
Yes. Invite them as an Editor (edit and publish) or a Viewer (look only). They sign in to Ulika; they do not need a GitHub account or repository access. See Inviting people.
Can I give someone access to just one project?#
No. Roles apply to every project in the workspace. If a client needs their own space, give them their own workspace.
How do I remove someone's access quickly?#
Remove them from the Team table (Remove from workspace). Their access to every project ends immediately, their CLI sessions are revoked, and agents they approved are revoked too. Content they already published stays. See Team roles.
Security#
Does Ulika see my GitHub password or keep a long-lived key?#
No password: Ulika uses a GitHub App you install and limit to chosen repositories, and it asks GitHub for short-lived keys (about an hour) for each job. A key that can write is limited to one repository. See Security and privacy.
Can an AI agent publish or edit my content?#
No. An agent approved through ulika connect gets a token with two scopes only: connect sites and read their progress. It cannot publish, edit content, read drafts, invite people or manage tokens. It expires after 30 days, is revoked after 14 days unused, and you can revoke it any time in Settings under Agents. See AI agents.
Is my content public before I publish?#
No. Drafts stay in Ulika. Only published releases are visible on your site (and, for Git delivery, in .ulika/content.json in your repository, which is as public as the repository).
Does ulika logout revoke my access?#
It forgets the credential on that machine only. To cut off a machine you no longer trust, remove or re-role the person who approved it: their tokens stop working at once.
Leaving Ulika#
Can I stop using Ulika without losing my site or content?#
Yes. Your repository and your live site stay with you. On Git-delivery sites your published content is already committed in the repository as .ulika/content.json and builds do not depend on Ulika. To remove the connector cleanly, revert its pull request (see the question above), then disconnect or delete the project in Ulika. For an older fetch-delivery connection, revert the connector before deleting the project, since its builds still call Ulika.
What does deleting a project remove?#
Deleting a project (owners only, from the Danger zone in the project's settings) removes its fields, collection items, media records and versions, and releases the objects Ulika created on your Vercel project. It does not touch your repository or your deployed site, and there is no undo. Disconnect repository is milder: content already detected stays editable, but Ulika stops reading your code. See Delete a project.
Where do I get help when something stops?#
Start with Needs attention reasons, then Vercel problems, GitHub problems and CLI problems.
Was this page helpful?