gemini-cli - 💡(How to fix) Fix [Bug] OAuth auto-created project has no IAM permissions — all requests return 429 [3 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

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#26421Fetched 2026-05-05 06:03:56
View on GitHub
Comments
3
Participants
4
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×3labeled ×1
RAW_BUFFERClick to expand / collapse

Describe the bug Fresh install of Gemini CLI v0.40.1 on Windows. After OAuth login, the auto-created GCP project impactful-gauge-28k8m was generated without granting any IAM permissions to my account. All API requests to cloudcode-pa.googleapis.com return HTTP 429 RESOURCE_EXHAUSTED — even from the very first message. Cannot access the project in GCP Console ("Missing resourcemanager.projects.get"). Re-authentication does not create a new project.

To Reproduce

  1. Install gemini-cli v0.40.1 on Windows 11
  2. Run gemini, authenticate with Google OAuth (Google One AI Pro subscriber)
  3. Type any message — "Thinking..." spins forever
  4. Debug log shows 429 on both retrieveUserQuota and generateContent

Expected behavior Project should be created with proper IAM permissions so OAuth-authenticated users can use Gemini CLI.

Environment:

  • OS: Windows 11
  • Gemini CLI version: 0.40.1
  • Auth method: OAuth (Google One AI Pro)
  • GCP Project: impactful-gauge-28k8m
  • Account: [email protected]

extent analysis

TL;DR

The issue may be resolved by manually assigning the necessary IAM permissions to the user account in the auto-created GCP project.

Guidance

  • Verify that the IAM permissions are indeed missing by checking the project's IAM settings in the GCP Console.
  • Check the debug log for any specific error messages related to authentication or authorization that may indicate the root cause of the issue.
  • Attempt to manually assign the necessary IAM permissions to the user account [email protected] in the project impactful-gauge-28k8m to see if it resolves the issue.
  • If re-authentication does not create a new project, try deleting the existing project and re-running the authentication process to see if it creates a new project with the correct permissions.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue may be specific to the Gemini CLI version 0.40.1 or the OAuth authentication method used. Further investigation may be required to determine the root cause of the issue.

Recommendation

Apply workaround: Manually assign the necessary IAM permissions to the user account in the auto-created GCP project, as this may resolve the issue and allow the user to access the project and use the Gemini CLI.

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