How to Undo Changes and Restore Versions in ChanTan Studio
ChanTan saves a version every time it works, so nothing you do is permanent. Learn Undo, Redo, undoing one specific change, and restoring any earlier version.
Nothing you do in ChanTan is permanent. A version of your project is saved automatically as it works, and again before every direct edit you make yourself.
If a change made things worse, you can always step back.
1. Find the Undo button
Look under the message box, on the right of the small footer row. There sit "Undo" and "Redo".
"Undo" only appears when there's an older version to go back to. "Redo" only appears after you've already stepped back.
2. Press "Undo"
A confirmation always appears first, so an accidental click can never move your project.
"Undo one version?" "This rolls your project back to the previous version. Your preview and files will be restored to that earlier state." "Your current files are saved first, so you can step forward again with Redo."
3. Confirm and watch it land
You briefly see "Rolling back one version..." and then your app reloads.
✅ Done! Your preview on the right now shows the earlier state — and so do your files. Everything you can see is restored: your code, your text and the real photos. If you replaced a picture and pressed Undo, the old picture genuinely comes back on screen, not just the old code.
Changed your mind? Press "Redo" to step forward again.
Undo never wastes a click: it skips over versions that are identical to what you already have, so one press always lands on a state that visibly differs.
Undo one specific change
You don't have to walk back step by step.
- Hover over the ChanTan reply that made the change you regret.
- A small "↩ Undo" appears in its corner — always visible on phones.
- Press it and confirm.
That rolls back to the version saved with that exact message. The button is hidden while ChanTan is working.
Open Version History
The "Version History" bar at the top of the chat column opens the list of saved versions, so you can see what was kept and when.
From there you can:
- Preview any version — an amber banner warns you: "Previewing old version — this is NOT the current state", with "Back to current" to return. Click-to-edit is switched off while you're looking at an old version, on purpose.
- Restore a version with its restore arrow.
- Pin a version so it's protected from cleanup, rename it, or delete it.
- "Restart preview" — free and safe, and unrelated to versions.
What gets a version saved
| When | Saved? |
|---|---|
| Every build run by the AI | Yes, automatically |
| Every direct edit you make by clicking | Yes — saved before the edit is written |
| Text, colour and photo changes | Yes, including the actual image |
| Your app's data (records, app users, orders) | No — data is not part of code versions |
Open the "…" receipt on any reply to see whether it saved one: "Version saved — you can undo anytime".
Messages you may see
| Message | What it means | What to do |
|---|---|---|
| "Already at the earliest version." | Nothing older exists | Nothing to do |
| "Nothing to redo." | You're on the newest version | Nothing to do |
| "Undo failed." / "Redo failed." | The step didn't apply | Try again — your project is untouched |
| "That version is no longer available" | That saved version has been cleared away | Pick a more recent one from Version History |
If Undo and Redo are greyed out or missing
Greyed out means ChanTan is working right now, or your live preview is still starting. Wait a few seconds and they come back.
Missing entirely means there's nothing older to undo to, or nothing newer to redo.
Honest limits
- A new build after an undo clears the redo path. Step back, then build something new, and you can no longer step forward to what was there before.
- Your app's data is separate from code versions. Undo restores the app; it doesn't restore records your app saved. App data is backed up daily, but there is no self-service restore button for it — ask in the chat or contact support.
- Undo is safe by design: your current files are always saved before rolling back, so a wrong Undo is itself undoable.