One model quota exhausted make the whole models unavailable

[serguei9090]

What happened?

(file:///C:/Users/ASCC/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/chunk-NET4RIEQ.js:306115:2 │
│ 2) │
│ at async GeminiClient.sendMessageStream │
│ (file:///C:/Users/ASCC/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/chunk-NET4RIEQ.js:306227:1 │
│ 4) │
│ at async │
│ file:///C:/Users/ASCC/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/interactiveCli-UPXIMCUC.js: │
│ 28202:24 │
│ at async │
│ file:///C:/Users/ASCC/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/interactiveCli-UPXIMCUC.js: │
│ 28378:38 { │
│ cause: { │
│ code: 429, │
│ message: 'You have exhausted your capacity on this model. Your quota will reset after 19h16m11s.', │
│ details: [ [Object], [Object] ] │
│ }, │
│ retryDelayMs: 69371663.390807, │
│ reason: 'QUOTA_EXHAUSTED' ▄│
│ }

[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?

Change the model manually or in Auto model selector

Model usage │
│ │
│ Flash ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 100% Resets: 5:27 PM (19h 11m)
│ Flash Lite ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 7% Resets: 5:27 PM (19h 11m)
│ Pro ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 52% Resets: 10:25 AM (12h 8m)

and I didnt used model 2.5 but still get same issue

Client information

• CLI Version: 0.41.1
• Git Commit: e1a5449
• Session ID: 671de020-6505-484c-8323-c3ce94d1c313
• Operating System: win32 v23.10.0
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-2.5
• Auth Type: oauth-personal
• Memory Usage: 252.0 MB
• Terminal Name: xterm.js(6.1.0-beta.197)
• Terminal Background: #191a1b
• Kitty Keyboard Protocol: Supported
• IDE Client: VS Code

Login information

google oAuth

Anything else we need to know?

No response

[gemini-cli]

There is a problem with the Gemini CLI issue triaging. Please check the action logs for details.