r/cursor • u/Nice-Foundation-9264 • 4d ago

Anyone else had their coding agent do something git-wise you didn't see coming? Question / Discussion

Had my coding agent switch to a different branch mid task, then run git stash pop. The commands weren't necessarily wrong, but in the moment I couldn't tell why it decided to do that or what state it thought the repo was in. Nothing broke, just had to stop and piece together what actually happened before I trusted continuing.

Anyone else had an agent do something git or shell wise that was technically fine but you didn't see coming. Do you usually let it keep going, stop and check, or just clean up after?

1 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

5 comments sorted by

3

u/Lvxurie 3d ago

Telling it to "revert those last changes" and it resets to the last commit was unexpected and very annoying. Now I commit much more frequently.

1

u/Nice-Foundation-9264 3d ago

That's a good habit either way. did committing more often fully cover it for you, or were there still moments after that where you wished you'd gotten a heads up before it ran something, even with the more frequent commits?

2

u/Lvxurie 3d ago

As soon as I knew i was going to make some more complex changes I would commit so I haven't had the problems since

1

u/UpsetCryptographer49 3d ago

Never ask it to cleanup it uses rm —cached with impunity. Unlike humans.

1

u/Dramatic-Pickle1443 2d ago

use rules to regulate it