Claude Code Checkpoints
71–80 of 136 posts
Re: Claude Code Checkpoints
#72This 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.
Re: Claude Code Checkpoints
#73This 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…
Github Copilot in vscode can do that and also has the Claude models available
Re: Claude Code Checkpoints
#74Earlier quoted context omitted.
Gemini cli already got this, it's disabled by default. Ref: https://github.com/google-gemini/gemini-cli/blob/main/docs/c...
if only gemini cli could edit files without getting stuck in an infinite loop
Re: Claude Code Checkpoints
#75I 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…
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...
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.
Re: Claude Code Checkpoints
#76i 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!
(These people dont realise that there a lot of tradeoffs to be made that pop up during implementation)
Re: Claude Code Checkpoints
#77this is coming to Claude Code
Re: Claude Code Checkpoints
#78Re: Claude Code Checkpoints
#79This 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…
Re: Claude Code Checkpoints
#80Earlier quoted context omitted.
Are you aware of trademark law?
Yes, tried to make it clear that this is Checkpoints for Claude Code. An addition to Claude Code.