Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Google One AI Pro account can sign in successfully, but all prompts fail with 403 PERMISSION_DENIED in Gemini CLI [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25252•Fetched 2026-04-14 05:56:31
View on GitHub
Comments
3
Participants
3
Timeline
9
Reactions
2
Author
JettHayesJettHayes
Participants
gemini-cli[bot]gemini-cli[bot]JettHayesJettHayessachin1yadav1sachin1yadav1
Timeline (top)
commented ×3labeled ×3cross-referenced ×1subscribed ×1

Root Cause

Please confirm whether personal Google AI Pro / Google One AI Pro subscribers are currently supposed to have access to Gemini CLI through OAuth. If yes, this seems to be a bug in authorization or entitlement handling. If no, the current behavior is confusing because sign-in succeeds but all requests fail with 403.

RAW_BUFFERClick to expand / collapse

What happened?

I can sign in to Gemini CLI successfully with my personal Google account that has an active Google AI Pro / Google One AI Pro subscription. However, every prompt fails with 403 PERMISSION_DENIED.

So this is not a sign-in problem. OAuth works, but actual usage is denied.

I have already tried signing out and signing back in, and the issue still happens on every request.

Please confirm whether personal Google AI Pro / Google One AI Pro subscribers are currently supposed to have access to Gemini CLI through OAuth. If yes, this seems to be a bug in authorization or entitlement handling. If no, the current behavior is confusing because sign-in succeeds but all requests fail with 403.

Environment: Gemini CLI 0.37.1

What did you expect to happen?

I can sign in to Gemini CLI successfully with my personal Google account that has an active Google AI Pro / Google One AI Pro subscription. However, every prompt fails with 403 PERMISSION_DENIED.

So this is not a sign-in problem. OAuth works, but actual usage is denied.

I have already tried signing out and signing back in, and the issue still happens on every request.

Please confirm whether personal Google AI Pro / Google One AI Pro subscribers are currently supposed to have access to Gemini CLI through OAuth. If yes, this seems to be a bug in authorization or entitlement handling. If no, the current behavior is confusing because sign-in succeeds but all requests fail with 403.

Environment: Gemini CLI 0.37.1

Client information

I can sign in to Gemini CLI successfully with my personal Google account that has an active Google AI Pro / Google One AI Pro subscription. However, every prompt fails with 403 PERMISSION_DENIED.

So this is not a sign-in problem. OAuth works, but actual usage is denied.

I have already tried signing out and signing back in, and the issue still happens on every request.

Please confirm whether personal Google AI Pro / Google One AI Pro subscribers are currently supposed to have access to Gemini CLI through OAuth. If yes, this seems to be a bug in authorization or entitlement handling. If no, the current behavior is confusing because sign-in succeeds but all requests fail with 403.

Environment: Gemini CLI 0.37.1

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue is likely due to a mismatch between the expected authorization permissions for Google AI Pro / Google One AI Pro subscribers and the actual permissions granted to the Gemini CLI, resulting in a 403 PERMISSION_DENIED error.

Guidance

  • Verify the documentation for Google AI Pro / Google One AI Pro to confirm if subscribers are supposed to have access to Gemini CLI through OAuth.
  • Check the Gemini CLI documentation to see if there are any specific requirements or restrictions for using the CLI with Google AI Pro / Google One AI Pro subscriptions.
  • Investigate the authorization flow to ensure that the correct permissions are being requested and granted during the OAuth process.
  • Consider reaching out to the Gemini CLI support team to confirm if this is a known issue or a bug in the authorization or entitlement handling.

Notes

The issue seems to be related to the authorization and entitlement handling of the Gemini CLI, but without more information about the expected behavior and the actual implementation, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Wait for further clarification from the Gemini CLI support team or the Google AI Pro / Google One AI Pro documentation to confirm the expected behavior and potential workarounds.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING