Checkpoints and rollback

Checkpoints help undo a group of session changes. By default, Mogick creates a checkpoint before each run and captures affected file content before modification. It does not snapshot the entire project.

Rewind in the TUI

1. Wait for the current run to finish, or press Esc and wait for cancellation to complete.
2. Enter /rewind and select the point to return to.
3. Check the result, workspace files, and remaining conversation.

Restore truncates history after the selected point and restores files according to captured content and conflict protection. The first user message after that point is placed back in the input box so you can edit and resend it.

A running session cannot be restored. Paths written by another session are protected; conflicts may limit or skip file restoration. A rewound conversation does not prove that every file was restored.

Automatic checkpoints

Set this in the effective config.json:

{
  "session": {
    "checkpoint_auto_before_run": true
  }
}

The default is true. Setting it to false stops automatic per-run checkpoint creation. See Data directories for configuration paths.

The 26.9.11 CLI has no subcommands for manually creating, listing, or restoring checkpoints. Use TUI /rewind; do not use sessions checkpoint or its restore flags from older documentation.

Restore scope

• Only captured changes eligible for restoration are covered. Arbitrary shell effects, external-system actions, and untracked files are not guaranteed to be undone.
• History truncation and file restoration are separate effects. Check both when conflicts occur.
• Checkpoints do not replace Git branches or project backups. Keep a recoverable copy before important operations.

Inspect changes with Changes and Review, or save the conversation using Session export.