Docs · Use Caelo

The Caelo admin

The admin is where you and your team work on the site. Most work happens in Live edit, by talking to the AI. The other areas are for reviewing, checking and configuring.

First login

The installer ends by printing a one-time setup link (/setup?token=…). It is valid for 24 hours. Open it, and you create the Owner account with your own password. There is no default password and no shared admin login.

Right after that, Caelo opens /welcome/ai. You pick an AI provider, paste its API key and choose a model:

  • Anthropic (Claude)
  • OpenAI
  • Google (Gemini)

A local, OpenAI-compatible endpoint and further model settings are under Settings → AI provider & models (/settings/ai). Until a provider is set, the admin sends you back to this page. After that you land in the chat, and most of the rest happens there.

If you forget your password, /forgot sends a reset link. Without an email transport set up, that link is written to the server log instead.

The main areas

The sidebar shows only what your role allows. An editor without settings rights does not see Settings, for example.

AreaWhat it is for
Dashboard (/)The starting page after login.
Live edit (/edit)Your real site with the AI chat on top. This is where most editing happens. See Live editing.
PagesAll pages as a tree, with search, status and each page's location, history and SEO fields.
ModulesThe building blocks pages are made of: a header, a hero, a pricing table. Each has its own history.
Content libraryContent shared between pages. Edit a shared item once and every page that uses it updates.
MediaImages and files, with upload, alt texts and usage.
TemplatesPage types, such as a blog article or a product page.
ChatsAll chats, including chats that are not tied to one page.
Open changesEverything not yet staged, chat by chat. See Drafts, staging, publishing.
Fonts, ThemesThe site's typography, colours and brand assets such as the logo.
DeploymentsDraft, staging and live, with promote. Rolling the live site back to an earlier build goes through the AI, with an approval in the chat.
QualityResults of the quality check, accepted findings, and every "publish anyway" decision. See Quality gate.
Detected bugsProblems the AI noticed in Caelo itself while working, ready to report.
SettingsSite, publishing, AI, plugins, people and approvals (below).
AccountYour own login and profile.

Users who can change settings also see Ramp up, a step-by-step wizard that fills a new install from an existing website. The chat route described in Moving an existing site is the usual way to do that.

Cmd+K (or Ctrl+K) opens a command palette to jump to any area.

Settings

Settings are grouped by topic. Find a setting at the top searches all of them.

  • Site: site defaults, SEO and site identity (public address, language, sitemap), layouts, menus and other structured data, redirects, media delivery, site import.
  • Domains & publishing: domains and SSL, DNS records with a live check, staging access, deployments, quality checks, Caelo updates.
  • AI assistant: provider and models, AI spending, spending limits, model prices, site memory (brand voice and standing instructions), skills, background AI runs, external AI tools over MCP.
  • Plugins: turn plugins on or off, approve what they may access, and the inboxes for forms, comments, newsletter and ratings. See Plugins.
  • People & access: users, roles and visitor accounts.
  • Approvals & safety: pending approvals, public form protection, detected bugs, usage data sharing (opt-in).

Where the AI works

The AI is in two places in the admin: the chat overlay in Live edit, for work on pages, and Chats, for work that is not about one page. A third way in, from outside the browser, is MCP, which connects Claude Code or another agent.

You can also ask the AI about the admin itself, for example to invite a user, change a spending limit or find out which version runs. Many of those changes wait for your approval (next section).

What the AI cannot do alone

  • Publish live. The AI may stage its work. Publish live is always a human click.
  • Hard-to-revert actions. About 50 actions always wait for a human click on an approval card in the chat: layouts, templates, themes, plugins, URL migrations, users, roles, site-wide undo, email, AI provider, MCP tokens, domains, Owner settings and basic SEO settings. The person who clicks Approve needs the same permission the action itself requires.
  • Activate plugins. Only an Owner activates a plugin or grants it access.
  • Install Caelo updates. The AI can say which version runs and whether an update is out. Only the Owner installs one.

Every change is saved as a snapshot, so it can be undone. How that works is in Drafts, staging, publishing.

Something wrong or missing on this page? Open an issue on GitHub