That is not my experience.
Which is what?
Claude Code runs Git reset –hard origin/main against project repo every 10 mins
31–40 of 219 posts
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#32While that's obviously a bug which should be fixed, having stuff just sitting around uncommitted for days (which is much longer than 10 mins) is an anti-pattern (that I used to fall into).
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#33[flagged]
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#34Earlier quoted context omitted.
> Just by a thing being common in training data doesn't mean it will be produced. That's not what I said at all. I never said it will be produced. I said there is some probability of it being produced. > False, it goes against the RL/HF and other post training goals. It is correct that frequency in training data alone does not determine outputs, and that post-training (RLHF, policies, etc.) is meant to steer the mode…
It is meaningless to say that because the author was able to reproduce it multiple times.
> It is meaningless to say that because the author was able to reproduce it multiple times.
I don't know how that refutes what I'm saying.
The behaviour was reproduced multiple times, so it is clearly an observable outcome, not a one-off. It just shows that the probability of `git reset --hard` is > 0 even with RLHF and post-training.
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#35I think this post potentially mischaracterises what may be a one off issue for a certain person as if it were a broader problem. I'm guessing some context has been corrupted?
you might be right, but consider the implications, if context can be corrupted in 0.1% cases and it starts showing another destructive behaviour, after creating 1000 tickets to agent, your data might be accidentally wiped off
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#36Not sure I understand, wouldn't permissions prevent this? The user runs with `--dangerously-skip-permissions` so they can expect wild behaviour. They should run with permissions and a ruleset.
Who knows whether permissions would prevent this? Anthropic's documentation on permissions (https://code.claude.com/docs/en/permissions) does not describe how permissions are enforced; a slightly uncharitable reading of "How permissions interact with sandboxing" suggests that they are not really enforced and any prompt injection can circumvent them.
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#37no more developers, all code is written alone /s
yes sir
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#38Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#39> Process monitoring at 0.1-second intervals found zero git processes around reset times.
I don’t think this is a valid way of checking for spawned processes. Git commands are fast. 0.1-second intervals are not enough. I would replace the git on the $PATH by a wrapper that logs all operations and then execs the real git.
Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins
#40I'm curious how common this is or if this just affects this one user.
I opened up Hacker News and I saw this right at the top, and I assumed it had started happening to everyone. I thought, good thing I'm not running Claude Code right now.