Live data from Hacker News

Claude Code runs Git reset –hard origin/main against project repo every 10 mins

github.com

51–60 of 219 posts

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#51
post #34

Earlier quoted context omitted.

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.

If it reliably reproduces something undesirable with statistical significance, then it is a bug. It can be fixed with RLHF.

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#53
post #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.

Sure looks to me like this whole case is Claude Code chasing its own tail, failing to debug, and offering to instead generate a bug report for the user when it can't figure out a better way forward.

Maybe even submitting the bug report "agentically" without user input, if it's running on host without guardrails (pure speculation).

E: It's a runaway bot lol https://github.com/anthropics/claude-code/issues/40701#issue...

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#56

I 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

I'd been using cursor at work for a year or two now, figured I'd try it on a personal project. I got to the point where I needed to support env-vars, and my general pattern is `source ./source-me-local-auth` => `export SOME_TOKEN="$( passman read some-token.com/password )"` ...so I wrote up the little dummy script and it literally just says: "Hrm... I think I'll delete these untracked files from the working directory before committing!" ...and goes skipping merrily along it's way.

Never had that experience in the whole time using cursor at work so I had to "take the agent to task" and ask it "WTF-mate? you'd better be able to repro that!" and then circle around the drain for a while getting an AGENTS.md written up. Not really a big deal, as the whole project was like 1k lines in and it's not like the code I'd hand-written there was "irreplaceable" but it lead to some interesting discussion w/ the AI like "Why should I have to tell you this? Shouldn't your baseline training data presume not to delete files that you didn't author? How do you think this affects my trust not just of this agent session, but all agent interactions in the future?"

Overall, this is turning out to be quite interesting technology times we're living in.

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#57

Earlier quoted context omitted.

I was thinking surely scheduled tasks need to be explicitly invoked but nope: https://code.claude.com/docs/en/scheduled-tasks#set-a-one-ti... Some people are upset at my brave new world characterization, but yeah even as someone deriving value from Claude Code we've jumped the shark on AI in development. Either the industry will face that reality and recalibrate, or in 20 years we're going to look back on these days…

I agree that it's worrying that we're moving more and more towards implicit and opaque state. Hiding what exactly is getting edited, very limited tooling to check what the subagents are doing exactly, setting up scheduled and recurring tasks without it being obvious etc. It's tending more and more towards pushing the user to treat the whole thing as a pure chat interface magic black box, instead of a rich dashboard t…

It does make WH40k seem more plausible. Tech priests praying to the capricious machine spirit to just please do the thing.

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#58

Earlier quoted context omitted.

I agree that it's worrying that we're moving more and more towards implicit and opaque state. Hiding what exactly is getting edited, very limited tooling to check what the subagents are doing exactly, setting up scheduled and recurring tasks without it being obvious etc. It's tending more and more towards pushing the user to treat the whole thing as a pure chat interface magic black box, instead of a rich dashboard t…

It does make WH40k seem more plausible. Tech priests praying to the capricious machine spirit to just please do the thing.

[dead]

Re: Claude Code runs Git reset –hard origin/main against project repo every 10 mins

#60
post #12

cool. if you choose to use a non-deterministic black box of bullshit, should you really be surprised when it shits all over your floor?

The person who posted this bug doesn't seem like the pinnacle of software engineering. To me, this looks like either a user error or some corrupt file or context you should be able to clean up pretty quickly.

You reap what you sow, finance bro.

Post reply on HN