How to See and Undo What Claude Changed in ZartonAI
Every Claude session is a checkpoint and every post or product keeps its history — so you can see who changed what and put it back in one step

You asked Claude to “tidy up the service descriptions” on your website before heading out to a panel upgrade. By lunch your office manager calls: the prices on three services look wrong, and a blog post you liked has a new title. Was that Claude, or someone on the team? And how do you put it back without retyping everything from memory?
This guide shows you how to see and undo what Claude changed in ZartonAI. You will learn how every Claude session becomes a checkpoint you can look back on, how to read the version history of a single post or product to see who changed what, and how to restore one entry — or undo a whole session — in one step. It is the safety net that makes it reasonable to hand real work to an AI assistant.
Why an undo button matters when AI does the work
Owners of electrical, plumbing, HVAC, auto body and contracting businesses don’t have time to double-check every edit. The whole point of working through Claude is that you say what you want in plain words and it gets done. But a request can be misunderstood, and a small slip — the wrong product, a price typed into the wrong field — can sit on your live website for days.
ZartonAI keeps a record of the changes so you don’t have to. Two things work together:
- Checkpoints. Each Claude session in a project is listed as a checkpoint: when it began, when it was last active, who it was acting for, how many changes it made and which entries it created. Undoing a checkpoint puts your websites and content back to how they were when that session started.
- Version history. Every content entry — a blog post, product, service, event and so on — keeps its earlier versions. Each version shows when it was saved, who or what made the change (the editor, Claude, the assistant or an import) and what the changed fields held before.
How to see and undo what Claude changed in ZartonAI, step by step
- List the recent Claude sessions. Start by looking at the checkpoints for your project, newest first. Each line tells you when the session began, its last activity, who it acted for and how many changes it made. If your office manager noticed the problem after lunch, the session from that morning is the one to look at.
- Check what the session touched. A checkpoint shows the number of changes and the entries it created. A session with two changes is a quick check; one with forty deserves a careful look before you decide anything. Ask Claude to describe the session in plain words so you know exactly what is on the table.
- Open the history of the entry that looks wrong. When only one thing is off — a product price, a post title — go to that entry’s version history. You will see its versions newest first, each with the time, who or what made the change, and the values the changed fields had before. You can look back up to 50 versions.
- Find the version from just before the mistake. Read down the list until you reach the change you did not want. The version to restore is the one saved before it. Don’t retype the old values by hand — restoring brings back exactly what was there, including details you might forget.
- Restore that one entry. Restoring puts back the entry’s fields, text, SEO title and description, dates, status, categories, relations and media as they were in that version. ZartonAI saves the current version first, so the restore itself can be undone. If the entry is published, the live site changes straight away.
- Or undo the whole session. When a session went wrong from start to finish, undo its checkpoint instead of fixing entries one at a time. Your websites go back to how they were — both live and draft — when the session began, every entry it changed goes back to its earlier version, and entries it created move to the trash. Visitors see the result at once.
- Check the result, and know you can go forward again. Look at the page or entry the way a customer would. Every step of an undo is kept as a version, so if you undid too much you can restore the newer version again. Nothing is lost by trying.
Which undo to use
| Situation | Use | What changes |
|---|---|---|
| One post, product or service is wrong | Restore an earlier version of that entry | Only that entry; the current version is kept first |
| A whole Claude session went wrong | Undo the session’s checkpoint | Websites (live and draft) and every entry it changed; entries it created go to the trash |
| A page, menu or theme change broke the site | Roll back to an earlier website release | Pages, header and footer, menus and theme |
Website releases and rollbacks are covered in our guide on how to publish, undo and roll back website changes in ZartonAI.
Tips and common mistakes
- Use the smallest undo that fixes the problem. If one price is wrong, restore that product. Undoing a whole session also reverses the good changes it made.
- Look before you undo. Read the checkpoint or the version list first, so you know what will go back. An undo is reversible, but a published entry changes on your live site the moment you restore it.
- Restore the version before the mistake, not the mistake itself. Each version shows what fields were before that save. Pick the one from just before the unwanted change.
- Remember that new entries go to the trash, not away for good. Undoing a session moves the entries it created to the trash rather than wiping them out.
- Keep “Allow actions” for people you trust. Restoring a version and undoing a session change what customers see, so they only work through Claude when actions are allowed. Pair that with sensible team roles and permissions.
Do it with Claude
ZartonAI works with Claude through the Zarton connector, so you can ask about changes in plain language. Claude reads the history first and tells you what each version or session holds before anything is put back. Restoring a version and undoing a session change your live content, so they only work when you have switched on “Allow actions” for the connection. Try requests like:
“What did Claude change on our site today?”
“Show me the history of the Water Heater Install product — who changed the price, and when?”
“Put the Panel Upgrade service back to how it was before this morning.”
“This morning’s session made a mess of the services. Tell me what it changed, then undo the whole thing.”
“I undid too much — restore the newer version of the spring tune-up blog post.”
Want more ways to hand work to Claude safely? See how to put your follow-ups on autopilot or search and create business documents.
Frequently asked questions
Can I tell whether a change was made by Claude or by someone on my team?
Yes. Each version in an entry’s history says who or what made the change — the editor, Claude, the assistant or an import — along with the time and what the changed fields held before.
What happens to pages and posts Claude created when I undo a session?
Entries the session created move to the trash, entries it changed go back to their earlier versions, and your websites return to how they were, live and draft, when the session began.
Can I undo an undo?
Yes. ZartonAI keeps the current version before restoring, and every step of a session undo is kept as a version, so you can restore the newer state again.
Does restoring an entry change my live website?
If the entry is published, yes — the restored version shows on the live site straight away. A draft entry stays a draft.
Let Claude do the work, and keep the undo button. Try ZartonAI and see every AI change, with a one-step way back.
Try it at zartonai.com











Comments
No comments yet — be the first to share your thoughts.
Join the discussion