Claude Code Checkpoints (claude-checkpoints.com)

I don't know what this is but isn't git enough? Incidentally I'm not convinced in my day-to-day for "jujitsu" (jj) but from what I understand about how it works, I've been wanting to give it a try for agent-based coding, based on the way it defaults to saving everything and letting you sort it out after. I do like how Aider commits everything so you can easily roll back, although it ends up with a few too many commits imho.

I've been wanting to experiment also with getting an agent to go back and rebase history, rewrite commits etc in the context of where the project ended up, to make a more legible history, but I don't know if that's doable, or even all that useful.

This is something I really wish was just built-in to Claude Code. I want it built in because I don't want to have to think about it beforehand. I should be able to jump back in conversation history and have the state of the code jump back with me, so it's restored to the same state it originally was at that point in the conversation.

(There does also need to be a way to jump back in the conversation history without reverting the code, there are times that is useful too!)

I tend to have auto-accept on for edits, and once Claude is done with a task I'll just use git to review and stage the changes, sometimes commit them when it's a logical spot for it.

I wouldn't want to have Claude auto-commit everything it does (because I sometimes revert its changes), nor would I want to YOLO it without any git repo... This seems like a nice tool, but for someone who has a very different workflow.

Hi, the developer here. Its a very early version so there could be a lot of bugs, but I like to use it myself (already found several bugs and updated version soon on its way). Switching from Cursor to Claude Code this was the biggest loss. Have tried to improve on the Cursor functionality, with features I missed.

I would love any feedback on what you are missing etc

i love the process of AI vibe coding slowly re-inventing the normal structures of software development

how long until we start seeing software products for scrum management and t-shirt size estimation for claude code

introduce waterfall methodology to the LLM!

Not to trivialize the work being done here but isn’t this as simple as a hook on edit and write tool calls that commits to git? I’m not sure I see the need for a whole app around this vs just the standard git workflow

If Claude Code LLMs are reportedly so good, then why is the Claude Code CLI such a buggy, messy, featureless disaster? Are they dogfooding?

Git add doesn't work?

this is coming to Claude Code

Great idea, but i've set it up and the app is pretty unusable for me, there is some sort of blocking process which runs every few seconds and freezes the UI, so you can interact with it properly

I want to do this with btrfs subvolumes/snapshots.

Disappointing that Claude’s chat interface is falling so far behind.

- no large context

- no zipfile uploads

- no multi file downloads

[dead]

Interesting to watch the explosion of projects, even whole startups, which are just a feature addition to Claude Code. Shows how beloved it has become.

This is fantastic, but a very spicy business. All Claude needs to do is add one feature and you've got your whole business nuked from orbit.

Under the hood, is this simply checkpointing the files in the claude target folder or are you also checkpointing the claude context? One of my biggest pain points is after a few compactions/edits to claude.md and all of a sudden Claude has made a few mistakes and all the context window cruft of fixes it attempted and reverted actually seem to confuse it further and it would be nice to reset to a known happy place code & contextually and retry from there.

So basically, "watch jj"

Or you could use something like NILFS2 [0]. It would be nice to be able to just turn such a function on and off per folder.

[0] https://docs.kernel.org/filesystems/nilfs2.html

I have a strong suspicion that if you need, or feel you need something like this, you're misusing coding agents.

Am I the only one who is getting tired of all these LLM generated landing pages with their hallmark indigo backgrounds/gradients, unnecessary and tasteless transitions, and meaningless marketing sell points?

I just add

> always git commit with a one line message

to my `~/.claude/CLAUDE.md` file. This has in my experience been enough to get atomic commits after every minor change. I'm probably not the target audience for this though.

People don't seriously still "lose work" do they? The last time that happened to me was a floppy disk failure in the 90s... Using LLMs doesn't preclude using git and keeping backups like everyone should.

This looks well-built, but have you considered using Jujutsu (jj) instead? It elegantly solves the snapshot/checkpoint problem without needing MCP servers or a separate app.

With jj, every file change is automatically captured (no manual commits needed), and you can create lightweight "sandbox" revisions for each Claude Code task. When things go wrong, `jj undo` instantly reverts to any previous state. The operation log tracks everything, making it virtually impossible to lose work.

The workflow becomes: let Claude Code generate messy experimental code → use `jj squash`/`jj split` to shape clean commits afterward. You get automatic checkpointing plus powerful history manipulation in one tool.

I've been using jj with Claude Code for months and it's transformed how I work with coding agents - no fear of breaking things because everything is instantly reversible. The MCP integration seems like added complexity when jj's native capabilities already handle the core problem.

For anyone interested in the jj + agent workflow, read my post: https://slavakurilyak.com/posts/use-jujutsu-not-git

That said, respect for shipping something that solves a real pain point! The UI looks clean and the diff viewer is nice.

Coding with LLM’s has taught me that there is value to treating AI produced code as a slot machine, that sometimes produces brilliant work and sometimes causes huge bugs. The best way to use LLM’s is to structure the project to maximize the benefit from the rare brilliances and minimize the risk and hazard of those bugs. Version control has to be treated somewhat like a bonsai, a cycle of growth and pruning with an ultimate framework in mind.