gemini-cli - 💡(How to fix) Fix Gemini Code Assist VS Code: account bound to inaccessible phantom project ID (online-geode-fdt91) - cannot login [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#25674Fetched 2026-04-20 12:15:35
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Timeline (top)
labeled ×1

Root Cause

Root cause: phantom project ID comes from cloudcode-pa.googleapis.com/v1internal:loadCodeAssist server response, not local storage. Cannot be fixed locally.

RAW_BUFFERClick to expand / collapse

Account email: [email protected] OS: Windows 11 VS Code: 1.116.0 Extension version: 2.77.2 (also tried 2.78.0)

Problem: After signing in, the extension automatically sets project ID "online-geode-fdt91" in geminicodeassist.project setting. This project does NOT exist in my Google Cloud Console and I have no access to it. Worked fine on April 19, 2026. Broke on April 20, 2026.

Steps already tried:

  • Deleted geminicodeassist.project from settings.json (regenerates automatically from server every time)
  • Downgraded extension to 2.77.2 and 2.77.3
  • Changed project ID to my own project gemini-vscode-493822 (Gemini API enabled, IAM permissions set correctly)
  • Cleared VS Code globalStorage cache
  • Added geminicodeassist.apiKey in settings.json
  • Revoked Google account permissions

Additional info: This account is a Google One AI Ultra subscriber (paid plan). This bug is completely blocking paid professional work.

Root cause: phantom project ID comes from cloudcode-pa.googleapis.com/v1internal:loadCodeAssist server response, not local storage. Cannot be fixed locally.

Please reset the cloudaicompanionProject server-side binding for this account.

extent analysis

TL;DR

The issue can likely be resolved by resetting the cloud-side binding for the account, which is currently setting a non-existent project ID.

Guidance

  • The problem seems to stem from a server-side issue, where the cloudcode-pa.googleapis.com/v1internal:loadCodeAssist server response is providing a phantom project ID that does not exist in the user's Google Cloud Console.
  • To verify the issue, check the project ID being set in the geminicodeassist.project setting after signing in and ensure it matches the expected project ID.
  • The user has already tried various local fixes, such as deleting settings, downgrading the extension, and revoking Google account permissions, but the issue persists, indicating a server-side problem.
  • The user should contact the extension support or Google Cloud support to request a reset of the cloud-side binding for their account.

Notes

The issue seems to be specific to the user's account and the Google One AI Ultra subscription, and the root cause is identified as a server-side issue, making local fixes ineffective.

Recommendation

Apply workaround: Contact the extension support or Google Cloud support to request a reset of the cloud-side binding for the account, as the issue is likely due to a server-side configuration problem.

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