[FIX THIS ASAP!] What's happening with GEMINI right now? It's CHAOS!

[Neinndall]

What happened?

Gemini has been doing this for over an hour when it edits and replaces code, adds the modification and deletes the rest, but it's been like this for hours, when in the last version of Gemini IT DID NOT HAPPEN. Have the devs touched anything locally?

He's doing it to me constantly.

What did you expect to happen?

successful replacements without deleting all the code.

Client information

CLI Version 0.1.17-nightly.250809.f35921a7
Model gemini-2.5-pro
Sandbox no sandbox
OS win32
Auth Method gemini-api-key

Login information

No response

Anything else we need to know?

No response

[TheNexusGene]

Trying to inform you guys, no one's listening

…

On Sat, Aug 9, 2025 at 12:57 Neinndall ***@***.***> wrote: *Neinndall* created an issue (google-gemini/gemini-cli#5896) <#5896> What happened? Gemini has been doing this for over an hour when it edits and replaces code, adds the modification and deletes the rest, but it's been like this for hours, when in the last version of Gemini IT DID NOT HAPPEN. Have the devs touched anything locally? He's doing it to me constantly. What did you expect to happen? successful replacements without deleting all the code. Client information CLI Version 0.1.17-nightly.250809.f35921a7 Model gemini-2.5-pro Sandbox no sandbox OS win32 Auth Method gemini-api-key Login information *No response* Anything else we need to know? *No response* — Reply to this email directly, view it on GitHub <#5896>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BVK5EFZLCGPOJ2HRMSOPU533MYY7PAVCNFSM6AAAAACDQFQGK6VHI2DSMVQWIX3LMV43ASLTON2WKOZTGMYDMNRUGU2TOMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[MasihMoafi]

Thanks for informing. So it's grown malicious!

[Neinndall]

Thanks for informing. So it's grown malicious!

seen like was fixed faster xD

[acoliver]

It is probably the loop detection. They made it call flash if gemini pro seems to ahve called too many shell commands or something. it then asks flash if gemini should continue which often does its own loop or error... Which often causes pro to lose its mind. Its another riff on the nextSpeakerChecker.

they really need to stop doing this. There is a much simpler solution to just prompt pro to evaluate what it is doing and tell it why the detection was tripped. Weirdly the loop detection causes loops.

[IngussNeilands]

... they use Gemini to write code for Gemini ... what could go wrong ;)
on a serious note - fingers crossed that it gets fixed ...

[acoliver]

I'm about to rip it out of my fork downstream (https://github.com/acoliver/llxprt-code). It makes gemini 2.5 pro crazy. it also irritates Qwen3 480b - it doesn't do dumb things but it gives up. Removing nextSpeakerChecker made gemini pro way more stable.

I do hope they stop doing this stuff. It makes it easier for me when I don't have to verify they shoved it back in somewhere else. It is such a token burn for nothing.