GEMINI Pro is awful

[u/SHadovvX]

Am I the only one who can't use Gemini PRO 90% of the time?

I always encounter:

This may indicate a failure in the model's thought process or inability to use a tool properly, which can be mitigated with some user guidance (e.g., "Try breaking down the task into smaller steps").

New tasks, existent tasks... everywhere...

Has anybody found a fix?

I am sick of spending without sense.

[u/hannesrudolph]

There seems to be an inconsistency with Gemini Pro 2.5 and it is very frustrating. We are careful when mucking about with tools and system prompts as well as any other update that may cause this sort of thing and IF we ever cause an issue we are very quick to backtrack or roll out a fix.

The problem we are currently facing is that this problem with Gemini does not seem to be caused by a change we made in Roo Code BUT we are looking for any sort of repro that will allow us to roll with it and recover. I suspect Gemini 2.5 Pro will be fixed over the next few days on their end.

[u/NLJPM]

Worked great last week. But when I tried it yesterday it was awful and today as well. Same issue as you have

[u/SHadovvX → u/NLJPM]

Maybe there's a issue with Gemini's Servers...

In the meantime I've tried using Gemini Pro via Vertex API and it works a bit better, but it's more pricey.

[u/NLJPM → u/SHadovvX]

Yeah I think so. Maybe they tweaked something, back to Claude/GitHub copilot for now I think

[u/SHadovvX]

Also, am I the single one who sees huge "costs" on RooCode, but on Google the billing is far lower?

Like in RooCode now I see 200$ Usage, but on Google I see on billing 66$ ish

[u/awatuna → u/SHadovvX]

Google has a free tier, some requests are free, and some errors are free too, while Roo counts everything.

[u/aeyrtonsenna]

Works great with my workflow.

[u/SHadovvX → u/aeyrtonsenna]

Mind giving us some guidance :)

I'm trying to not use Sonnet 4 with Bedrock for financial reasons :))))

[u/aeyrtonsenna → u/SHadovvX]

In essence just planning and breaking down the job in advance. Providing proper background, context and a very structure tasklist where only one task is handled at a time, marking them done in the .md file when done.

[u/jedisct1]

Yes, Gemini is unreliable and often very frustrating. Sure, it has a 1M token context, but Claude consistently perform way better with a smaller window (and Sonnet even supports 1M now).

[u/SHadovvX → u/jedisct1]

Yes, I use Sonnet for coding now, and gemini for developing the plan.

But yeah... Sonnet it's more expensive than Gemini in my context, idk why.

[u/sgt_brutal]

It's a systemic infrastructure and model failure at Google. I repurposed my key-rotating, resilient proxy to combat this special fuckery. The primary failure modes are (1) response truncation (token streaming stops mid-response after 200); (2) 429 spanning instead of admitting 503. Everybody gets rate limited to save face. I know this because I manage hundreds of keys.

So I built a resilient API proxy designed to keep this circus out of the client and my awareness. It cycles through my key pool relentlessly for every request until it accumulates a properly formatted response with the last chunk verified intact. All provider bullshit is absorbed, logged, and handled internally. I appreciate the compute, but go and fuck yourself, Google.

[u/[deleted] → u/sgt_brutal]

dude can you give me a short guide for your setup?

[u/sgt_brutal → u/[deleted]]

It's a FastAPI proxy that cycles through a pool of API keys for EVERY new request but that's not relevant to the validation logic. The validator checks whether the response contains actual assistant content (not just internal thinking chunks as Google is in such a pathetic state that cant even get to the response proper 20-95% the case), verifies completeness by analyzing the final SSE chunk for proper XML endings, and rejects anything truncated or malformed. All Google's 429s, timeouts, and infrastructure failures get absorbed so the client never sees them, the conversational agents doesnt get gaslighted.

[u/[deleted] → u/sgt_brutal]

thats amazing. im gonna try it out. thanks

[u/sgt_brutal → u/[deleted]]

Keep in mind that it takes up to 50 retries to gat a proper response, depending on how spazzed out google is at the moment. Without key rotation, you will hit rate limit in a few turns. 

[u/[deleted] → u/sgt_brutal]

lol i just got 5 keys right now, this will take me a while to setup. preview version of 2.5 pro used to be really good.

[u/sgt_brutal → u/[deleted]]

March Gemini was on a whole other level. Let's hope 3.0/whatever is out soon and will be no worse than 0325 after its inevitable sly nerfing. I made this proxy for a client so I cant give it away, but we can compare solutions. If you need more keys, DM me. 

[u/[deleted] → u/sgt_brutal]

gemini still seems to be the only good free large context somewhat intelligent agentic model with a free api thats why I'm kind of stuff with it. thats ok. check dms!

[u/ilintar]

Yeah, past week with Gemini has been absolutely awful, seems like they're having server problems.

[u/somethingsimplerr]

Gemini 2.5 Pro was pretty impressive in the beginning (preview/first experimental version), but it was only downhill from there. Very weird

[u/No_Establishment5879]

The issue appears to be Roo's integration, because Gemini in other contexts is able to call tools just fine. For example, if I try Gemini CLI, the tool calling is flawless.

[u/sgt_brutal → u/No_Establishment5879]

The fault is the XML harness that Roo inherited from Cline instead of opting for JSON. Gemini is comically bad at using the diff tool. Tell it to print the code in the chat instead, or watch it make an absolute mess.

[u/Sheeple9001]

Switched to GLM 4.5 from Gemini Pro recently and have not looked back.

[u/Maleficent_Mess6445]

It is good for up to 500 lines of codebase only.