Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix 403 PERMISSION_DENIED on Gemini CLI for valid Google One AI Pro account (Code Assist activated, all local fixes attempted) [2 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#26112•Fetched 2026-04-29 06:35:50
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Author
brain898brain898
Participants
brain898brain898Delta-WaterDelta-WaterSuzy1uSuzy1u
Timeline (top)
commented ×2cross-referenced ×1labeled ×1

Error Message

Error Details

  • Error message:​ The caller does not have permission
RAW_BUFFERClick to expand / collapse

Problem

Gemini CLI consistently returns 403 PERMISSION_DENIED ("The caller does not have permission") for every prompt, while the same Google account works perfectly on web Gemini and Antigravity IDE.

Environment

  • OS:​ Windows
  • CLI version:​ latest (freshly reinstalled via npm install -g @google/gemini-cli@latest)
  • Node.js:​ (please fill in your version, run node -v)
  • Account email:​ [email protected]
  • Subscription:​ Google One AI Pro (active, paid plan confirmed on codeassist.google.com)
  • Network egress IP:​ 168.158.125.3 (US, Arizona)

Error Details

  • Endpoint:​ https://cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse
  • Status:​ 403 Forbidden
  • Error message:​ The caller does not have permission
  • Reason:​ forbidden
  • Status code:​ PERMISSION_DENIED

Trace IDs

  • f63fec6f43d395d2 (2026-04-28 08:40:30 GMT)
  • 3c0381784abdbefa (2026-04-28 12:51:11 GMT)

What Works

  • Web Gemini (gemini.google.com): ✅ working
  • Antigravity IDE: ✅ working
  • codeassist.google.com dashboard: ✅ shows "Paid" plan, fully activated

What Fails

  • Gemini CLI: ❌ every prompt returns 403

Troubleshooting Already Attempted

  • Cleared ~/.gemini, %LOCALAPPDATA%\google-gemini, %APPDATA%\google-gemini
  • Uninstalled and reinstalled @google/gemini-cli@latest
  • Cleared npm cache
  • Removed third-party app authorization at myaccount.google.com/permissions
  • Logged out of all Google accounts in browser, re-authenticated CLI from scratch
  • Confirmed correct cached account via /about ([email protected])
  • Unset all GOOGLE_* and GEMINI_* environment variables
  • Verified network egress IP is in US (Arizona) via ipinfo.io
  • Confirmed Code Assist is activated (paid plan) at codeassist.google.com
  • Confirmed account is a personal account (not Workspace-managed)

Important Note

I have never used any third-party tools, reverse proxies, or shared my account credentials. This appears to be an entitlement / authorization issue on the backend, similar to #24533 and #24517.

Request

Please investigate the entitlement state for my account using the trace IDs above and restore Gemini CLI access for my Google One AI Pro subscription.

extent analysis

TL;DR

The most likely fix is to investigate and resolve the entitlement state for the account using the provided trace IDs, as the issue appears to be related to authorization on the backend.

Guidance

  • Investigate the entitlement state for the account using the provided trace IDs (f63fec6f43d395d2 and 3c0381784abdbefa) to determine the cause of the PERMISSION_DENIED error.
  • Verify that the Google One AI Pro subscription is correctly linked to the account and that there are no issues with the subscription status.
  • Check for any differences in authentication or authorization between the working web and IDE interfaces and the failing CLI, as this may indicate a specific issue with the CLI's authentication flow.
  • Consider reaching out to the Google support team for further assistance, as the issue appears to be related to the backend entitlement state.

Notes

The issue seems to be specific to the Gemini CLI and is not related to the user's network or environment, as the web and IDE interfaces are working correctly. The fact that the user has never used third-party tools or shared their account credentials suggests that the issue is likely related to the account's entitlement state.

Recommendation

Apply workaround: Reach out to the Google support team for further assistance in investigating and resolving the entitlement state for the account, as the issue appears to be related to authorization on the backend.

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…
#api#agent execution#callback error#memory management#environment variable

Still need to ship something?

×6

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

Back to top recommendations

TRENDING