Original explainer
Cline checkpoints: Compare and three restore choices
Inspect file differences before restoring files, the task or both, and distinguish checkpoints from Git and external actions.
Broken code and a conversation going in the wrong direction require different restoration choices. The official Cline checkpoint page provides Compare and three Restore options. The expected output is a decision record that preserves useful code or conversation. You need a Cline interface with checkpoints; no editor was started to verify these controls for this page.
Action and checking sequence
Compare changes
Use Compare to inspect changes associated with the checkpoint.[1]
Choose what to restore
Choose Restore based on whether files or conversation should be preserved.[1]
Check the resulting state
After restoration, inspect files and task state before continuing or committing.[1]
Checkpoints are separate from main Git history
The documentation describes a separate shadow Git repository that stores file snapshots after tool use without adding checkpoint commits to your main Git history. Checkpoints are enabled by default and can be toggled under Feature Settings → Enable Checkpoints. Large repositories can incur storage and snapshot overhead, so inspect performance in your own project when reviewing this setting.[1]
Compare before restoring
Find the Checkpoint indicator and Compare and Restore controls near a tool step. Compare opens a file diff in the editor. Original exercise: a change adjusts validation and error wording. Record which changes should remain before choosing a restoration point. A failing test does not automatically mean the later conversation should be removed.[1]
Three restoration targets
- Restore Files restores the file snapshot while keeping conversation, useful when the approach is valuable but the implementation needs another attempt.
- Restore Task Only removes later messages without changing files, useful when code should remain but the prompt needs a different direction.
- Restore Files & Task restores files and removes later messages, useful when restarting from a known state.
Before restoring, identify uncommitted files and manual changes you need to retain, and save a separate copy if necessary. These controls restore files and task state. Their presence does not prove that external service actions can be undone; handle remote reversal through the relevant service.[1]
After-restoration checks and page scope
After restoration, inspect working-tree differences, confirm the intended files and conversation remain, and run checks appropriate to the change before deciding on a Git commit. This page verifies documented interface paths and restoration semantics. It did not install Cline, create checkpoints, use Compare or Restore, or enable auto-approval. The exercise is not a claim that a project was successfully restored.[1]
Article sources
Original editorial content; official descriptions and checking suggestions are distinguished.
Tools in this explainer
Tool directory
Cline
A coding agent for reading and changing files and using tools in editors and terminals, with configurable model access.