gemini-cli - 💡(How to fix) Fix The latest (two or three) versions of the CLI are utterly destroying my Google workspace Gemini quotas [1 comments, 2 participants]

What happened?

The latest version of the CLI is utterly destroying my Google workspace Gemini quotas. I need to constantly interrupt ongoing thinking processes because it gets stuck on a loop (whether loop detection is enabled or not) and doesn't result in anything of value. These occur quite often as work is wrapping up. I interupt and use continue and only one simple final action is perfomed. Meanwhile, during thinking I can litterally watch the quota indicator incrementing in realtime. Since the last two releases I can barely go two hours before consuming my daily quota. Please help!

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

I didn't expect to burn through 2% of my daily token quota on run make lint-fix test and resolve any issues

Client information

• CLI Version: 0.41.2
• Git Commit: b0c7a1722
• Session ID: 3d041099-bdf3-486a-b6ba-5ba041f63eb5
• Operating System: linux v25.8.1
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-3
• Auth Type: oauth-personal
• Memory Usage: 540.0 MB
• Terminal Name: VTE(7600)
• Terminal Background: #000000
• Kitty Keyboard Protocol: Unsupported

bug-report-history-1778421585866.json

Login information

Google Account/API KEY, I have both and the results are the same. Last week using the API Key cost me $150 for approximately 3hrs of work which were not particularly productive.

Anything else we need to know?

The recent loop detection solution seems to be an attempt at resolving the run away token consumption but it isn't working properly at all. I sincerely ask you to consider reverting the majority of the CLI codebase to at least 2-3 weeks ago. I know this won't happen... but the current state is untenable. It really is.