Claude Code Checkpoint vs Git Commit
People think a Claude Code checkpoint is a git commit. It is not. A checkpoint is a save point Claude Code makes on your computer at each prompt, so you can rewind a bad edit. It is kept for about 30 days, and it misses changes made by shell commands. A commit lives in git, is shared with your team, and stays until someone removes it.
Claude Code Checkpoint
A save point Claude Code makes at each prompt, so you can go back.
A checkpoint is a restore point Claude Code makes each time you send a prompt. Before Claude edits a file, it keeps a copy of the file. Press Esc twice, or run /rewind, to go back to an earlier point. You can restore the code, the conversation, or both. Checkpoints are saved with the session, so a resumed session can still rewind. They do not undo changes a shell command made to files Claude never edited with its own tools.
Commit
A saved snapshot of your project, with a note saying what changed.
A commit is a saved snapshot of your project at one moment. It holds the staged changes, a short message, the author's name and the time. Each commit gets a unique code, like 93eadff, so you can find it later. Commits link to the one before, which makes a chain that is the project's history. A commit lives only on your computer until you push it.
In one line
- Claude Code Checkpoint
- A save point Claude Code makes at each prompt, so you can go back.
- Commit
- A saved snapshot of your project, with a note saying what changed.
These live in different corners of the glossary (AI and Development), which is exactly why they get confused.