Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Gemini CLI v0.38.2 – 403 PERMISSION_DENIED despite active Google One AI Ultra subscription [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#25603•Fetched 2026-04-18 05:57:25
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
andreyrequestandreyrequest
Participants
andreyrequestandreyrequestgemini-cli[bot]gemini-cli[bot]juntaosunjuntaosun
Timeline (top)
labeled ×3commented ×2cross-referenced ×2mentioned ×1

Error Message

I am experiencing a persistent API error in Gemini CLI v0.38.2: text× API Error: [{ "error": { The error started approximately one week ago (around April 10, 2026) and completely prevents me from using the CLI. Subscription is active and paid, but I still get 403 PERMISSION_DENIED error.

Fix Action

Fix / Workaround

This appears to be the same entitlement/sync bug that several other Ultra users are reporting in April 2026. Could you please escalate this to the engineering team? Any temporary workaround or ETA for a fix would be greatly appreciated. Thank you!

RAW_BUFFERClick to expand / collapse

What happened?

Hi, I am experiencing a persistent API error in Gemini CLI v0.38.2: text× API Error: [{ "error": { "code": 403, "message": "The caller does not have permission", ... "status": "PERMISSION_DENIED" } }]

I am signed in using Google /auth (not an API key). My plan shows correctly as “Gemini Code Assist in Google One AI Ultra” and the subscription is active and paid. The error started approximately one week ago (around April 10, 2026) and completely prevents me from using the CLI. I have tried logging out/in again, deleting tokens, and restarting — the issue remains. I have also opened a support ticket with Google One and it was escalated to the higher/engineering team today.

This appears to be the same entitlement/sync bug that several other Ultra users are reporting in April 2026. Could you please escalate this to the engineering team? Any temporary workaround or ETA for a fix would be greatly appreciated. Thank you!

My account: mayabioroboticsai

What did you expect to happen?

I expected that after signing in with Google /auth, Gemini CLI v0.38.2 would correctly recognize my active and paid Google One AI Ultra subscription and let me use the CLI normally with full Ultra limits. The CLI itself shows:

“Signed in with Google /auth” “Plan: Gemini Code Assist in Google One AI Ultra”

Instead, every command fails with 403 PERMISSION_DENIED (“The caller does not have permission”). This started about one week ago and completely prevents me from working with the tool.

Client information

About Gemini CLI │ │ │ │ CLI Version 0.38.2 │ │ Git Commit b0ed611a0 │ │ Model Auto (Gemini 3) │ │ Sandbox no sandbox │ │ OS linux │ │ Auth Method Signed in with Google ([email protected]) │ │ Tier Gemini Code Assist in Google One AI Ultra │ │

Login information

My account: mayabioroboticsai I am logging in with Google Account using the /auth command (not API key).

The CLI correctly shows:

  • Signed in with Google /auth
  • Plan: Gemini Code Assist in Google One AI Ultra

Subscription is active and paid, but I still get 403 PERMISSION_DENIED error.

Anything else we need to know?

No response

extent analysis

TL;DR

The most likely fix is to wait for the engineering team to resolve the entitlement/sync bug that is causing the 403 PERMISSION_DENIED error for Gemini Code Assist in Google One AI Ultra users.

Guidance

  • The issue appears to be related to an entitlement/sync bug that is affecting multiple Ultra users, so it's likely a server-side problem that requires a fix from the engineering team.
  • Since the user has already tried logging out and in, deleting tokens, and restarting, and the issue remains, it's unlikely that a simple workaround will resolve the problem.
  • The user has already opened a support ticket with Google One, which has been escalated to the higher/engineering team, so the best course of action is to wait for an update from the team.
  • In the meantime, the user can try to check for any updates on the Gemini CLI or Google One AI Ultra subscription status to see if there are any changes that may affect the issue.

Notes

The issue seems to be a known problem that is being worked on by the engineering team, so it's likely that a fix will be available soon. However, without more information about the bug or the team's progress, it's difficult to provide a more specific solution or timeline.

Recommendation

Apply workaround: Wait for the engineering team to resolve the entitlement/sync bug, as it's likely that a server-side fix is required to resolve the issue.

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#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

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

Back to top recommendations

TRENDING