# Undo & revert

> Roll the project back to before the last AI change — one word in chat, no confirmation dance.

Source: https://knowledge.estage.com/capabilities/undo/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
## How to trigger it

Just say so in chat — for example *"undo"*, *"undo that"*, *"revert"*, *"roll that back"*, or *"go back to before that change"*. No special syntax needed.

Or click the **Undo** button in the toolbar after an AI change.

## What happens

Genesis restores your project to the exact state it had **before the most recent AI turn** —
instantly, with a confirmation like *"Reverted the previous turn (7 files restored)."* If
there's nothing to undo, it says so.

Saying **undo again** steps back one more turn — you can walk back through several changes.

## Choosing what to revert

The chat command always targets the *latest* turn. To undo a specific earlier change, use the
**±N files** checkpoint on that exact message in chat history — or restore a full snapshot
from [Version History](/workspace/version-history/). The three levels compared:

| Tool | Scope |
| --- | --- |
| Asking to undo in chat / toolbar button | The last AI turn |
| Checkpoint on a chat message | That specific turn |
| Version History | The whole project, any snapshot |

## Notes

- Reverting is itself safe — the state you reverted *from* remains in Version History.
- Phrases like "go back" alone are ambiguous (could mean navigation) — use the words above to
  be unambiguous.