Environment
• OS: Win 11
• Network: Home network, no VPN
• Auth method: Google OAuth
Antigravity IDE Version: 2.0.4
VSCode OSS Version: 1.107.0 (user setup)
Commit: def9583aef9852ff94cb0dea16ede9bb6b095b30
Date: 2026-06-02T00:22:56.234Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Language Server CL: 924974766
Issue Summary
I cannot sign in to Antigravity with my Google AI Pro account. My secondary free Gmail account logs in immediately on the same machine and network, isolating the problem to an account-level entitlement failure, not a device or network issue.
Error
“Eligibility check failed: failed to get load code assist response: failed to make code assist backend request”
Simultaneously, the Gemini Code Assist extension in VS Code returns:
“Your current account is not eligible for Gemini Code Assist for individuals, the free version of Gemini Code Assist.”
Troubleshooting Completed
• Cleared Antigravity Session Storage and Local Storage
• Revoked all third-party OAuth connections at myaccount.google.com/connections
• Audited Google Cloud Console — checked for phantom auto-generated projects
• Reinstalled Antigravity fresh
• Signed in via Chrome exclusively
• No OpenClaw or third-party quota tools used
Hypothesis
Based on other threads here, this appears to be the known phantom Cloud Identity Org / Code Assist backend entitlement mismatch — where a personal Google AI Pro account is misidentified as a Workspace/enterprise account during the eligibility handshake, causing the Code Assist backend request to fail. The free account bypasses this check.
Key Isolation
Free Gmail → Antigravity login works
Free Gmail → Gemini Code Assist in VS Code works
Google AI Pro account → Both fail with the above errors
Urgency
Gemini Code Assist in VS Code is deprecated June 18, 2026. Antigravity is the only intended migration path, and my Pro subscription is actively blocking access to it.
Requesting:
- Confirmation this is a known bug
- Any backend entitlement force-sync steps
- ETA on a fix
Happy to provide account details via DM to a Google team mem