google-gemini / google-gemini/gemini-cli

Gemini 2.5 Pro quota stuck at 100% / limit reached for several days

Open
#29,064 0 comments 0 reactions 0 assignees View on GitHub
area/platform status/need-triage
Dominant language
TypeScript
Stars
107k
Forks
14.6k
Avg merge
2d 3h
Merged PRs (30d)
45

Description

### What happened?

Gemini CLI has shown the Pro quota as 100% used / “limit reached” for several days and it is not resetting as it previously did.

I am using Gemini CLI 0.56.0 and signing in with my Google account. The plan shown in Gemini CLI is Gemini Code Assist.

I have already re-authenticated with Google, but the Pro quota still remains at 100% / limit reached. Flash quota continues to reset normally.

Gemini 2.5 Pro is still recognised by the CLI, but I cannot use it because the Pro quota remains stuck at the limit. Previously, the Pro quota would reset normally.

### What did you expect to happen?

I expected the Pro quota to reset after its normal quota-reset period, as it did previously, and for Gemini 2.5 Pro to become available again.

### Client information

*

### Login information

Sign in with Google / OAuth personal account. Gemini CLI shows the plan as Gemini Code Assist. I am not using Vertex AI or an API key.

### Anything else we need to know?

I have already tried signing out/re-authenticating with the same Google account, but the issue persists.

/usage continues to show Pro at 100% used / limit reached for several days, while Flash quota resets normally.

CLI version: 0.56.0
Git commit: b6e23a7dc
OS: Linux / Google Cloud Shell

This behaviour is different from previously, when the Pro quota would reset normally.

I can attach screenshots showing the Pro quota at 100% / limit reached and the model-selection screen.

Please confirm whether this is an intentional quota-policy change or a quota/entitlement issue affecting Gemini Code Assist / oauth-personal users.

Contributor guide

Open the contributing guide

Research direction

Reproduce with Gemini CLI 0.56.0 on Linux/Google Cloud Shell using Google OAuth, then inspect /usage and the model-selection screen. Compare the Pro and Flash quota behavior and establish whether the stuck Pro entitlement is a CLI defect or an intentional quota-policy change; done means documenting the cause and restoring normal Pro availability if the CLI is responsible.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.