Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Gemini CLI shows Google One AI Pro plan but returns 403 PERMISSION_DENIED [1 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#26039•Fetched 2026-04-28 06:50:02
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
1
Author
rodinsonluker493-gifrodinsonluker493-gif
Participants
rodinsonluker493-gifrodinsonluker493-gif
Timeline (top)
labeled ×1

Gemini CLI recognizes my Google One AI Pro plan, but every prompt still fails with 403 PERMISSION_DENIED.

This does not look like a local proxy or subscription-detection issue, because the CLI UI shows that the paid plan is recognized.

Error Message

A simple prompt such as 你好 fails with:

[
  {
    "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"
    }
  }
]

Root Cause

This does not look like a local proxy or subscription-detection issue, because the CLI UI shows that the paid plan is recognized.

Code Example

[
  {
    "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"
    }
  }
]

---

https://cloudcode-pa.googleapis.com/v1internal:generateContent
https://cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse

---

project: ordinal-octagon-8p248

---

fce99eebb5be5e88
51557ffc3ff917fe
RAW_BUFFERClick to expand / collapse

Description

Gemini CLI recognizes my Google One AI Pro plan, but every prompt still fails with 403 PERMISSION_DENIED.

This does not look like a local proxy or subscription-detection issue, because the CLI UI shows that the paid plan is recognized.

Current CLI state

  • Gemini CLI version: 0.39.1
  • Auth status in CLI: Signed in with Google
  • Plan shown in CLI: Gemini Code Assist in Google One AI Pro
  • Model shown in CLI: Auto (Gemini 3)
  • Auth mode in ~/.gemini/settings.json: oauth-personal
  • Proxy: 127.0.0.1:7890, verified working

Error

A simple prompt such as 你好 fails with:

[
  {
    "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"
    }
  }
]

Diagnostics from earlier failed requests

Earlier full diagnostics showed requests going to the Gemini CLI / Code Assist backend even though the selected auth type is oauth-personal:

https://cloudcode-pa.googleapis.com/v1internal:generateContent
https://cloudcode-pa.googleapis.com/v1internal:streamGenerateContent?alt=sse

The earlier request body also included this project value:

project: ordinal-octagon-8p248

I did not intentionally configure or choose a Google Cloud project. My expectation is that Google account sign-in with Gemini Code Assist in Google One AI Pro should allow Gemini CLI requests using the recognized Pro plan.

Trace IDs from earlier failed responses

fce99eebb5be5e88
51557ffc3ff917fe

Timeline

  • First observed: 2026-04-22 around 11:25 UTC / 19:25 Asia/Shanghai
  • Still reproducible: 2026-04-27 Asia/Shanghai, after re-authentication and after the CLI recognized the Google One AI Pro plan

Could you please check whether there is a server-side permission issue with the Gemini CLI oauth-personal / Code Assist backend mapping for this account or for the cloudcode-pa.googleapis.com path?

extent analysis

TL;DR

The most likely fix is to investigate and potentially correct the server-side permission configuration for the Gemini CLI oauth-personal auth mode with the Code Assist backend.

Guidance

  • Verify that the oauth-personal auth mode is correctly configured to use the recognized Google One AI Pro plan without requiring an explicitly configured Google Cloud project.
  • Check the Gemini CLI documentation to see if there are specific requirements or limitations for using oauth-personal with Google One AI Pro plans.
  • Investigate the role of the project value (ordinal-octagon-8p248) in the request body and whether it needs to be explicitly set or configured for oauth-personal auth mode.
  • Consider reaching out to the Gemini CLI support team or checking their issue tracker for similar reports related to oauth-personal auth mode and Google One AI Pro plans.

Notes

The issue seems to be related to the interaction between the Gemini CLI, Google One AI Pro plan recognition, and the oauth-personal auth mode. Without more information about the Gemini CLI's internal workings or the specifics of the Google One AI Pro plan integration, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Investigate and potentially correct the server-side permission configuration, as the issue seems to be related to the permission denied error and the oauth-personal auth mode.

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#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix Gemini CLI shows Google One AI Pro plan but returns 403 PERMISSION_DENIED [1 participants]