Antigravity "Account Not Eligible" / "Ineligible": What Each Error Means and How to Fix It

Updated October 30, 2026. Facts re-checked against the Antigravity FAQ, Terms and changelog, plus replies from Google staff on the Google AI Developers Forum.

Antigravity shows several different "not eligible" messages, and they do not all have the same cause. This page lists each exact message, what it means, and the steps that fix it. If your problem is instead a login that never finishes (stuck on "Awaiting Authentication", no browser redirect), use the Antigravity Unable to Sign In guide.

Find Your Exact Error

"Sorry, this account is ineligible to use Antigravity"

What it means: Antigravity looked at your Google Account and refused it. When the second line is present, the stated reason is location.

Cause: a Google staff reply on the forum states Antigravity evaluates location strictly from the country associated with your Google Account (the country on the Terms of Service page), not your Google Play country, billing address or current IP address. The message appears when that country is not on the supported list, or when the association is out of sync (for example an account created in another country, or recently changed). Users with a US-associated account have reported it, and staff pointed them at the steps below. Without the "location" line, the same dialog can also be caused by age or account type.

Fix:

1. Sign in to the affected account in a browser and open policies.google.com/terms to see the country associated with it.
2. Compare it to the supported list in the FAQ. If it is on the list, go to step 3. If it is not and it is the wrong country, follow Check Your Country Association. If it is the right country and not on the list, Antigravity is not available for that account; see Supported Regions.
3. Confirm the account is a personal Google Account (Workspace accounts need admin provisioning) and that age verification (18+) is complete at myaccount.google.com/age-verification. Google staff say recent age changes can take 24 to 48 hours to propagate.
4. On pay.google.com open the profile selector (top left) and make sure there is no secondary or older payment profile tied to another country. Staff list this as a cause of an out-of-sync association.
5. Revoke the cached grant: open myaccount.google.com/permissions, select Google Antigravity and remove access. Signing out inside the app does not revoke the server-side grant.
6. Sign back in using the sign-in URL pasted into a private/incognito window with only that account signed in, then run Antigravity: Reset Onboarding from the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) if the app keeps the old result.

Source: Google staff replies in the forum threads 191504 and 192063.

"Eligibility check failed: your current account is not eligible for Antigravity" (CLI)

What it means: sign-in (OAuth) worked, but the next account check did not pass. The CLI usually prints a verification link under this message.

Cause: user logs attached to antigravity-cli issue #785 show the backend answering 403 PERMISSION_DENIED with reason VALIDATION_REQUIRED and the text "Verify your account to continue". In other words it is an account verification requirement, not necessarily a region block. Google's own reply on that issue says to check that the country on the Terms of Service page is a supported location. This reading of the logs comes from user reports; Google has not published a description of the internal reason code.

Fix:

1. Check the country on policies.google.com/terms against the supported list, and age verification (18+) at myaccount.google.com/age-verification.
2. Confirm 2-Step Verification is on at myaccount.google.com/signinoptions/two-step-verification. Google staff list it as a requirement to check.
3. Open the CLI's verification link in a private window signed in to only that one account. With several accounts signed in, the check can attach to the wrong browser session (staff reply, forum thread 179397).
4. Finish the verification (QR code and phone prompt) until the page confirms success.
5. In agy, run /logout, quit, run agy update, start agy and sign in again so the new session carries the verified state.
6. If the SMS step never completes, verify the phone number directly in your account instead: open myaccount.google.com/phone and confirm it with an incoming code or voice call. Users in Spain and Armenia reported the QR/SMS step failing; a Google staff reply on the Armenian case recommended this route and then running Reset Onboarding.

"Further action is required to use Antigravity"

What it means: this is the verification gate from the section above, shown in the desktop app or IDE. A Google staff reply notes that seeing this screen, rather than a location message, means your region passed and the account is hitting a Google Account security or verification check.

Typical loop: you click Verify, the browser says "You have successfully authenticated", you return to Antigravity, and the same message appears again.

Fix (from Google staff replies):

1. Sign out of all other Google accounts in your default browser so only one established personal Gmail account is signed in. With several accounts active, Verify can apply to a different browser session than the one you chose when you click Sign in again.
2. On that account, confirm the country association at policies.google.com/terms, age verification (18+), 2-Step Verification, and a verified recovery phone (a standard mobile number).
3. With only that account active, click Verify in Antigravity and complete the prompt.
4. Wait a few minutes (up to 30 to 60 minutes if earlier attempts used several accounts), fully close and relaunch Antigravity, then click Sign in again.
5. If the browser step ends on accounts.google.com/signin/continue with "500" or "We couldn't verify your info": complete age verification directly at myaccount.google.com/age-verification rather than through the redirect, turn off any VPN, proxy or header-altering extension for the attempt, update to the latest release, and test whether signing in with agy returns a specific eligibility message.
6. Check Google Account Security for pending "Is this you?" prompts, then run Antigravity: Reset Onboarding and sign in again.

Source: staff replies in forum threads 196453, 190133 and 189894. These are workarounds from staff replies, not a documented guaranteed fix.

"This account isn't eligible for Google Antigravity benefits included with Google AI plans"

What it means: this message comes from the Google One / Google AI plans side (for example after clicking Get Plan), not from the sign-in screen. It is about whether the account can receive the plan benefits. The follow-up text names two reasons: country and age.

Cause: the FAQ says personal accounts can use Antigravity on any plan including the free tier, but paid Google AI plans are not available everywhere. The FAQ lists regions that do not currently have access to Google One AI plans, which includes Türkiye and the U.S. Virgin Islands, among others. Users also report it on accounts they believe qualify; one forum thread is locked with no staff explanation, so the exact rule for those cases is not documented.

Fix:

1. Check the account's country on policies.google.com/terms against the "do not currently have access to Google One AI plans" list in the FAQ.
2. Complete age verification at myaccount.google.com/age-verification.
3. Make sure you are subscribing with the same Google Account you sign in with. In Antigravity, open Settings, then Account, to see which one is active, and sign out and in again if it is the wrong one.
4. If the account is in a listed country and no step changes it, there is no supported workaround; the free tier remains available where Antigravity itself is available.

Terms of Service Flag (Third-Party Tools, OpenClaw)

A sudden block on an account that worked before is often a Terms of Service action, not a region problem. Section 6 of the Antigravity Additional Terms says you must not abuse, harm, interfere with or disrupt the Service, including "using the Service in connection with products not provided by us", and gives the example of using OpenClaw with Antigravity OAuth as a breach that may lead to suspension or termination of Antigravity and/or Gemini CLI accounts. The FAQ repeats this for Claude Code, OpenClaw and OpenCode and recommends a Gemini Enterprise or Google AI Studio API key for third-party coding agents.

What Google has said about recovery (Google's post in gemini-cli discussion #20632, February 27, 2026): a system-wide automated unban was applied to recently flagged accounts, and going forward a flagged account gets an email and a specific error message that points to a Google Form. You review the terms, recertify that you will follow them, and the account is reinstated through a periodic sync, typically within a day or two. A second violation leads to a permanent ban. Because the abuse check sits in a shared backend layer, a block can affect Antigravity, Gemini CLI and Gemini Code Assist together.

If you used third-party software with your Antigravity login:

1. Stop using it and remove its access at myaccount.google.com/connections.
2. Look for the email or in-app message from Google and use the form it links to. Do not reconnect the tool.
3. If there is no message and the block continues, ask on the Antigravity forum. Outcomes for reported bans have been inconsistent, and no timeline is published.

A reported Gemini CLI wording for this case is "Gemini has been disabled in this account for violation of Terms of Service. If you believe this is an error, please contact Google Cloud Support" (from openclaw issue #14203, a user report). For the vaguer "There was an unexpected issue setting up your account", see the sign-in guide; that message is not always a ban.

Personal vs. Workspace Accounts

The FAQ says Workspace and Gemini Enterprise accounts are managed by your organization, and that your administrator must give the account access to Antigravity before you can sign in.

1. Workspace account: ask your Workspace administrator to provision Antigravity, or sign in with a personal Google Account instead.
2. Gemini Enterprise license: choose Business account when you sign in. A Google Cloud administrator must assign you a license or the required IAM role, and AI developer tools may need to be turned on for the region where the subscription is provisioned.
3. Same email, more than one identity provider: sign in with the identity that matches the license.
4. Enterprise sign-in works in the Antigravity App, Antigravity CLI and IDE extensions, but not in the standalone Antigravity IDE.

Age Requirement

Antigravity is unavailable to users under 18. If you meet the age requirement but the account shows as unverified, verify your age at myaccount.google.com/age-verification. Google's age verification help page says it may ask for a valid government ID or a credit card; a card check is an authorization, not a charge, and an uploaded ID is deleted after your date of birth is verified.

Check Your Country Association

Use this only if the country on your Terms of Service page is wrong, for example because you moved.

1. Open policies.google.com/terms while signed in to the affected account and read the country.
2. If it is wrong, submit the Google country association form (the Antigravity FAQ links to it) with the country you actually live in, and give an accurate reason. Google reviews the request; no processing time is published.
3. After approval, revoke the old grant at myaccount.google.com/permissions, sign in again in a private window and run Reset Onboarding.

The form is for correcting an account's real country. It is not a way around availability: if your actual country is not on the list, Antigravity is not available to you at this time.

Supported Regions

The FAQ states: "If you're not in one of these countries or territories, you can't use Google Antigravity at this time." It lists 224 countries and territories in five groups: Americas (51), Europe (47), Africa (56), Asia (43) and Oceania and Antarctica (27). Always check the live list, because it changes: antigravity.google/docs/faq.

Some places are not on the October 30, 2026 list, including mainland China, Hong Kong, Russia, Belarus, Moldova, Iran, Syria, North Korea and Cuba. Ukraine is listed for "supported territories". A previous version of this page said Ukraine was unsupported and quoted "200+" countries; both were out of date.

The Google One AI plans list is a separate, shorter exclusion list (see above).

Reset Local Sign-In State

After you change anything on the account, clear what the app cached:

1. Revoke Antigravity at myaccount.google.com/permissions.
2. In the app, open the Command Palette and run Antigravity: Reset Onboarding.
3. In agy, run /logout.
4. Update to the latest version, fully quit, relaunch, and sign in with one account in a private window.

For stuck sign-in screens and cache folders, see the Unable to Sign In guide. For the "This client is no longer supported for Gemini Code Assist for individuals" message, see Gemini CLI to Antigravity CLI migration.

If It Still Fails

If you have done the steps for your exact message and nothing changes, Google staff on the forum ask for these details, so collect them before posting at discuss.ai.google.dev/c/antigravity:

• The country shown on policies.google.com/terms.
• Whether the account is @gmail.com or Workspace.
• Whether the same error appears in the Antigravity CLI (agy), the App and the IDE.
• Your Antigravity version (Help, then About) and the time of the last failed attempt, with timezone.
• The exact message text, copied, with any email addresses removed.

The Antigravity support page lists the official communities. Other fixes: Troubleshooting Guide.

Earlier Guidance (March 2026)

This section keeps the guidance from earlier versions of this page so nothing is lost. Where an item is outdated or unverified, a dated note says so. For the current steps, use the sections above.

The 30-Second Fix

Earlier versions said most users solve this by changing their Google Account region to a supported country and signing in with a Personal Gmail account (not a corporate workspace account).

OpenClaw Ban & ToS Section 6 — Are You Affected? (Ongoing in 2026)

Community reports from March 2026 said the most common cause of a sudden "not eligible" flag was a Terms of Service enforcement action, not a region problem. Reports placed the start of the bans around February 12 to 14, 2026, when accounts that routed requests through OpenClaw's OAuth integration were reportedly banned from Antigravity. The relevant rule is Section 6 of the Antigravity Additional Terms, which says you must not "abuse, harm, interfere with, or disrupt the Service," including "using the Service in connection with products not provided by us." Earlier versions of this page described the enforcement as ongoing in 2026.

In plain terms, Section 6 bars pointing Antigravity at any backend that isn't Google's own: third-party OAuth proxies like OpenClaw, BYOK (bring-your-own-key) wrappers, local-model bridges, and custom relay servers. If your account suddenly shows "not eligible" or returns a 403 and you have used OpenClaw or a similar proxy, this is a likely cause.

Community posts attributed the reason to "use of Antigravity servers to power a non-Antigravity product" and a zero-tolerance policy, and quoted Varun Mohan, who leads Antigravity at Google, as citing a "massive increase in malicious usage of the Antigravity backend that has tremendously degraded the quality of service." We could not find an official source for these quotes.

How to recover (community-reported):

1. Uninstall or disconnect OpenClaw from your Antigravity account entirely. Community reports said OpenClaw's developer later removed Antigravity as a supported backend.
2. Clear stored auth tokens (see Advanced Fix: Clear Corrupted Auth Tokens below).
3. Wait 24 to 72 hours. Reports said Google was restoring restricted accounts for users who had removed third-party tool access.
4. If your account is still blocked after 72 hours, contact Google Support or ask on the Antigravity forum, and mention the third-party tool you removed.

Community reports (2026): ongoing eligibility and ban threads are tracked on GitHub and Google's own developer forum. See gemini-cli issue #15986 ("your current account is not eligible for Antigravity"), the "Addressing Antigravity Bans & Reinstating Access" discussion, and Google's "Please stop banning paid Antigravity subscribers for using OpenClaw (Error 403)" thread.

For sign-in issues unrelated to OpenClaw, see our full Antigravity Unable to Sign In fix guide.

"There Was an Unexpected Issue Setting Up Your Account"

A separate but related error, "There was an unexpected issue setting up your account. We apologize for the inconvenience. Please try again later.", has been widely reported since early 2026 and is distinct from the standard "account not eligible" message. It typically appears after a successful Google OAuth redirect, during the Antigravity desktop-app setup phase.

Common triggers (community-reported):

• Pro or Ultra subscription renewal dates (the account flag lags behind payment confirmation).
• Signing in immediately after a region change, before the change has propagated.
• Residual corrupted auth tokens from a previous failed login attempt.
• Using the app on a second device before completing setup on the first.

Step-by-step fix:

1. Force-quit Antigravity completely. Do not just close the window.
2. Clear your auth tokens using the commands in the Advanced Fix section below.
3. Open an Incognito / Private browser window and navigate to antigravity.google to verify your account is accessible there first.
4. Relaunch Antigravity and sign in fresh. Do not use "Sign in with a different account"; sign out fully first.
5. If the loop persists, wait 30 to 60 minutes before retrying. This is often a server-side flag sync delay, not a client problem.
6. On macOS: also try running defaults delete com.google.Antigravity in Terminal before relaunching.

Note: this error has also been reported on Antigravity Manager (a third-party wrapper). If you are using Antigravity Manager, update to the latest version or switch to the official Antigravity app.

Check If Your Region Is Supported

Earlier versions of this page said Google Antigravity is available in most countries worldwide, with notable exceptions. The sample below is from that earlier version:

• Americas: United States, Canada, Brazil, Mexico, Argentina, Chile, Colombia, Peru, and most Caribbean nations.
• Europe: All EU countries, United Kingdom, Norway, Switzerland, Iceland, and most Eastern European nations.
• Asia-Pacific: Australia, New Zealand, Japan, South Korea, Singapore, India, Indonesia, Thailand, Taiwan, and many others.
• Middle East & Africa: UAE, Saudi Arabia, Israel, South Africa, Egypt, Kenya, Nigeria, and numerous other countries.

Listed as not supported in the earlier version: China, Russia, Iran, North Korea, Syria, Cuba, Crimea, Moldova, and Ukraine. Users in these regions consistently reported the "account not eligible" error regardless of account type.

The earlier version pointed readers to Google's official Antigravity availability page for the complete list of 200+ supported countries and territories, and said the list had not changed significantly since late 2025.

The Solution: Change Your Google Account Region

Earlier versions said the fix was straightforward but required patience: change your Google account's associated region to a supported country.

Step 1: Request Region Change

1. Visit Google's official region change form: Google Country Association Form.
2. Check your current region first: if it is already in a supported region, you might have a different issue (see "Personal vs. Workspace" above).
3. Select your target region: choose the country you actually live in, and only if it is on the supported list.
4. Provide an accurate reason: state where you really reside. Earlier versions of this page suggested leaving out network details; the correct approach is simply to give truthful information, because the form is for correcting an account's real country.
5. Submit the request: Google reviews it manually.

Step 2: Wait for Confirmation

Earlier versions said the review typically takes 30 minutes to 24 hours, with an email notification once approved. This is community-reported (March 2026); Google does not publish a processing time.

Step 3: Configure Your VPN (Optional but Recommended)

If you use a VPN for other legitimate reasons, a VPN, proxy or header-altering extension can also interfere with the verification step. Google staff replies recommend turning it off while you verify and sign in (see "Further action is required" above).

Step 4: Sign In to Antigravity

Once your account country is correct and any confirmation email has arrived:

1. Go to the Antigravity Download Page.
2. Download and install the version for your OS (Windows, Mac, or Linux).
3. Sign in with your updated Google account.
4. Follow the setup wizard to configure your preferences.

Age Requirements & Restrictions

Google restricts most generative AI features, including Antigravity, to users who are 18 years of age or older.

• If your Google Account date of birth indicates you are under 18, the eligibility check will fail automatically.
• Accounts managed via Family Link are also generally ineligible for Antigravity access (community-reported; not stated in the FAQ).

Advanced Fix: Clear Corrupted Auth Tokens

Earlier versions said Antigravity can store a "restricted" token locally that keeps blocking access even after you fix your account region, and that manually clearing these tokens can force a fresh login.

macOS:

Windows:

After running these commands, restart Antigravity and try signing in again.

What to Do If It Still Doesn't Work

If you're still seeing the error after changing your region:

• Wait 24-48 hours: sometimes the region change takes time to propagate across Google's globally distributed systems.
• Clear browser cache: old session data might be causing issues. Clear cookies for google.com and antigravity.google.
• Try an Incognito window: prevents interference from other extensions or cached data.
• Check the sign-in flow: if you're stuck on the login screen itself rather than an eligibility message, see our Antigravity Unable to Sign In guide for step-by-step fixes.
• Review all troubleshooting steps: our Main Troubleshooting Guide covers agent errors, quota limits, and other common issues.
• Contact Google Support: if the problem persists after 48 hours, reach out to Google's support team directly.

Sources (checked October 30, 2026)

• Antigravity FAQ: personal accounts, enterprise sign-in, age, geographic availability, third-party software, headless mode.
• Antigravity Additional Terms of Service, section 6.
• Antigravity changelog (App v2.26.0, October 22, 2026, was the latest entry when checked).
• Google post on bans and reinstatement.
• Google AI Developers Forum staff replies (links inline above) and antigravity-cli issue #785.
• Google Account Help: age verification.