Skip to main content
Checkpoints are automatic snapshots of your workspace taken as Sixth works. They let you see exactly what changed at each step and roll back your files, the conversation, or both.

​
How checkpoints work

Sixth saves a checkpoint after each change it makes (file edits, commands and so on). Checkpoints are kept in a separate shadow Git repository, so they never touch your own Git history, branches or staging area. In the chat, each checkpoint is a thin line: Checkpoint ────────── Compare · Restore

​
Comparing

Click Compare to open a diff of everything that changed since that checkpoint.

​
Restoring

Click Restore and choose: After Restore files, the checkpoint line is marked (restored).
Use Compare first to check exactly what a restore will undo.

​
Editing a message

Clicking one of your earlier messages lets you edit and resend it from that point. Press Enter (Restore chat) to roll back just the conversation, or ⌘/Ctrl + Enter (Restore all) to also restore your files to that point. See Editing messages.

​
When to use them

  • With auto-approve: let Sixth move fast, knowing any step can be undone.
  • Trying alternatives: restore files and ask for a different approach.
  • Exploring prompts: restore the task only to try a different instruction while keeping the file changes.

​
Turning checkpoints off

Checkpoints are on by default. Turn off Enable Checkpoints under Settings → Features if you don’t want them; because they use Git under the hood, very large workspaces can be slow to snapshot.

​
Deleting checkpoints

Checkpoints are stored with your task history in VS Code’s global storage. Deleting a task from history deletes its checkpoints too; Delete All History removes all of them.