Checkpoints

Checkpoints automatically snapshot your workspace before the agent acts on each user message. If the agent takes the task in a direction you didn’t want, you can restore to any earlier point and try again — file state and conversation history are both rewound together.

How Checkpoints Work

Each time you send a message, Kodik saves a snapshot tied to that message. The snapshot captures the content of every file the agent has touched. Checkpoints:

• Are taken automatically — no manual action needed.
• Do not interfere with your Git history. Snapshot storage is handled by a separate session layer.
• Track which files were created or modified so only the relevant files need to be rewound.

Checkpoints must be enabled in settings. When disabled, the restore action is blocked and a warning is shown.

Restoring to a Checkpoint

To restore to an earlier point in the conversation:

1. Find the user message you want to restore to.
2. Click the restore action on that message.
3. Kodik rewinds the conversation history to that message, restores file content from the saved snapshot, and clears any subsequent API context.

After a restore, the agent is ready to receive a new message from the restored point. You can edit your original message before re-sending it — see Editing Messages.

Relation to Auto-Approve

Checkpoints are especially useful with Auto-Approve mode enabled: the agent runs without interruption, so checkpoints are the primary way to undo a run that went wrong.

Use Cases

• Trying a different approach: restore to before an edit and give the agent a different instruction.
• Recovering from unexpected changes: if the agent modifies files you did not intend to touch, restore to just before that step.
• Experimenting safely: let the agent attempt something risky, review the diff, and restore if you don’t like the result.