Analysis updated 2026-05-18
Roll back both code and Claude Code session state after an AI edit goes wrong
Save frequent checkpoints during an AI coding session without polluting git log
Preview a restore with dry-run before actually rolling back files
Attach an exported AI conversation file to a checkpoint for reference
| mqz0211/claude-checkpoint-manager-ccm | 00kaku/wp-rest-playground | aaddrick/ticketmill | |
|---|---|---|---|
| Stars | 5 | 5 | 5 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | easy | hard | hard |
| Complexity | 2/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Beta software, requires Node.js 16+ and git on PATH, back up important work before relying on --prune restores.
Claude Checkpoint Manager, known by its command name ccm, is a command line tool that lets developers save and roll back both their code and the state of an AI coding assistant session together, specifically for people using Claude Code. The idea is that when an AI assistant makes a series of changes that go wrong, you can rewind your files and the assistant's session context back to an earlier known good point, without cluttering your project's real git history with a pile of experimental commits. It works by storing each checkpoint as a normal git commit, but hidden away on a special reference path that git's usual commands like git log and git status never look at, so your visible history stays clean while still benefiting from git's efficient storage, meaning unchanged files across checkpoints take up almost no extra disk space. Alongside your code, it also copies relevant session state files from the folders Claude Code stores its local data in, skipping anything that looks like it might contain a secret, password, or API key, and referencing rather than copying very large files. Using it involves running one setup command in a project, then saving a checkpoint with a short message whenever you reach a good point in your work. A status command shows a timeline of your checkpoints with file counts, sizes, and rough token estimates, and a restore command rolls your files and session state back to a chosen checkpoint. Restores automatically take a safety checkpoint of your current state first, so even a restore itself can be undone if needed, and there is a preview mode that shows what a restore would change without actually doing it. The project is installed by cloning its repository and running a couple of npm commands, and it requires Node.js and git to already be available on your computer. The author describes the project as still in beta, with the core commands implemented and tested but not yet used heavily in the real world, and recommends backing up anything important before relying on it.
A CLI that snapshots your code and Claude Code session together as hidden git checkpoints you can roll back to.
Mainly JavaScript. The stack also includes JavaScript, Node.js, Git.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.