Antigravity eligibility stuck after successful OAuth — 403 VALIDATION_REQUIRED / verification loop (Windows, Japan account)

Google Antigravity
1

Hello Antigravity Support Team,

I am unable to use Google Antigravity because my Google account remains stuck in an eligibility / verification loop, even though Google authentication itself succeeds.

Environment

  • Windows PC
  • Personal Gmail account
  • Google Terms of Service country/region: Japan
  • Antigravity IDE
  • Antigravity 2.0 desktop app
  • Antigravity CLI (agy, tested with CLI 1.2.12)

Main symptoms

  • Antigravity IDE completes Google OAuth in the browser, but the IDE still reports that the account is not eligible / not signed in.
  • Antigravity 2.0 displays “Verification Required – Please verify your account to continue using Antigravity.”
  • Antigravity CLI reports:

Eligibility check failed: Your current account is not eligible for Antigravity. Verify your account to continue.

Important backend evidence

The IDE logs show that authentication itself succeeds:

Auth succeeded, refreshing features and managers

But immediately afterward, the Code Assist backend returns:

403 PERMISSION_DENIED

reason: VALIDATION_REQUIRED

Verify your account to continue.

The IDE then changes the authentication state to loginError.

Verification behavior

  • The backend provides a Google validation_url.
  • Opening that URL and completing Google authentication can reach an “Authentication successful” page.
  • I also successfully completed a Google Prompt verification on an already signed-in phone.
  • However, Antigravity still fails the eligibility check afterward.
  • Another verification flow asks me to scan a QR code and send an SMS to Google short code 244444. My mobile carrier cannot send SMS to this short code, so that verification method cannot be completed.

Troubleshooting already performed

  • Confirmed the Google Terms country is Japan, which is an Antigravity-supported country.
  • Confirmed Google OAuth completes successfully.
  • Confirmed the antigravity-ide:// protocol correctly launches Antigravity IDE.
  • Confirmed the local OAuth callback server starts successfully.
  • Removed the Windows credential:

gemini:antigravity

  • Backed up and reset the Antigravity CLI local session data.
  • Performed a completely fresh Google OAuth login.
  • Tested Antigravity CLI independently from the IDE.
  • Tested on a direct network connection where Google/OpenAI connectivity works normally.
  • Tested again through Clash Verge using a stable Japan exit node.
  • Explicitly set:

HTTP_PROXY=http://127.0.0.1:7897

HTTPS_PROXY=http://127.0.0.1:7897

NO_PROXY=localhost,127.0.0.1,::1

  • Verified through curl that the Japan proxy can access both Google Accounts and OpenAI successfully.
  • Reauthenticated from scratch while Antigravity CLI was explicitly using that Japan proxy.
  • The result is still exactly the same:

Eligibility check failed: Your current account is not eligible for Antigravity. Verify your account to continue.

Because the same account-level error occurs in Antigravity IDE, Antigravity 2.0, and Antigravity CLI, and persists after a completely fresh OAuth session on multiple working network paths, this appears to be an account-side Antigravity / Gemini Code Assist entitlement or verification-state issue rather than a local installation or network issue.

Could someone from the Antigravity team please check the backend eligibility / verification / entitlement state for my account and refresh or correct it if necessary?

If the 244444 SMS challenge is mandatory, could you also provide an alternative verification method, since my carrier cannot send messages to that short code?

I can provide sanitized auth.log, ls-main.log, trace IDs, screenshots, and error IDs if needed.

Thank you.

2

Hi @RisingSun,

Welcome to the Forum.

Please try the below steps to resolve:

  1. Update to the Latest Official Releases (Changelog):

    • Ensure you are running Antigravity 2.0 v2.18.1 (which specifically fixes Google Sign-In browser security and incomplete session issues), Antigravity CLI v1.2.11, and Antigravity IDE v2.5.5.

  2. Confirm Account Security Alerts & Age Eligibility (FAQ):

  3. Reset Onboarding & Verify in Antigravity 2.0 Without a Proxy:

    • Turn off Clash Verge and clear HTTP_PROXY / HTTPS_PROXY (routing through a proxy exit node often triggers the 244444 SMS challenge and invalidates Google Prompt verification).
    • In Antigravity IDE, open the Command Palette (Ctrl+Shift+P) and run Antigravity: Reset Onboarding.
    • Sign in to Antigravity 2.0 (v2.18.1) using a fresh Incognito browser window, send a short prompt/message to actively trigger and persist the account verification, and then sign back into Antigravity IDE with the same account.

If the 403 VALIDATION_REQUIRED error still persists after these steps, please share your sanitized auth.log, ls-main.log, and trace IDs in a .txt file .