gemini-cli - 💡(How to fix) Fix 403 forbidden for gemini cli using [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#25446Fetched 2026-04-16 07:06:22
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
0
Timeline (top)
commented ×3labeled ×3closed ×1cross-referenced ×1

Code Example

> /about
 About Gemini CLI│                                                                                                                      │
CLI Version                              0.32.1Git Commit                               e8a57c78c                                                                   │
Model                                    Auto (Gemini 3)Sandbox                                  no sandbox                                                                  │
OS                                       win32                                                                       │
Auth MethodTier                                     Gemini Code Assist in Google One AI Pro
RAW_BUFFERClick to expand / collapse

What happened?

after i mistakenly created a google cloud project, by following the insturction of goole assist extension of vscode, i am unable to fix the 403 forbidden problem in gemini CLI even i delete the gcloud project later. i think i am a personal account with no organization (it is shown in gcloud project too).

What did you expect to happen?

personal account should not be asked to create gcloud project at all as the markdown file suggest the most situation.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
 About Gemini CLI                                                                                                     │
│                                                                                                                      │
│ CLI Version                              0.32.1                                                                      │
│ Git Commit                               e8a57c78c                                                                   │
│ Model                                    Auto (Gemini 3)                                                             │
│ Sandbox                                  no sandbox                                                                  │
│ OS                                       win32                                                                       │
│ Auth Method                                           │
│ Tier                                     Gemini Code Assist in Google One AI Pro
</details>

Login information

No response

Anything else we need to know?

i used to use the google assist extension and gemini cli successfully, only encounter the gcloud project request today

extent analysis

TL;DR

The 403 Forbidden problem in Gemini CLI may be resolved by re-authenticating or re-configuring the Google Cloud project settings.

Guidance

  • Verify that the Google Cloud project deletion was successful and there are no remaining resources or permissions associated with the deleted project.
  • Check the Gemini CLI authentication method and ensure it is not trying to use the deleted Google Cloud project for authentication.
  • Try re-authenticating with the Gemini CLI using the /login command to see if it resolves the 403 Forbidden issue.
  • If the issue persists, try resetting the Google Assist extension settings in VSCode to ensure it is not causing any conflicts with the Gemini CLI.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The root cause of the issue is unclear, and it may be related to the Google Cloud project deletion or the Gemini CLI authentication method. Further investigation is needed to determine the exact cause.

Recommendation

Apply workaround: Re-authenticate with the Gemini CLI using the /login command, as it may resolve the 403 Forbidden issue without requiring a full fix.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING