Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code Checkpoints

claude-checkpoints.com

Post reply on HN
Print view View original

41–50 of 136 posts

Re: Claude Code Checkpoints

#41

Post by emilecantin »

michaelmior wrote: post #39
emilecantin wrote: post #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.

As someone who doesn't use CC, auto-commit seems like it would be the easiest way to manage changes. It's easy enough to revert or edit a commit if I don't like what happened.

It's also very easy to throw away unstaged changes, and to stage exactly what you want. I treat the staging process ("git add") as a code review.

Re: Claude Code Checkpoints

#42

Post by andrewmutz »

Wowfunhappy wrote: post #6

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…

Cline gives you the ability to jump back to any point in the task. The three options are "Restore task", "restore files" and "restore task and files"

A common experience with these tools is that if you realize you want to change the direction you're heading, it's better to jump back to that point in the work and redo it than it is to try to redirect the tool from where you are. Here's a great post about it on the Cline blog

https://cline.bot/blog/how-i-learned-to-stop-course-correcti...

Re: Claude Code Checkpoints

#43

Post by punnerud »

adds68 wrote: post #32

Great idea, but i've set it up and the app is pretty unusable for me, there is some sort of blocking process which runs every few seconds and freezes the UI, so you can interact with it properly

Strange, tested on MacBook Pro M3, Pro Intel and MacBook Air M1. All with different OS versions. Straight after the MCP connection setup this happens?

Re: Claude Code Checkpoints

#44

Post by black_knight »

CuriouslyC wrote: post #22
kristianp wrote: post #9

Earlier quoted context omitted.

This was a pain point in coming from Aider to CC. How to have diffs of the changes once CC has done the changes? Having git commits done the way Aider does it would have saved me a lot of time.

You can prompt claude code to do that, or use hooks. You can run lint/test/commit automatically on agent stop.

Yes, but the convenience of aider’s /undo might take quite some work to replicate.

Re: Claude Code Checkpoints

#45

Post by faangguyindia »

Wowfunhappy wrote: post #6

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…

Gemini cli already got this, it's disabled by default.

Ref: https://github.com/google-gemini/gemini-cli/blob/main/docs/c...

Re: Claude Code Checkpoints

#46

Post by black_knight »

mhast wrote: post #8
radarsat1 wrote: post #2

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

I always squash and reorganise the commits from aider. It is however awesome that everything is in git directly from the agent. I can’t imagine why not all these tools do this!

Re: Claude Code Checkpoints

#47

Post by js8 »

CuriouslyC wrote: post #24
endymion-light wrote: post #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!

T shirt estimation doesn't make any sense for AI dev, not one bit. They get epic long features done in hours, and all the shirt sizing comes from cases where the agent circles the drain and needs to be guided, which isn't predictable. The shirt sizes now are for manual acceptance testing.

> T shirt estimation doesn't make any sense for AI dev

It doesn't make sense for NI (natural intelligence) dev, either. Even SCRUM doesn't make much sense. The only Agile thing that really makes sense is Kanban, which is actually known to computer science as dispatch queue.

In the 60s, OS researchers spent time figuring out how to optimally schedule resources for computation. Today, almost nobody uses these techniques. (This is known as "waterfall" in PM parlance.)

It turns out, the cheapest way to schedule computing resources is a simple dispatch queue. Why spend extra time figuring out in what order things need to be done, or how long they will take, if they need to be done anyway? It never made sense and it doesn't matter whether the agent is NI or AI.

Re: Claude Code Checkpoints

#48

Post by neutronicus »

epolanski wrote: post #40
Cheer2171 wrote: post #19

If Claude Code LLMs are reportedly so good, then why is the Claude Code CLI such a buggy, messy, featureless disaster? Are they dogfooding?

By which metric is it a disaster? Seems quite solid and impressive to me as it is.

I replied to a sibling comment with my observations - the upshot is the actual user interaction is quite buggy in my experience.

If you typically compose prompts in a separate editor and paste them in you aren't likely to even notice. But it's the kind of thing that would drive me up the wall in a piece of software whose primary function was less impressive.

Re: Claude Code Checkpoints

#49

Post by felixgallo »

punnerud wrote: post #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

Are you aware of trademark law?

Re: Claude Code Checkpoints

#50

Post by fastball »

emilecantin wrote: post #41
michaelmior wrote: post #39

Earlier quoted context omitted.

As someone who doesn't use CC, auto-commit seems like it would be the easiest way to manage changes. It's easy enough to revert or edit a commit if I don't like what happened.

It's also very easy to throw away unstaged changes, and to stage exactly what you want. I treat the staging process ("git add") as a code review.

It's also very easy to throw away actual commits, as long as you don't push them (and even then not so difficult if you're in a context where force-pushing is tolerable).
Post reply on HN