←back to thread

Claude Code Checkpoints

(claude-checkpoints.com)
184 points punnerud | 1 comments | | HN request time: 0.001s | source
Show context
radarsat1 ◴[] 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 #
hoppp ◴[] No.45051433[source]
Yea but then you need need to commit each iteration of each file right away, even if its not working.

Its fine if you just rebase at the end manually, but not good if you don't, your history will be cluttered and as hard to read as the codebase.

Eventually most people who use coding tools will have low knowledge of what is being generated and then they probably never rebase either...

replies(1): >>45054330 #
1. samtheprogram ◴[] No.45054330[source]
Yup, just rebase.

I just commit with a “wip!”-prefaced message whenever the LLM pauses and says it’s finished, including new files. You can squash and cleanup later, or revert back to a state before it screwed up.

Also doubles as a way to cohesively look at the changes it made without all the natural language and recursive error/type fixing it does while working.

I don’t understand why people are making it so complicated. You’re saving a minute per iteration with the LLM, tops, at risk of losing control or introducing hard to find issues. It is the definition of diminishing returns.