CCheckpoints

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.

On npm: ccheckpoints

What is CCheckpoints?

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.

Quick Start

# 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:

1. ✅ Auto-setup Claude Code hooks (if not already done)
2. ✅ Start the background server
3. ✅ Open the dashboard in your browser

How It Works

1. Automatic Tracking: Every time you send a message to Claude Code CLI, CCheckpoints saves it as a checkpoint
2. Background Server: Runs quietly at http://127.0.0.1:9271 to handle tracking
3. Web Dashboard: Beautiful interface to see all your checkpoints and sessions
4. SQLite Database: All data stored locally in %APPDATA%/CCheckpoints/

Commands

Just run it!

ccheckpoints
# or
ccp

This does everything - sets up hooks if needed and opens the dashboard.

Manual setup (optional)

ccheckpoints setup
# or
ccp setup

Only needed if you want to setup without opening the dashboard.

Show dashboard

ccheckpoints show
# or
ccp show

Same as running just ccheckpoints - opens the dashboard (with auto-setup if needed).

Help

ccheckpoints --help
# or
ccp --help

Verbose mode

ccheckpoints --verbose
# or
ccp --verbose

See detailed logs of what's happening behind the scenes.

What Gets Tracked?

• Every message you send to Claude Code CLI (submit event)
• Session stops (when you exit Claude Code)
• Timestamps for everything
• Full conversation context

Screenshots

📊 Session Overview

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.

🎯 Checkpoint Timeline

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

🔍 Compare Changes

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

File Locations

• Windows: %APPDATA%/CCheckpoints/
• Mac/Linux: ~/.ccheckpoints/

Contains:

• checkpoints.db - SQLite database with all your data
• logs/ - Debug logs (when using --verbose)

For Developers

Build from source

# 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

Development mode

npm run dev         # Run without building
npm run dev:watch   # Auto-reload on changes

How the Hook System Works

When you run ccheckpoints setup, it adds these hooks to your Claude Code config:

• userPromptSubmit → Tracks when you send a message
• stop → Tracks when session ends

The hooks call ccheckpoints track --event=<type> which sends the data to the background server running on port 9271.

Troubleshooting

Port 9271 already in use?

The background server needs port 9271. If it's busy, close other apps using it.

Dashboard won't open?

Make sure the server is running. Try ccheckpoints --verbose to see what's happening.

Hooks not working?

Run setup again:

ccheckpoints setup

See detailed logs

ccheckpoints --verbose

Check logs in %APPDATA%/CCheckpoints/logs/

Found Something?

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!

License

MIT License — Copyright (c) 2025 Fayaz Bin Salam. See LICENSE for the full text.

Contributing

Contributions are warmly welcomed and greatly appreciated! Whether it's a bug fix, new feature, or improvement, your input helps make this project better for everyone.

Before submitting a pull request, please:

1. Create an issue describing the feature or bug fix you'd like to work on
2. Wait for discussion and approval to ensure alignment with project goals
3. Fork the repository and create your feature branch
4. Submit your pull request with a clear description of changes

This approach helps avoid duplicate efforts and ensures smooth collaboration. Thank you for considering contributing!

Share

Sharing this repository with your friends is just one click away from here

---

Support

If this saved you time, you can buy me a coffee — it keeps these projects maintained and free.

---

💼 Need this customised — or need it yesterday?

I take fixed-price web & desktop work on my own projects. No hourly billing, no surprise scope:

Drop-in integration — I wire this into your codebase and hand you a PR that builds	$45 · 3 days
Priority bug fix or small feature — jumps ahead of the free issue queue	$95 · 72 hours
Custom build — branded, packaged and deployed, source yours	$130 · 7 days
A full app from scratch	from $350 · quoted first

All prices and how to buy → p32929.github.io/hire
Or buy through Fiverr (escrow, ID-verified, 5.0★) — safest for a first job.

Scoping and quotes are free: open an issue and describe the job.