←back to thread

Claude Code Checkpoints

(claude-checkpoints.com)
184 points punnerud | 2 comments | 28 Aug 25 09:16 UTC | HN request time: 0.489s | source
Show context
radarsat1 ◴[28 Aug 25 12:17 UTC] No.45051243[source]▶
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.

replies(4): >>45051308 #>>45051403 #>>45051433 #>>45051448 #
1. jtickle ◴[28 Aug 25 12:36 UTC] No.45051403[source]▶
I recently started using Aider and had that thought about too many commits. What I realized though was: (1) if I'm going to contribute to a project, I should be working in a local branch and interactively rebasing to clean up my history anyway (and of course carefully reviewing Aider's work first) and (2) if I'm working on my own thing WITHOUT LLM, I tend to prefer to commit every dang little change anyway, I just don't remember to do it because I'm in the zone and then inevitably wish I had at some point.
replies(1): >>45053493 #
2. vlovich123 ◴[28 Aug 25 15:33 UTC] No.45053493[source]▶
> I tend to prefer to commit every dang little change anyway, I just don't remember to do it because I'm in the zone and then inevitably wish I had at some point.

That’s what I do too until I developed a practice to break up into thematic commits as I realize I need them. And if I don’t, then I just git reset to the beginning and use git gui to commit lines and chunks that are relevant for a given piece of work. But with experience, I barely do the break down completely - I generally don’t even bother creating commits until I have a starting sense of what the desired commit history should be.