←back to thread

Claude Code Checkpoints

(claude-checkpoints.com)
184 points punnerud | 1 comments | | HN request time: 0.202s | 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 #
mfenniak ◴[] No.45051308[source]
I don't think jujutsu woild help with this use case -- jujutsu will not save everything because it is not running constantly on your repo. It snapshots the working tree only when you run a `jj` command. Ineffective if an agent is doing work.
replies(2): >>45051334 #>>45061100 #
1. adobrawy ◴[] No.45051334[source]
You can use Claude hooks ( https://docs.anthropic.com/en/docs/claude-code/hooks#stop-an... ) to trigger jj / git automatically.