Gaslighting about failing edits is definitely Gemini’s specialty. I don’t know the details, but maybe the edit tool should respond with one of three statuses: “Clean unambiguous edit, trust me it worked”, “Edit required some guesswork, double check”, “Failure”.
1 Like
I am laughing with you here. The sheer frustration I feel with braindead LLM hallucination is just unmatched. Gemini 2.5 has brought out the absolute best of me…
I have attempted several usage of rules to prevent such failures; sometimes it seems to work, but only if it decides it needs to use the rule that is specified to always be in context, or use it if I manually tag it - but sometimes it will just not use it no matter what I do.
1 Like
Similarly, I’m finding Gemini is getting trapped in it’s thinking stage and endlessly repeating the same 3 thoughts to itself.
2 Likes
I’m having the same problems. And Gemini accidentally deleted some important files a couple of times.
@danperks this is killing me (and poor gemini); here’s some more data to help you reproduce it:
- I’m also on windows (not wsl)
- happens like every conversation (say 1 in 5 file writes). it thinks its changes haven’t been applied but they have. i have to tell it to try reading the file.
- my computer is running super slowly lately (noticeable delay when typing)
- happens with all sorts of content, e.g. code and documentation files (although below apostrophe issue hints at escaping problems)
So, it seems to me like a timing issue with the edit_file tool. Like it writes its changes, waits for like 20ms for some async updates to occur (disk writes / cursor indexing / whatever), checks the result, doesn’t see the changes, replies back to gemini that it failed, meanwhile 30ms later the change goes through, but gemini’s already acting on the incorrect response.
Pls try grabbing a pc and overloading its disk/cpu with whatever tasks (moving files etc), then at the same time asking gemini to edit some files, esp bigish. The issues should start pretty quickly.
2 Likes
This issue really caused me some frustration. Yesterday gemini was buzzing along so smoothly i didn’t even use git, and today it has completely messed up all the work we did yesterday by just completely failing to use edit and reapply correctly like 80% of the time (it seems like prepending edits and reapply are the worst). And there was this quirk where when the tool gets called often in succession, it opens each file, some of them are displayed as not saved, even after clicking “accept”, and the end result is a mess cause i don’t know if i’m overwriting on save or actually saving his edits. sometimes after clicking accept but not saving, i end up with an empty file. plz fix
2 Likes
So far it’s working, thanks!
[edit]
I spoke too soon, still not working 
Cursor team! Fix this please!
1 Like
Solving this issue has a potential to greatly lower the heavy usage of Sonnet 4 by Cursor users.
I fail to understand why this isn’t treated as a priority.
1 Like
This is a severe issue for my company, and we use Cursor extensively - but we are forced to consider alternatives as Cursor lacks agility, has critical bugs, yet seems to be focusing on completely useless features like Slack integration
3 Likes
I’m here having same issues and looking forward to a stable fix from Cursor side.
1 Like
Can you give me a tip on how to integrate this rule and get Gemini to pay attention to it? I often swap models around during use and don’t want to have to copy this file in as context each time I use gemini? Thanks. (Also, yeah, why isn’t this a top priority for Cursor team to fix?)
Setup a rule to reapply the edit if it fails and read the file to double check if reapply also failed
this helped so much ! thx !
to add to this, I’ve had several times where Gemini has described the output it is getting as “garbled” and “corrupted”, it seems there is a low level encoding/decoding issue here that only affects Gemini when it is using its Edit tools. We would need Cursor’s devs to do a thorough debugging of the actual output it’s getting from the Edit tools.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.