Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix oauth-personal returns 403 PERMISSION_DENIED — was working until April 10, now broken on Ubuntu and Windows [1 comments, 2 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#25425•Fetched 2026-04-15 06:44:40
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
ArkNillArkNill
Participants
ArkNillArkNillgemini-cli[bot]gemini-cli[bot]
Timeline (top)
cross-referenced ×4labeled ×3commented ×1

Error Message

I tested on a completely separate Windows 11 machine with a fresh install and got the exact same error, so this isn't a local environment issue.

  • Deleted ~/.gemini/oauth_creds.json and started fresh — new token, same error

Code Example

2026-04-07  session-...-8d7d3841.json  → success ("What is 2+2?" → "4")
2026-04-08  session-...-ab0a0d23.json  → success ("What is 7*8?" → "56")
2026-04-10  session-...-69759bc0.json  → success (project analysis, got full response)
2026-04-15  session-...-4876cf08.json  → 403 PERMISSION_DENIED
RAW_BUFFERClick to expand / collapse

I've been using the official Gemini CLI with oauth-personal for about a week without issues. My last successful session was on April 10 (I can see the response in my local session files). Today, every API call returns 403 PERMISSION_DENIED — login works fine, subscription is recognized, but nothing goes through.

I tested on a completely separate Windows 11 machine with a fresh install and got the exact same error, so this isn't a local environment issue.

Setup

  • Gemini CLI v0.38.0 (npm install -g @google/gemini-cli)
  • Ubuntu 24.04 + Windows 11 (both fail identically)
  • Node.js v22.22.1
  • Google One AI Pro subscriber, oauth-personal auth

What happens

  1. /auth → Google login succeeds
  2. CLI correctly shows "Plan: Gemini Code Assist in Google One AI Pro"
  3. Any message → 403 "The caller does not have permission"

What I've tried

  • Re-authenticated multiple times with /auth
  • Deleted ~/.gemini/oauth_creds.json and started fresh — new token, same error
  • Verified the token is valid and not expired
  • Tested on a different machine and OS — same result

Timeline from my session files

2026-04-07  session-...-8d7d3841.json  → success ("What is 2+2?" → "4")
2026-04-08  session-...-ab0a0d23.json  → success ("What is 7*8?" → "56")
2026-04-10  session-...-69759bc0.json  → success (project analysis, got full response)
2026-04-15  session-...-4876cf08.json  → 403 PERMISSION_DENIED

Something changed server-side between April 10 and today.

Not a third-party tool issue

I want to be clear — I've never used OpenCode, OpenClaw, or any third-party CLI with my Google OAuth credentials. This is purely the official @google/gemini-cli from npm.

Related issues

This looks like the same cloudaicompanionProject routing problem described in #25189, #24517, and #24533.

extent analysis

TL;DR

The most likely fix is to wait for an official update or patch from the Gemini CLI team, as the issue seems to be related to a server-side change that occurred between April 10 and April 15.

Guidance

  • Verify that the issue is indeed related to the server-side change by checking the official Gemini CLI GitHub page for any updates or announcements regarding the cloudaicompanionProject routing problem.
  • Review the related issues (#25189, #24517, and #24533) to see if any workarounds or temporary fixes have been suggested by the community.
  • Consider reaching out to the Gemini CLI support team to report the issue and ask for an estimated timeline for a fix.
  • If possible, try to test the CLI with a different authentication method (if available) to see if the issue is specific to the oauth-personal auth.

Example

No code snippet is provided as the issue seems to be related to a server-side change and not a code-specific problem.

Notes

The issue seems to be specific to the official Gemini CLI and not related to any third-party tools. The fact that the issue occurs on different machines and OS suggests that the problem is indeed server-side.

Recommendation

Apply workaround: Wait for an official update or patch from the Gemini CLI team, as the issue seems to be related to a server-side change. This is the safest approach, as attempting to modify the CLI or authentication method could potentially introduce new issues.

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#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

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

Back to top recommendations

TRENDING