Your account is not eligible for Gemini Code Assist for individuals at this time

Title: Antigravity IDE Google AI Pro login fails with state syncing error: key not found

Hello Google Antigravity Team,

I am experiencing a persistent authentication problem with Antigravity IDE 2.5.5 on Windows.

Environment

  • OS: Windows 11
  • Antigravity IDE: latest version available to me
  • Google account: Personal Gmail account with an active Google AI Pro subscription
  • Browser authentication: successful
  • Another Gmail account without Google AI Pro: able to log in on the same PC and network

Problem

When I log in to Antigravity IDE using my Google AI Pro account, Google authentication completes successfully, but Antigravity then shows:

Your account is not eligible for Gemini Code Assist for individuals at this time

The same computer and network can successfully log in using another Gmail account.

Troubleshooting already performed

I have tried:

  1. Resetting the Antigravity onboarding.

  2. Completely closing Antigravity IDE.

  3. Renaming the following directories to create a clean profile:

    • %APPDATA%\Antigravity IDE
    • %APPDATA%\Antigravity
  4. Starting Antigravity again and logging in from a clean profile.

  5. Re-authenticating through Google.

  6. Removing the Windows Credential Manager entry:
    LegacyGeneric:target=gemini:antigravity

  7. Logging in again after the credential was removed.

The problem persists after all of these steps.

Relevant Antigravity logs

The new clean-profile logs repeatedly show:

Failed to get OAuth token:
error getting token source from auth provider:
state syncing error: key not found

and:

failed to get load code assist response:
error getting token source:
state syncing error: key not found

The following is also reported:

Failed to get CAIC project: key not found

Additional related messages:

Cache(loadCodeAssistResponse): Singleflight refresh failed:
error getting token source: state syncing error: key not found
Cache(userInfo): Singleflight refresh failed:
failed to get load code assist response:
error getting token source: state syncing error: key not found

The errors occur immediately after successful Google authentication.

Local state investigation

I also inspected the newly generated Antigravity profile.

globalStorage\state.vscdb does not contain authentication-related keys such as:

auth
account
google
credential
token
identity

The storage metadata contains:

"antigravityUnifiedStateSync.oauthToken.hasLegacyMigrated": true

and:

"unifiedStateSync.hasUserStatusMigrated": true

However, the Antigravity authentication provider still fails with:

state syncing error: key not found

Important comparison

The same PC and network can authenticate another Gmail account successfully.

The failure appears specifically when using my Google AI Pro account.

Therefore, could the Antigravity team please investigate whether the Google AI Pro account’s Antigravity provisioning, OAuth state synchronization, or CAIC project initialization is failing?

In particular, I would appreciate checking why Antigravity reports:

Failed to get CAIC project: key not found

and why the OAuth token source cannot retrieve the required state after successful Google authentication.

I can provide sanitized Antigravity logs and additional diagnostic information if required.

Thank you.

Hi @cs_buat_aplikasi,

Welcome to the Forum,

Thank you for reporting. This isn’t related to your Google AI Pro plan. Antigravity checks your account again each time you sign in and sometimes it asks for verification even if nothing has changed.

To resolve this, please try the following troubleshooting steps:

  • Download the latest version of Antigravity 2.0 from the official page and sign in. You will be prompted to complete verification.
  • If you scan the QR code and the verification gets stuck or fails to unblock your account (a known issue currently affecting some users), please try using an alternate verification method. You can do this by opening the verification link on an Android phone or tablet already signed into your account, and selecting options like “Device check” instead of SMS.
  • Verify that your region and age settings meet Google account requirements.