Pricing

Antigravity "Verification Required" and Eligibility Check Errors: How to Fix Them

Antigravity stuck on verification or "eligibility check failed"? Why it happens (age, region, plan), fixes from Antigravity's GitHub issues, and what to check.

By Engineer Foodie Desk Nov 3, 2026 ✓ Sources checked Nov 3, 2026

8 min read

Error wording, eligibility rules and fixes checked Nov 3, 2026 in Antigravity’s FAQ and four open issues on Google’s antigravity-cli GitHub: #785, #991, #950 and #1299. The /logout command was checked Nov 2, 2026 in the CLI reference. Student offer terms checked Oct 29, 2026. Every source is listed at the bottom. No affiliate links on this page (how we work).

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

Here’s the CLI version, word for word from #991:

Eligibility check failed: Your current account is not eligible for Antigravity. Verify your account to continue.
Alternatively, try signing in with another personal Google account.
Please verify your account in your browser to continue: ...

The Antigravity desktop app says it shorter. A user on the same issue reports that “Desktop continues to show “Verification required,” and agent requests fail with “Error Verification Required."" Under the hood, logs posted in #785 show PERMISSION_DENIED (code 403): Verify your account to continue. with reason: VALIDATION_REQUIRED.

One-line answer: Google’s server hasn’t marked your Google account as eligible for Antigravity yet, usually because of location, age or account type, so check those three, finish the account verification in the same browser profile, then sign out and back in.

Annoyingly, your password and OAuth sign-in are usually fine. People in these issues sign in successfully, see “Authentication successful” in the browser, and still get bounced. It’s Seinfeld’s “The Parking Garage”: you’re sure the car is right here, you’ve walked past the same pillar five times, and you still can’t leave.

What Antigravity checks

Google’s FAQ lists three checks for personal accounts. Personal Google accounts (like @gmail.com) “can use Google Antigravity on any plan, including the free tier” (FAQ, verified Nov 3, 2026). Paying isn’t one of the checks. These are:

Check	Rule	Where
Location	Supported country	Google Terms page
Age	18 or older	Age verification
Account	Personal, or provisioned	Your admin

Source: Antigravity FAQ, verified Nov 3, 2026.

Location. Your account “must be associated with a country or territory where Antigravity is available.” The FAQ has the full list by region (India, Singapore, Taiwan, Japan and the US are on it; mainland China isn’t). What matters is the country tied to your Google account, not where your laptop is. Google says to check it on the Google Terms of Service page. If it’s wrong, submit a request to change it.

Age. “Antigravity is unavailable to users under 18.” If you’re 18 or older and Google doesn’t know it, verify your age.

Account type. Work and school accounts “aren’t personal Google Accounts.” A Google Workspace admin “must explicitly provision Antigravity for your account”. Gemini Enterprise users pick Business account at sign-in and need a license or IAM role from their admin. AI developer tools “may be turned off by default” for them. And enterprise sign-in doesn’t work in the standalone Antigravity IDE, only in the app, CLI and IDE extensions (all from the FAQ).

On top of those three, the issues show a fourth gate: an in-app phone or identity verification that Google triggers on some accounts. That’s the “Verify your account to continue” link. Google doesn’t document when or why it appears.

Fixes in order

Each fix says where it comes from. Nothing here involves VPN country hopping, switching between accounts you’ve made for this, or third-party wrappers. Google’s FAQ says using third-party software with your Antigravity login “is a violation of our Terms of Service” and can get the account suspended, and automating account rotation “is not supported.” Don’t turn a sign-in problem into a ban.

1. Check the country on your Google account (per docs, and the maintainer reply in #991 and #785). Open policies.google.com/terms while signed in to the same account and see which country it shows. If it’s wrong, file the country-association form. On both issues a Google collaborator gave the same advice: check the supported list, check the ToS country, and request a change if it’s wrong. Fair warning: in #785 the reporter’s account was set to Japan, which is supported, and still got the error. Country is the first check, not a guarantee.

2. Verify your age (per docs). Do it on Google’s age verification page. #1299 shows that age verification alone doesn’t always clear it, but if it’s missing you’re blocked for sure.

3. Use the right account type (per docs). On a Workspace or school account, ask your admin to provision Antigravity, or sign in with a personal account. On Gemini Enterprise, choose Business account and confirm you have a license.

4. Complete the in-app verification, then sign in fresh (reported in #785). One user saw “Please complete verification” in the corner of the app, scanned the QR code with their phone, and “everything worked normally again.” A commenter on #785 and #1299 adds that the verification link is tied to the exact account. Open it in the browser profile signed in to that Google account, then get fresh tokens instead of reusing the old ones. The clean, documented way to do that is /logout, which will “Disconnect your profile and purge authentication tokens from the secure keyring” (CLI reference, verified Nov 2, 2026), then sign in again.

5. Remove proxies from the equation (reported in #1299). The #1299 reporter’s launcher ran through a local proxy, and a commenter suspects the source IP of model requests is checked separately from the browser’s. That’s a user theory, not a Google statement. The safe version is: try once on a plain home or office connection, without proxies or VPNs. Don’t use a VPN to fake a supported country. That’s exactly the location check working as designed.

6. On a headless server, make the sign-in stick first (reported in #950). On an Ubuntu VPS, the #950 reporter found the token didn’t persist until they set GEMINI_FORCE_FILE_STORAGE=true, and only then hit the eligibility error. The same person found another personal account worked on the same VPS, and the maintainer replied “it could be an account-related issue.” So if your token won’t save, fix that first. Otherwise you’re debugging two problems at once.

7. If the SMS step hangs, stop retrying and report it (reported in #991 and #950). Several users say the verification page sits on “This may take a few minutes” after the SMS is sent, on more than one carrier. Nobody in the threads has a fix for that. Google’s FAQ sends support questions to the communities on its support page, and #785 is where the open reports are collected. In #785, the reporter’s account started working again on Oct 23, 2026, and they wrote they had “not confirmed what caused the issue to be resolved.” It’s Newman at the door. You can say “Hello, Newman” through gritted teeth all you like, but only Google can let you in.

Paid but still blocked?

Yes, it happens, and it’s the most frustrating version. The #991 reporter is on Google AI Pro in Taiwan, a supported location. A commenter on #785 has an active AI Pro subscription, completed age verification, and still gets 403 VALIDATION_REQUIRED. Another #991 commenter wrote, less politely, “I paid the sub for getting this weird error.” The #950 reporter got Google AI Plus through a student benefit and was blocked too.

Paying for Google AI Pro raises your Antigravity limits. It doesn’t skip the eligibility gate. Location, age and account checks still apply. If you’re a student, Google’s free year of AI Pro is for “eligible U.S. college students ages 18+” (gemini.google/students, verified Oct 29, 2026). Our Antigravity student offer post covers the details, but the same age and location rules apply after you claim it.

I’ll be honest: this is a bad look for Google. Taking money for Google AI Pro, then telling the same account it’s “not eligible” with no documented reason, no ETA and a GitHub thread as the support desk, is rough. #785 has been open since Aug 13, 2026.

Here’s what I’d do

Check the ToS country, age verification and account type. That’s five minutes and covers what Google documents.
Do the in-app verification in the right browser profile, then /logout and sign in again.
Try one clean connection without proxies.
If it still loops, add your details (version, OS, plan, country) to #785 rather than opening a new issue, and don’t post your email address publicly.
Meanwhile, keep working. A different signed-in personal account that already passes is fine. Making new accounts to dodge the check isn’t. If you need to ship code, see Antigravity vs Cursor or the AI coding tools comparison.

Once you’re in, the next errors you’ll meet are limits, not eligibility: Antigravity individual quota reached and Antigravity agent execution terminated. And if you’re wondering what you get without paying, see Is Antigravity free?.

Getting a 400 “User location is not supported” or INVALID_ARGUMENT instead of a verification wall? See Antigravity Error 400.

FAQ

Why does Antigravity say verification required? Google hasn’t marked your account as eligible yet, so check your account country, verify your age at 18 or older, use a personal or admin-provisioned account, and finish the in-app verification.

What does “Eligibility check failed: Your current account is not eligible for Antigravity. Verify your account to continue.” mean? It’s the CLI version of the same gate, and Google’s maintainers point to the supported-country list and the country shown on your Google Terms of Service page.

Why does Antigravity eligibility check fail with Google AI Pro? A paid plan raises limits but doesn’t bypass the location, age and account checks, and open issues #991 and #785 show AI Pro users still blocked.

Can I use Antigravity with a Workspace account? Only if your Workspace admin explicitly provisions Antigravity for you, otherwise sign in with a personal Google account.

Does a VPN fix Antigravity verification required? No, using a VPN to look like you’re in a supported country works against Google’s location check, so fix the country on your account instead.

Sources

Google Antigravity FAQ (personal accounts, location, age, account type, country list, ToS on third-party software): https://antigravity.google/docs/faq (verified 2026-11-03)
GitHub issue #785, PERMISSION_DENIED (code 403): Verify your account to continue. / VALIDATION_REQUIRED: https://github.com/google-antigravity/antigravity-cli/issues/785 (verified 2026-11-03)
GitHub issue #991, eligibility check failed on Google AI Pro, “Verification required” in Desktop: https://github.com/google-antigravity/antigravity-cli/issues/991 (verified 2026-11-03)
GitHub issue #950, headless VPS, token storage and eligibility: https://github.com/google-antigravity/antigravity-cli/issues/950 (verified 2026-11-03)
GitHub issue #1299, verification loop after successful sign-in (marked duplicate of #785): https://github.com/google-antigravity/antigravity-cli/issues/1299 (verified 2026-11-03)
Google Antigravity CLI reference, /logout: https://antigravity.google/docs/cli/reference (verified 2026-11-02)
Google Terms of Service country check: https://policies.google.com/terms and country change form: https://policies.google.com/country-association-form (linked from the FAQ, verified 2026-11-03)
Google AI Pro student offer: https://gemini.google/students/ (verified 2026-10-29)