Undo a change an agent made
An agent connected to BOLDCMS can say what it changed and put a page back the way it was. A restore always lands on the draft, so the live page keeps showing until you publish.
1. Find the change
What did agents change in
<your-project>since this morning?
The agent lists the changes made through MCP in that project, newest first. Each entry comes with the restore that undoes it, or the reason there is none.
To look at one page instead:
Show me the saved versions of the About page, and what changed in each.
Each version comes with its time, its status, its author where known, and a summary of the fields that changed.
2. See what the restore would do
Restore the About page to the version from yesterday at 14:00. Show me what would change first, and wait.
The agent asks for the restore without confirming it. Nothing is written; you get the exact difference the restore would make.
3. Restore
Apply it.
The page's draft now holds the earlier version. The live page has not changed.
4. Publish
Show me a preview of the About page, then publish it.
Visitors see the restored page from this point.
Limits
- Only pages, blog posts, services, portfolio items, events and forms have versions. Anything else has no history to restore.
- Only the 10 newest versions of a document are kept. A change older than that can still be listed, with no version left to restore.
- A restore puts back every language at once, because a version holds the whole document. A version older than one of its translations is refused instead of deleting that translation.
- A change made in the admin appears in the versions without an author, and does not appear in the list of agent changes.