Skip to main content
For quick reversals — last prompt, last edit — use Undo / Redo. For anything bigger, use Version history.

Keyboard shortcuts

Undo / redo work across the editor, the live preview, and visual edits.

What undo reverts

Schema migration caveat

Undoing a schema-changing prompt restores the code but leaves the database with the new schema. The orphan field is harmless (no code references it) but stays until the next migration. For destructive schema changes (renames, drops), undo will warn you and walk through the cleanup. See Convex migrations.

Tips

Undo + Redo + Version history work together. Undo for the last 5 minutes; version history for older changes. Redo restores after an Undo if you change your mind.
Undo is per-user on multi-user projects. If your teammate prompted last, Cmd+Z undoes your last action, not theirs. Use version history to undo cross-user.

Version history

For changes older than the last few actions.

Rollback

For undoing a production deploy.

Branching

For experimental changes you might discard.
Last modified on April 18, 2026