Docs · Use Caelo
Live editing
Live edit shows your real site with an AI chat on top. Point at something, say what should change, and look at the result. Nothing goes live until a person publishes.
What you see
Open Live edit (/edit) and the admin shows your actual site, full width, the way a visitor sees it. A chat window floats on top. You can drag it, pin it to the bottom or the right edge, or collapse it.
The slim toolbar above the page holds:
- a link back to the admin and the address of the page you are on;
- Edit elements, which turns element selection on and off (below);
- Diff, a side-by-side view of the current site next to your pending edits;
- a page picker (Switch page…);
- a status switch for the current page: Draft or Published;
- the pending-changes count, Stage and Publish live, and a link to the staging preview.
Editing by talking
Type what should change, in your own words. "Make the headline shorter." "Add a section about pricing below the features." "Move the about page under Company." You do not need to know how the site is built. The AI picks the right modules, fields and tools, and the preview reloads with the change.
Nothing you change here is live yet. It lands in the site's shared draft. How it gets to visitors is explained in Drafts, staging, publishing.
Pointing at an element
Click Edit elements in the toolbar. The button turns blue and reads Editing — click an element. Now a click on the page does not follow links. It selects the part of the page under the cursor and adds it to the chat message as a chip. Click several parts to collect several chips, then write what should happen to them: "make these the same colour". The AI limits its next edit to what you selected.
Click the button again to switch back. Then the page behaves like the live site: links navigate and scripts run. When you follow a link to another page, the editor follows along.
Cmd+M (or Ctrl+M) opens the media picker and puts the chosen image into your message.
Chats
The chat window has a chat list and a menu to start a new chat. A new chat starts without the earlier conversation, so start one for each new task.
All chats work in the same shared draft, so two chats see each other's unstaged changes. If you want to try something without affecting anyone, choose New experiment (own branch) from the chat menu. Details in Drafts, staging, publishing.
Stopping the AI, and other agents
Stop ends the AI's work in this chat on the server, not just in your browser tab. Helpers the AI started for the task stop too. Nothing restarts the AI by itself. It continues when you send your next message, or when you answer one of its approval cards.
Above the message box, Agents running lists everything working in this chat: Caelo's AI, its helpers, and an external agent connected over MCP. Each has its own Stop. One agent works in a chat at a time. A stopped external agent stays blocked in that chat until you click Allow again.
To take back what an agent already did, ask the AI to undo this chat.
Approvals in the chat
Some actions are hard to undo, such as a new layout, a theme switch or moving many URLs at once. For those the AI pauses and shows an approval card. Nothing happens until someone with the right permission clicks Approve. Open requests also show in a Pending your approval strip above the message box.
Quality check results
After a Stage, the result of the quality check appears in the same chat. If there are problems, a card asks first: Fix all with AI, fix or accept one group of findings, or Not now. The AI does not start fixing on its own. See Quality gate.
What steers the AI
- Site memory (Settings → Site memory): brand voice, words to avoid and standing instructions. The AI reads them in every chat.
- Skills: know-how for specific tasks, such as translating a page or migrating a site. They switch on by themselves when they fit.
Without the browser
The same tools are available to external agents over MCP. Their changes land in the same draft and the same chat history. Publishing stays with a person.
Something wrong or missing on this page? Open an issue on GitHub