Live data from Hacker News

Claude Code Checkpoints

claude-checkpoints.com

11–20 of 136 posts

Re: Claude Code Checkpoints

#11
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.

Re: Claude Code Checkpoints

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

Re: Claude Code Checkpoints

#13

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.

"Checkpoints for Claude Code" use git under the hood, but stored in .claudecheckpoints folder, to not mess with your own git. Add itself to .gitignore. It auto commits with a git message for the changes done through MCP locally.

Re: Claude Code Checkpoints

#14
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!

Re: Claude Code Checkpoints

#15
post #8

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 commit…

Git won't catch new files the agent is adding. To get around that you can of course always add all new files, but then you'll potentially have your repo polluted with a bunch of temporary scratch files instead. You can typically go back and edit git history. But it will require force push and breaking changes. And a few sacrifices to ensure that it doesn't make a mistake because then your repo is potentially broken.…

You could also create a branch, save your intermediates there, and then squash merge when you are ready.

Re: Claude Code Checkpoints

#16

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!

And soon enough it would need a project manager and HR to keep all the agents in line.

Re: Claude Code Checkpoints

#17

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 r…

Hi, the developer here. Already thinking about a way to add it as a background task that can communicate with multiple instances at once. As long as its part of CLAUDE.md, every new project would have it automatically included. Not part of Claude Code, but a good way closer?

Re: Claude Code Checkpoints

#18
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
Post reply on HN