Undo & Redo
ModZ to undo, ModShiftZ to redo, almost everywhere.
Two kinds of history
Section titled “Two kinds of history”In the text editors (manuscripts, notes, entity content), undo is the classic typing history you know from every editor.
Everywhere else, each surface keeps its own undo history:
| Surface | What’s undoable |
|---|---|
| Tables | Cell edits, add/delete rows, column changes, resizing, reordering |
| Kanban | Cell edits, card moves, column resizing |
| Project Database | Name/color edits, property changes, relationship add/remove, row create/delete |
| Mindmap | Node moves, add/delete, resizing, sticky-note and text-card edits, turning a text card into a page, paste, connection add/delete, line names, turning a line into a relationship |
| Map | Pin and zone create, edit, move and delete |
| Timeline | Date changes, label edits, card create/delete |
| Story outline | Everything: applying a template, beats added, deleted, retyped, dragged or moved between parts, parts added, renamed, recoloured, reordered or deleted, boundaries dragged, storylines created, edited or deleted, beats put on or taken off a thread, links and manuscript placements, tension |
Because each surface has its own stack, undoing on a mindmap never reverts a table edit you made earlier.
Good to know
Section titled “Good to know”- Typing keeps its own undo. In a text box (a beat’s sentence, a part’s name, a storyline’s paragraph), ModZ undoes what you typed, the way it does anywhere else. The surface’s history takes over again once you leave the field.
- Undo histories are kept while the view is open. Navigating away from a table or canvas clears its history.
- Manuscript formatting changes aren’t undoable; adjust them back in Format manuscript.
- Deleting items in the sidebar isn’t undone with ModZ. Restore them from the Trash instead.