My personal Google account is stuck in an Antigravity eligibility loop

Google Antigravity
1

My personal Google account is stuck in an Antigravity eligibility loop.

  • Account: …9@gmail.com
  • Account type: consumer/personal Gmail
  • Antigravity IDE: 2.15.1 on Windows
  • Google Terms country: United States
  • OAuth completes successfully, and the browser reaches the Authentication successful page.
  • The antigravity://oauth-success callback reaches the client.
  • Google requests are routed through a stable US residential IP.
  • loadCodeAssist still returns HTTP 403 PERMISSION_DENIED with reason VALIDATION_REQUIRED.
  • Message: “Your current account is not eligible for Antigravity. Verify your account to continue.”
  • Completing the verification URL generates another verification challenge on the next login.
  • Logs show quotaProject= empty and userTier= empty.
  • Latest loadCodeAssist trace: 0xb364fe11f41b969c

Please re-provision or refresh the account’s Cloud Code Assist / Antigravity eligibility and entitlement state.

2

Hi @zhuxia_zhu,

Could you please follow these steps:

  1. Check your Google Payments profile by going to payments.google.com > Settings and ensure your active country is US, and remove any old/inactive foreign payment profiles.
  2. If you’re physically located in an officially supported country (most regions are supported natively), disconnect from the proxy completely. Direct connections usually pass the check without tripping risk filters.
  3. Revoke existing app permissions by going to myaccount.google.com/connections and remove Google Antigravity / Google Cloud Code.
  4. Clear Windows credentials & cache:
    • Close Antigravity and delete %APPDATA%\Antigravity and %USERPROFILE%\.gemini.
    • Open Windows Credential Manager (control keymgr.dll) and remove any stored credentials related to Antigravity or google.
    • Reopen the IDE, press Ctrl + Shift + P, run Antigravity: Reset Onboarding, and sign in fresh.

Let us know if that clears the challenge loop for you! or the issue still persists!.