Skip to content

Commit 7ea3831

Browse files
committed
Refine checkpoints documentation: clarify how snapshots are created and stored
1 parent de65bc3 commit 7ea3831

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

docs/advanced-usage/checkpoints.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,21 +27,16 @@ Access checkpoint settings in Roo Code settings under the "Checkpoints" section:
2727

2828
## How Checkpoints Work
2929

30-
Roo Code creates immutable snapshots of your project using a shadow Git repository that operates independently from your own version control system. These checkpoints capture the complete state of tracked files at specific points in your AI-assisted workflow.
30+
Roo Code captures snapshots of your project's state using a shadow Git repository, separate from your main version control system. These snapshots, called checkpoints, automatically record changes throughout your AI-assisted workflow—whenever tasks begin, files change, or commands run.
3131

32-
Checkpoints are automatically created when:
33-
- A task begins (initial checkpoint)
34-
- Files are created, modified, or deleted
35-
- Commands are executed
32+
Checkpoints are stored as Git commits in the shadow repository, capturing:
3633

37-
Each checkpoint is stored as a Git commit in the shadow repository, capturing:
3834
- File content changes
39-
- New files added to the workspace
35+
- New files added
4036
- Deleted files
4137
- Renamed files
4238
- Binary file changes
4339

44-
4540
## Working with Checkpoints
4641

4742
Checkpoints are integrated directly into your workflow through the chat interface.

0 commit comments

Comments
 (0)