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

Projects

Project settings

Every tab of a project's Settings screen in Ulika: general details, repository, environments, integrations and the danger zone, plus how to change a project's repository.

Last updated October 10, 2026

Each project has a Settings screen for its name and details, the repository Ulika reads, where content is published, and the two actions that cannot be undone. Open your project and choose Settings in the project navigation. The heading shows the project's status next to it. A link can open a specific tab directly by adding ?tab= with general, repository, environments, integrations or danger.

Who can change settings#

Everyone in the workspace can open the screen. Only owners can change anything on it (the permission is called project settings and only the owner role has it). For everyone else the fields are disabled and the footer says "Only owners can change project settings." See Roles.

Tabs#

The tab strip scrolls sideways on a narrow screen. The tabs are General, Repository, Environments, Integrations and Danger zone.

General#

How the project is labelled across your workspace. The page says none of it touches your codebase.

SettingWhat it does
Project nameShown in the sidebar, the dashboard and the command menu. Required, up to 60 characters.
Website URLYour site's address, for example https://example.com. Used as the origin for SEO previews and canonical URLs. Must start with http:// or https://. It can be left empty.
DescriptionOne line so the rest of the team knows what the site is. Optional.
Accent colourOne of eight presets that tints the project's avatar so it is recognizable in a list: Indigo, Blue, Teal, Green, Amber, Crimson, Violet, Graphite.

The footer says "Unsaved changes." or "Everything is saved." Click Save changes to store them. On success you see "Project updated". The errors are:

  • "A project needs a name."

  • "Project names are capped at 60 characters."

  • "The website URL must start with http:// or https://."

  • "Pick one of the accent presets."

Note

Changing the project name does not rename your repository or your site, and changing Website URL here does not move your live site. It changes how Ulika labels and previews it. If your site's real address changed, see Frequently asked questions.

Repository#

Shows the codebase Ulika reads to find content.

  • The repository name as owner/name with a Connected or Disconnected badge.

  • The branch, the provider (GitHub, GitLab or Local checkout), and a "Built with" tag when Ulika knows which tool built the site (for example Claude Code, Codex, Cursor, Lovable or v0).

  • "Last synced" with how long ago, or "Never synced".

  • "Last webhook received:" with the time of the last signed GitHub webhook that reached Ulika. If requests arrive but fail the signature check it says "Last webhook received: never (requests arrived but failed the signature check)", which is the thing to check if GitHub events seem to be missing. See Troubleshooting GitHub.

Buttons:

  • Sync now (owners only). Refreshes the last-synced time. Per the current code, Ulika already read your code when you connected, and this action records a new sync time without changing any files. It is disabled when the repository is disconnected. Result: "Repository synced". If no repository is connected you see "Connect a repository before syncing."

  • Change repository (owners only). See Change the repository.

  • Open repo opens the repository on its host in a new tab.

Environments#

A read-only list of where published content is served. Each environment (production, and staging when present) shows the host (Vercel, Netlify or "No deploy target"), a link to its address, and "Deployed" with how long ago, or "Never deployed". There is nothing to edit here: environments come from your deployment connection. If none exist the screen says "No environments connected" and "Connect Vercel or Netlify so publishing has somewhere to land." See Connect Vercel.

Integrations#

A catalogue of what Ulika works with, in four groups:

GroupEntries
Source controlGitHub
DeploymentVercel, Netlify
Coding agentsClaude Code, Codex
ProtocolsModel Context Protocol

Each row shows a Connected badge, a Set up button, a Connect button or "Coming soon". The status comes from the project itself:

EntryShows Connected when
GitHubThe project has a connected repository.
VercelOne of the project's environments is hosted on Vercel.
NetlifyOne of the project's environments is hosted on Netlify. Ulika has no Netlify connection, so this does not normally happen.
Claude CodeThe project was recorded as built with Claude Code.
Codex and Model Context ProtocolNever. They run on your computer and Ulika cannot see whether they are installed, so they show Set up instead of a made-up connection.

Set up opens the exact commands for your Ulika address. Under Codex it shows the one-line setup command, "Run this once in your terminal, then restart Codex.", and the sentence to tell Codex. Under Model Context Protocol it shows setup for Claude Code, Codex, Cursor and other MCP clients, and the nine tools the server offers. Hide setup closes it. See MCP tools. Connect on an entry that is not connectable yet shows "is not connectable yet" with "Available in the next release."

Below the MCP setup, a line tells you whether an agent has used your workspace recently, for example "An agent last used your workspace 2 hours ago. Ulika cannot see whether MCP is installed on a machine, so this is not shown as connected." If none has: "Ulika cannot see whether MCP is installed on a machine, so it stays on Set up until you use it."

Note

For the real state of a connection, also use the Repository and Environments tabs and the connect pages: Connect from the dashboard, GitHub App and Vercel. The overview pages are GitHub, Vercel, Netlify, Claude Code, Codex and MCP. For the project's code, see Website code.

Danger zone#

Two actions, both immediate and neither can be undone from inside Ulika:

  • Disconnect repository: unlinks the repository.

  • Delete project: removes the project.

Both ask you to type the project's name. Details for deleting are on Delete a project. Only owners and admins can use them; for others the buttons are disabled with "Only owners and admins can disconnect a repository or delete a project."

Disconnect repository#

Description: "Unlinks owner/name. Content already detected stays editable and publishable, but Ulika stops reading the codebase, so new components will not appear."

  1. Click Disconnect.

  2. In the dialog titled Disconnect repository, type the project's name exactly where it says "Type (name) to confirm."

  3. Click Disconnect repository. You see "Repository disconnected" and "Detected content stays editable; the code link is gone."

The project's status becomes disconnected, and "Last synced" is cleared. The button then reads Not connected and is disabled. This only unlinks the code reading; it does not remove the connector from your repository or touch your site.

Change the repository#

If the project should read a different repository, use Change repository on the Repository tab. It always leads to the same page, and what you see depends on the project:

SituationWhat you see
You are not an owner"Only workspace owners and admins can change a repository." Ask an owner or admin. Nothing changes meanwhile.
The site is already live through UlikaA notice: "(your site) is already live through Ulika". Ulika does not swap the repository while the site is live, because the live content would end up attached to the wrong code: "Nothing was changed." The safe route is Connect a new repository, which sets up the other repository as a separate website and leaves this one untouched. Back to your website returns.
Connected through the Ulika GitHub AppA repository picker titled Change repository: "(owner/name) is the one in use. Choosing another one reads it from the start. Nothing in any repository is changed or deleted." Pick a repository and click Use this repository. Use Search your repositories, Add a repository on GitHub and Refresh list if yours is missing.
Linked to GitHub but needs a new sign-in"To pick a different repository, sign in to GitHub again so Ulika can list the ones it can see. Nothing is changed until you choose one and confirm." Click Continue with GitHub.
No GitHub repository at all"(project) has no GitHub repository to swap." Click Connect through GitHub.

Changing the repository needs the permission to create projects and the permission to change project settings, which only owners and admins have.

If a repository you want is not listed, GitHub has not shared it with Ulika yet. See GitHub App and Troubleshooting GitHub.

Other places that matter#

  • Team and invitations are covered in Roles and Invitations.

  • To remove the project completely, see Delete a project.

Was this page helpful?

PreviousInviting peopleNext Delete a project

On this page

  • Who can change settings
  • Tabs
  • General
  • Repository
  • Environments
  • Integrations
  • Danger zone
  • Change the repository
  • Other places that matter
Ulika documentationFAQ · CLI reference · Terms · Privacy