Drafts and approvals

The AI works fast. You decide what goes live.

Every change lands in a draft you can review. Changes that are hard to undo wait for a click from someone with the right permission. Everything else you can undo: per chat before it goes live, from the history afterwards.

Drafts, staging, publishing

See it

Change one thing, then take it back

Real screenshots from Caelo on a small demo site, Harbour Yoga. One request, one click on Publish live, one undo.

  1. Caelo Live Edit on the Harbour Yoga demo site: the hero section is selected and attached to the chat as a reference.
  2. The editor types the request into the chat: make the hero warmer and add a Sunday class to the schedule.
  3. The draft shows a warmer hero and the new Sunday class; in the chat the AI lists what it changed and what it left alone.
  4. After the click on Publish live, a notice confirms that the change is published to production.
  5. The editor asks in the chat to bring the previous hero back and keep the Sunday class.
  6. The hero is back to its original look while the Sunday class stays; the AI explains what it restored.

Screenshots from Caelo 0.10.52, October 2026. The demo site runs locally; the conversation is real.

Approvals

Some changes wait for your click.

When the AI wants to do something that is hard to undo, it stops and shows an approval card in the chat. Nothing happens until someone approves, and nobody can approve what they would not be allowed to do themselves.

  1. Draft
  2. Staging
  3. Live, by your click
On the pageSwitch on Edit elements, click a part of your real site and describe the change. For editors who never want to see a back end.
In the chatCaelo's own assistant builds pages in your design. It also works from Claude Code or Claude Desktop with nothing but a token.
With your agentConnect Claude Code or your own system through the Power-MCP. It gets the same tools as Caelo's assistant, under the same rules.

See it

The AI asks before it changes the whole site

Switching the theme touches every page. The AI prepares the change and waits; nothing happens until a person approves it.

  1. Before switching the whole site to an autumn theme, the AI asks for approval; the card in the chat offers Approve and Reject.
  2. After the approval the Harbour Yoga site shows the autumn theme with warm sand and rust colours.

Same demo site, same Caelo version. Today the card names the action; a preview of what it affects is planned (issue #813).

From draft to live

Five steps, one of them is always yours.

The AI may stage its own finished work and read the quality check. The last step stays with a person.

Publishing in detail
DraftEvery change lands in one shared draft. Visitors see nothing of it.
ExperimentWant to try something bigger? An experiment runs on its own branch and stays out of everyone's way.
Open changesOne list of everything not yet staged, chat by chat: stage all, stage some, or discard.
StageBuilds the staging site and runs the quality check. Staging is never indexed by search engines.
Publish liveA person's click, by someone with the right to publish. The AI and external agents cannot do it.

What waits

About 50 actions always wait for a human click.

These are the changes you cannot take back with one more call. Each request gets its own card, and there is no automatic approval.

PeopleNew users, roles and their permissions.
The whole siteLayouts, templates, themes and rolling the site back to an earlier state.
AddressesDomains, URL migrations, moving ten or more URLs, deleting five or more pages.
Code and keysPlugin settings, the AI provider, MCP tokens and email settings.

Undo

A mistake is undone, not repaired.

Every change is recorded. Drop a chat's changes before they go live, or roll a page back from its history afterwards.

Before it goes liveAsk the AI to undo this chat, or discard it under Open changes. What that conversation changed and did not stage yet is taken back. If another chat already built on it, Caelo asks first.
HistoryEvery change is saved. Pages, modules and templates each keep their history.
After publishingRestore an earlier version of a page, a module, a template or the whole site from its history. If you ask the AI instead, it prepares the revert and an owner or admin approves it in the chat.

Next

See where your site is built.

The admin and the database never sit on the server your visitors reach.

SecurityLive editing