Antigravity stuck in “Further action is required” loop after successful age verification

Hello Google Antigravity Team,

I am experiencing a persistent account verification/sign-in loop with Google Antigravity.

My Google Account age verification has already been completed successfully, and the Google Account page confirms that my age is verified.

However, Antigravity continues to display:

“Further action is required to use Antigravity. Please verify your account, then sign in again to continue.”

I have already completed the following troubleshooting:

  • Completed Google Account age verification successfully.
  • Uninstalled Antigravity and restarted Windows 11.
  • Installed a fresh copy of Antigravity 2.0 from the official Google Antigravity website.
  • Removed all existing Google Antigravity authorizations from Google Account → Linked apps.
  • Confirmed that Google Antigravity no longer appeared under Linked apps.
  • Completely closed VS Code and its background process.
  • Started Antigravity 2.0 by itself.
  • Performed a fresh Google sign-in.

The authentication process completes in the browser, but Antigravity returns to the same “Further action is required” screen.

I have also reproduced the Verification Required problem using the official Google Antigravity extension for VS Code.

Because the issue persists across both Antigravity 2.0 and the official VS Code extension even after age verification, a clean installation, authorization reset, and fresh sign-in, could the Antigravity team please check whether there is an account-side verification, eligibility, authentication, or entitlement/provisioning issue?

I can provide the relevant Error ID and screenshots if needed.

Thank you.

Hi @prasit_pratumrat2,

Welcome to the Forum,

Could you please confirm If your 2-Step Verification is configured and that there are no pending security alerts on your account?

Additionally, if you are using a VPN or specific network routing, try disabling it temporarily to see if the authentication completes successfully, as network-level risk flags can sometimes trigger this loop.