gemini-cli - 💡(How to fix) Fix Pro quota shows incorrect 100% consumption after creation of GCP account hence blocking usage of the model [1 participants]

What happened?

I have a Google Workspace account and GeminiCLI was running perfectly fine. I login using Google Auth (No keys involved). Then I went ahead and created an account on GCP and then everything just went downhill. Since then, I am simple unable to use the pro model and it is permanently stuck on 100% used. I want to reiterate that I have associated any key or GCP project with my GeminiCLI.

What did you expect to happen?

I expected GeminiCLI to continue working as it with all models available and quota getting used normally however this change has completely blocked the quota.

Client information

• CLI Version: 0.38.2
• Git Commit: b0ed611a0
• ** ession ID:** 0ba594ac-a614-4072-b477-eb5e9a26cd07
• Operating System: win32 v24.14.1
• Sandbox Environment: no sandbox
• Model V rsion: gemini-3-flash-preview
• Auth Type: oauth-personal
• Memory Usage: 219.6 MB
• Terminal Name: Unknown
• Terminal 20Background: Unknown
• Kitty Keyboard Protocol: Unsupported

Login information

I login using Google Auth of my workspace account. This is a company account, not a personal one. I can confirm that the organization has not blocked any usage or does not have any additional plans purchased that can clash with this. I am attaching screenshot of the same

<img width="1568" height="267" alt="Image" src="https://github.com/user-attachments/assets/6bb6ef63-a51a-4e1e-bb96-ebfaf561d077" />

Anything else we need to know?

Everything was working fine will all models until I went ahead and created a GCP account using my workspace account and it just went downwards from there.