gemini-cli - 💡(How to fix) Fix Gemini CLI fails to recognize Google AI Pro subscription after changing Gmail address [3 comments, 2 participants]

What happened?

After changing my @gmail.com address a week or two ago, Gemini CLI no longer recognizes my Google AI Pro subscription and reverts to free tier quotas:

 ▝▜▄     Gemini CLI v0.40.0
   ▝▜▄
  ▗▟▀    Signed in with Google: [email protected] /auth
 ▝▀      Plan: Gemini Code Assist /upgrade

/stats model:

│  Auto (Gemini 3) Stats For Nerds                                                                                                                        │
│                                                                                                                                                         │
│  Auth Method:                Signed in with Google ([email protected])                                                                      │
│  Tier:                       Gemini Code Assist                                                                                                         │
│  6% used (Limit resets in 22h 47m)                                                                                                                      │
│  Usage limit: 200                                                                                                                                       │
│  Usage limits span all sessions and reset daily.                                                                                                        │

The plan is identified as Gemini Code Assist and not Gemini Code Assist in Google One AI Pro despite having an active annual subscription. Gemini CLI quotas are incorrectly applied at a lower threshold as a result.

It is reasonable to assume this issue would impact Ultra subscribers as well.

This issue is cross-platform and reproducible in clean, sandboxed environments. I tested on Windows 11 and Debian in WSL.

How to reproduce the issue

1. Have a Google AI Pro or Ultra subscription associated with a Gmail account.
2. Change your Gmail address.
3. Install Gemini CLI in a clean environment.
4. Log in with Google (OAuth) using the new Gmail address.
5. Observe Gemini CLI fail to apply your subscription tier and revert to Gemini Code Assist with lower quotas.

What did you expect to happen?

I expect Gemini CLI to correctly report my subscription tier and receive the full usage quota:

 ▝▜▄     Gemini CLI v0.40.0
   ▝▜▄
  ▗▟▀    Signed in with Google: [email protected] /auth
 ▝▀      Plan: Gemini Code Assist in Google One AI Pro /upgrade

Client information

• CLI Version: 0.40.0
• Git Commit: 3d5bdc052
• Session ID: e47ecf78-1e6e-4c00-a126-83aa56c7dfc1
• Operating System: win32 v25.9.0
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-3
• Auth Type: oauth-personal (Signed in with Google)
• Tier: Gemini Code Assist << this is the problem
• Memory Usage: 508.8 MB
• Terminal Name: Windows Terminal / PowerShell 7.6.1
• Terminal Background: #0c0c0c
• Kitty Keyboard Protocol: Unsupported

Login information

I'm logging in with my Google Account using OAuth. The environment and Gemini CLI have no config or variables set related to Google Cloud/GCP or API keys. Authentication succeeds but the correct subscription tier does not apply.

Anything else we need to know?

Antigravity also suffered from a similar problem recently, preventing agent communication entirely, that was resolved in 1.23.2.