Checkpoints & Rewind
Go back in time with session checkpoints and rewind functionality.
Overview
Checkpoints are snapshots of your session at specific points in time. They capture both the conversation state and the file changes made up to that point, letting you "rewind" to an earlier state if needed.
This feature is invaluable when:
- The agent makes changes you want to undo
- You want to try a different approach
- Something breaks and you need to recover
- You want to compare different solutions
Claude Code Only
Checkpoints & Rewind currently integrates with Claude Code's native checkpoint system. This feature is not yet available for OpenCode or Codex sessions.
How Checkpoints Work
Checkpoints are created automatically at key moments:
- After the agent completes a significant task
- Before major file modifications
- At regular intervals during long sessions
What's Saved
Each checkpoint captures:
- Conversation State — All messages up to that point
- File Changes — Git-tracked modifications since session start
- Tool Execution History — What tools ran and their results
- Timestamp — When the checkpoint was created
Storage
Checkpoints are stored as part of the session data and synced with Claude Code's native checkpoint system. This means checkpoints created in C3 are accessible from the desktop CLI and vice versa.
Rewind Options
When you rewind to a checkpoint, you choose what to restore:
Code Only
Reverts file changes to the checkpoint state while keeping the full conversation history. Use this when:
- The agent's code changes didn't work but the conversation is valuable
- You want to try a different implementation approach
- You need to undo accidental deletions
Conversation Only
Truncates the conversation to the checkpoint while keeping current file changes. Use this when:
- The conversation went off-track but the code is fine
- You want to restart discussion with the agent
- Context is getting full and you want to compact
Both Code and Conversation
Fully restores the session to the checkpoint state. Use this for:
- Complete do-over from a known good state
- Recovering from major mistakes
- Starting a new approach from an earlier point
Rewind Creates a Fork
When you rewind to an earlier checkpoint, the conversation after that point is saved as a separate fork rather than being permanently deleted. You can access forked conversations from the session list, but you cannot directly "redo" after a rewind.
Using Checkpoints
Opening the Rewind Panel
- Tap the Rewind button (clock icon) in the chat toolbar
- The rewind panel slides up showing your recent checkpoints
- The most recent checkpoint is marked with a "Latest" badge
Checkpoint Information
Each checkpoint in the list displays:
- Message Preview — The first part of your message at that point
- Timestamp — Relative time (e.g., "5m ago", "2h ago")
- File Changes — Number of files modified after this checkpoint
- Lines Changed — Lines added (green) and removed (red) since
Restoring a Checkpoint
- Tap on the checkpoint you want to restore to
- An action sheet appears showing your selected message
- Choose your restore option:
- Restore code and conversation — Rewind both to that point
- Restore conversation — Fork conversation, keep current files
- Restore code only — Revert files, keep conversation (only shown if files changed)
- Tap "Never mind" to cancel
After Rewinding
When you restore a checkpoint:
- For conversation restores, a new forked session is created automatically
- Your original message is pre-filled in the input, ready to edit or resend
- A success message confirms the restore completed
Bash Changes Not Tracked
Rewinding does not affect files modified via bash commands (like rm, mv, or cp). Only changes made through the agent's file editing tools can be reverted.
Automatic Safety Net
Checkpoints are created automatically at each of your messages, giving you a safety net if things don't go as planned. You can confidently try ambitious approaches knowing you can always rewind.