A checkpoint system for Claude Code CLI that automatically tracks your coding sessions. Inspired by Cursor IDE's checkpoint feature - see everything you've done with Claude Code CLI and navigate through your conversation history.
CCheckpoints hooks into Claude Code CLI to automatically save checkpoints every time you interact with Claude Code CLI. It creates a timeline of your entire coding session that you can view in a beautiful web dashboard.
# Install globally
npm install -g ccheckpoints
# Run (auto-setup + open dashboard)
ccheckpoints
# or use the short alias
ccp
That's it! Running ccheckpoints
(or ccp
) will:
- β Auto-setup Claude Code hooks (if not already done)
- β Start the background server
- β Open the dashboard in your browser
- Automatic Tracking: Every time you send a message to Claude Code CLI, CCheckpoints saves it as a checkpoint
- Background Server: Runs quietly at
http://127.0.0.1:9271
to handle tracking - Web Dashboard: Beautiful interface to see all your checkpoints and sessions
- SQLite Database: All data stored locally in
%APPDATA%/CCheckpoints/
ccheckpoints
# or
ccp
This does everything - sets up hooks if needed and opens the dashboard.
ccheckpoints setup
# or
ccp setup
Only needed if you want to setup without opening the dashboard.
ccheckpoints show
# or
ccp show
Same as running just ccheckpoints
- opens the dashboard (with auto-setup if needed).
ccheckpoints --help
# or
ccp --help
ccheckpoints --verbose
# or
ccp --verbose
See detailed logs of what's happening behind the scenes.
- Every message you send to Claude Code CLI (submit event)
- Session stops (when you exit Claude Code)
- Timestamps for everything
- Full conversation context
Get a bird's-eye view of all your Claude Code CLI sessions. See when you started, how long you worked, and track your productivity patterns.

Every message you send to Claude Code CLI is saved as a checkpoint. Navigate through your entire conversation history with timestamps and full context.

See exactly what changed between checkpoints. Perfect for debugging when something breaks or understanding how your code evolved.

- Windows:
%APPDATA%/CCheckpoints/
- Mac/Linux:
~/.ccheckpoints/
Contains:
checkpoints.db
- SQLite database with all your datalogs/
- Debug logs (when using --verbose)
# Clone repo
git clone https://github.com/p32929/ccheckpoints.git
cd ccheckpoints
# Install deps
npm install
# Build
npm run build
# install globally
npm install -g .
# Now use it
ccheckpoints
npm run dev # Run without building
npm run dev:watch # Auto-reload on changes
When you run ccheckpoints setup
, it adds these hooks to your Claude Code config:
userPromptSubmit
β Tracks when you send a messagestop
β Tracks when session ends
The hooks call ccheckpoints track --event=<type>
which sends the data to the background server running on port 9271.
The background server needs port 9271. If it's busy, close other apps using it.
Make sure the server is running. Try ccheckpoints --verbose
to see what's happening.
Run setup again:
ccheckpoints setup
ccheckpoints --verbose
Check logs in %APPDATA%/CCheckpoints/logs/
If you find a bug or have an idea, feel free to open an issue! I'd be happy to discuss and see what we can do about it together.
Your feedback means a lot - thank you for using CCheckpoints!
MIT License
Copyright (c) 2025 Fayaz Bin Salam
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.