Checkpoints automatically save snapshots of your workspace after each step in a task. This feature lets you track changes, roll back when needed, and experiment confidently with your code.

​
How Checkpoints Work

Sixth creates a checkpoint after each tool use (file edits, commands, etc.). These checkpoints:
  • Work alongside your Git workflow without interference
  • Maintain context between restores
  • Use a shadow Git repository to track changes
For example, if you’re working on a feature and Sixth makes multiple file changes, each change creates a checkpoint. This means you can review each modification and, if needed, roll back to any point without affecting your main Git repository.

​
Viewing Changes & Restoring

After each tool use, you can:
  1. Click the “Compare” button to see modified files
  2. Click the “Restore” button to open restore options
Checkpoint comparison and restore options

​
Restore Options

To restore to a previous point:
  1. Click the “Restore” button next to any step
  2. Choose from three options:
    • Restore Task and Workspace: Reset both codebase and task to that point
    • Restore Task Only: Keep codebase changes but revert task context
    • Restore Workspace Only: Reset codebase while preserving task context
Example: If Sixth makes changes you don’t like while styling a component, you can use “Restore Workspace Only” to revert the code changes while keeping the conversation context, allowing you to try a different approach.
Checkpoint restore demo

Reverting both codebase and task to before any changes were made to start fresh

​
Use Cases

Checkpoints let you be more experimental with Sixth. While human coding is often methodical and iterative, AI can make substantial changes quickly. Checkpoints help you track these changes and revert if needed.

​
Using Auto-Approve Mode

  • Provides safety net for rapid iterations
  • Makes it easy to undo unexpected results

​
Testing Different Approaches

  • Try multiple solutions confidently
  • Compare different implementations
  • Quickly revert to working states
  • Ideal for exploring different design patterns or architectural approaches

​
Best Practices

  1. Use checkpoints as safety nets when experimenting
  2. Leverage auto-approve mode more confidently, knowing you can always roll back
  3. Restore selectively based on needs:
    • Use “Restore Task and Workspace” for a fresh start
    • Use “Restore Task Only” to try different prompts, but keep file changes
    • Use “Restore Workspace Only” to attempt different implementations while preserving conversation context

​
Relationship with Message Editing

The message editing feature uses checkpoints under the hood when you select the “Restore All” option. This allows you to not only edit and resubmit your message but also restore your workspace to the state it was in at that point in the conversation.

​
Deleting Checkpoints

You can delete all checkpoints by using the “Delete All History” button in the task history menu. Note that this will also delete all tasks. Checkpoints are stored in VS Code’s globalStorage.