Versions, undo, and retry
Step through your edit history and recover from failed generations.
Every message that changes your site creates a new version. Versions are how you roll back, compare, and recover — nothing you do in the editor is destructive.
Undo and redo
The toolbar has Undo and Redo buttons (keyboard shortcut friendly in a future update). Each click steps through one version:
- Undo — go back to the previous version. The preview and the “current version” pointer move back, but the chat history stays intact.
- Redo — go forward again.
You can undo past multiple edits, all the way to the original generation. Undo works after publishing too — you won’t affect the live site until you publish again.
Branching off a previous version
If you undo to a previous version and then send a new change request, the new edit is based on the version you undid to. It effectively branches the timeline from that point. The older “forward” versions are still there in Redo, but future edits follow the new branch.
Retry
Sometimes a generation fails — the AI runs out of turns, or hits an unexpected error. When that happens you’ll see a Retry button in the chat. Retry re-runs the last message with a fresh attempt.
What happens to my chat history?
Nothing. Undo, redo, and branching only affect versions. The full chat history is preserved — scroll up to load older messages at any time.
Best practices
- Undo is cheap; rewriting isn’t. If an edit doesn’t work, undo and try a better prompt rather than patching on top.
- Ask in chat after a failed generation if you don’t know why it failed. PageFork can often explain.
- Publish the version you like. Publishing snapshots the current version; editing afterwards is safe.