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

121–130 of 136 posts

Re: Claude Code Checkpoints

#121

Post by 0x6c6f6c »

jdthedisciple wrote: post #96
mhast wrote: post #8

Earlier quoted context omitted.

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

uhh... .gitignore solves that right?

These agents often generate randomly named files and dump them anywhere. You can end up with dozens of files added if you let it run on any problem it tries to create one-off "test / reproduction" cases. It hasn't always cleaned them up so a "git add all" approach can bring in junk, and the patterns for names aren't consistent. In fact they're often called stuff like *-test.js which looks like it could be a source OR test file.

Re: Claude Code Checkpoints

#122

Post by doritosfan84 »

bdangubic wrote: post #112
doritosfan84 wrote: post #106

Earlier quoted context omitted.

IME, the benefit is ease of branching paths. For example, if I'm working on a feature I can do something like this: - Put tests in one commit - Tell Claude to come up with several approaches where I'm not exactly sure what the best might be - Put approach 1 into a commit, 2 into a separate one, etc. These approach commits all live side by side instead of stacked on top of each other. - At any point I can create a new…

git has worktrees for this, I use them all the time

I don't see the correlation. Jujutsu has workspaces as the match to git's worktrees too because their worktrees are a different thing from what I'm talking about. Switching worktrees and making commits is way more work than just making commits.

Re: Claude Code Checkpoints

#124

Post by yumraj »

rubslopes wrote: post #105
earleybird wrote: post #104

Earlier quoted context omitted.

Pretty much bang on. I do have to remind myself that discipline in commit messages helps future me.

Claude Code produces pretty good commit messages, IMO. Just tell it: "commit".

Except it likes to put itself as the co-author in every commit message.

Even asking it repeatedly and putting not to do so in Claude.md has no effect. So I have to keep deleting that manually :)

Re: Claude Code Checkpoints

#125

Post by zhuravel »

yumraj wrote: post #124
rubslopes wrote: post #105

Earlier quoted context omitted.

Claude Code produces pretty good commit messages, IMO. Just tell it: "commit".

Except it likes to put itself as the co-author in every commit message. Even asking it repeatedly and putting not to do so in Claude.md has no effect. So I have to keep deleting that manually :)

Add "includeCoAuthoredBy": "false" to your settings file: https://docs.anthropic.com/en/docs/claude-code/settings

Re: Claude Code Checkpoints

#126

Post by zhuravel »

MacroStan wrote: post #111

Here's what I do to survive macos updates, random restarts, crashes etc. I had Claude Code to configure all of this: Terminal Setup: - Alacritty as your terminal - tmux as your session manager - Auto-start tmux in Alacritty configuration Key Protection: # Alacritty auto-starts tmux sessions tmux new-session -s main # Creates persistent session # tmux shortcuts (prefix: Ctrl+a) # Sessions persist even if terminal clos…

Why not use `claude --continue`?

Re: Claude Code Checkpoints

#127

Post by MacroStan »

zhuravel wrote: post #126
MacroStan wrote: post #111

Here's what I do to survive macos updates, random restarts, crashes etc. I had Claude Code to configure all of this: Terminal Setup: - Alacritty as your terminal - tmux as your session manager - Auto-start tmux in Alacritty configuration Key Protection: # Alacritty auto-starts tmux sessions tmux new-session -s main # Creates persistent session # tmux shortcuts (prefix: Ctrl+a) # Sessions persist even if terminal clos…

Why not use `claude --continue`?

I've tried claude --resume and it did not work. Also, I have 4 claude windows going on all the time. I do not know how to recreate all 4

Re: Claude Code Checkpoints

#128

Post by adastra22 »

doritosfan84 wrote: post #106
bdangubic wrote: post #103

Earlier quoted context omitted.

I dont understand the need for this at all. I use the git. Inside one CC session on average there will be 80-160 commits. I can revert back whatever I want whenever I want. Whenever context gets hairy I clear and ask CC to review specific commits to continue or whatever. I must be missing something here completely what is the need for jj at all…

IME, the benefit is ease of branching paths. For example, if I'm working on a feature I can do something like this: - Put tests in one commit - Tell Claude to come up with several approaches where I'm not exactly sure what the best might be - Put approach 1 into a commit, 2 into a separate one, etc. These approach commits all live side by side instead of stacked on top of each other. - At any point I can create a new…

Lack of staging in jj is a hard pass from me. I usually have a dozen different things I’m working on, and I commit piecemeal whenever one gets across the finish line. How do you do this in jj?

Re: Claude Code Checkpoints

#129

Post by adastra22 »

Wowfunhappy wrote: post #119
d4rkp4ttern wrote: post #117

Earlier quoted context omitted.

Actually, the ability to retain the current version when jumping back in conversation history is extremely useful for one reason: trimming context. For example I could work on adding a feature X, which will add some context. Then I rewind and add feature Y, etc. This helps delay compaction.

Yes, as I said there needs to be a way to jump back without rolling back the code as well!

You can. There is a slash command to move back to a prior point in the conversation. On mobile rn, but I know the is command exists as I’ve used it before.

Re: Claude Code Checkpoints

#130

Post by adastra22 »

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.

Do you not use git bisect?
Post reply on HN