gemini-cli - 💡(How to fix) Fix OAuth succeeds with Google AI Pro account, but every Gemini CLI request returns 403 PERMISSION_DENIED [2 comments, 3 participants]

Subject: Gemini CLI OAuth succeeds but requests fail with 403 PERMISSION_DENIED

Account:

• Google account: [email protected]
• Subscription: Google AI Pro

Environment:

• OS: Windows 10
• Shell: Windows PowerShell
• Gemini CLI version: 0.36.0

What happened:

1. Gemini CLI was installed successfully on Windows.
2. OAuth browser sign-in completed successfully.
3. Gemini CLI stores the login as personal OAuth.
4. The active Google account is [email protected].
5. After successful sign-in and restart, even a simple prompt like 1+1 fails.

Current local auth state:

• settings.json selectedType: oauth-personal
• google_accounts.json active: [email protected]

Actual error: 403 PERMISSION_DENIED The caller does not have permission

Exact CLI error text: [API Error: [{ error: { code: 403, message: The caller does not have permission, errors: [ { message: The caller does not have permission, domain: global, reason: forbidden } ], status: PERMISSION_DENIED } }]]

What was already tried:

• Reinstalled and ran Gemini CLI on Windows instead of WSL
• Cleared local Gemini auth/cache files
• Re-ran browser OAuth sign-in
• Confirmed the active account is the paid Google account
• Restarted Gemini CLI after successful authentication

Expected behavior:

• A Google AI Pro account should be able to use Gemini CLI after successful OAuth sign-in

Actual behavior:

• OAuth succeeds, but every request is rejected with 403 PERMISSION_DENIED

Request:

• Please confirm whether Gemini CLI access is enabled for this Google AI Pro account
• Please confirm whether any additional entitlement, region, or account verification step is required
• Please confirm whether this is a backend entitlement issue for Gemini CLI