Your Current Account Is Not Eligible for Antigravity: Every Cause and Fix

You clicked sign in, the browser handed the login back, and Antigravity returned a sentence about you rather than about your code: your current account is not eligible for Antigravity. Nothing on screen says which check failed, and no email arrives. The account works everywhere else in Google.

Five of the six messages in circulation mean Google’s system said no to the account. Only one is about something you did, and that one says so in its own text. All six get searched as one error and answered as one error, and the fixes do not transfer. Getting the region right does nothing for an account that failed age verification, and neither one touches a suspension.

Antigravity refuses an account for four documented reasons: the account’s region, an unverified age, a Workspace or school account, and a location Google cannot determine, plus a Terms of Service block that only looks like an eligibility error. For the location case Google names the message and nothing more; the network advice attached to it below comes from a forum user, neither staff nor moderator, with no confirmed success. Which fix works depends on which message you saw.

Which Antigravity error did you actually get?

The exact words on the screen decide everything that follows. The six strings below split into three groups that share nothing: a region and account-type group, an age group, and a suspension that is not an eligibility check at all.

None of this comes from an Antigravity account of mine. I read Google’s Antigravity FAQ, seven threads on Google’s own developer forum and one GitHub issue on 17 August 2026, and I ran a count of that forum the same day. Where a fix below is reported to have worked, the page says who reported it and what the next person in the thread said. Nothing here was tested from inside the product.

“Sorry, this account is ineligible to use Antigravity” is the same block in different words. The longest-running thread on it opened on 29 December 2025, ran to 20 posts and still has no accepted answer as of 17 August 2026. If that is your message, work region, then age, then account type in that order.

”Not currently available in your location”: is your country on Google’s list?

Google lists Antigravity as available in five regional blocks whose headings add up to 224 countries and territories, and separately lists 31 regions with no Google One AI plan. All 31 sit on the availability list, so in those places Antigravity works and there is no paid tier to buy.

Google publishes the availability list on the Antigravity FAQ, split into Americas, Europe, Africa, Asia, and Oceania and Antarctica. Read on 17 August 2026, the five headings claim 51, 47, 56, 43 and 27, which totals 224. The lists under them hold 222 entries: the Asia heading says 43 over a 42-item list, the Oceania and Antarctica heading 27 over a 26-item list. Check your own country against the list, not against the headline number.

Further down the same page, under “Why am I ineligible for a Google One AI plan?”, Google names 31 regions with no access to Google One AI plans. I compared the two lists on 17 August 2026, and all 31 appear on the availability list. Twenty-six matched exactly; the other five matched across a naming difference, the availability list writing Falkland Islands, Heard Island, Saint Helena, South Georgia and U.S. Outlying Islands for the plan list’s longer names.

Read on antigravity.google/docs/faq, 17 August 2026.

That has a practical consequence in those 31 places. Antigravity is supposed to work there on the free tier, and the usual advice for an eligibility error, buy a plan, is not available to buy. Anyone in Türkiye, Kosovo, Greenland, Sudan, Brunei or the Faroe Islands told to upgrade their way out of this is being told to do something Google’s own page rules out.

Google’s instruction for the region case sits in a note above the availability list: check the country on the Google Terms of Service page, and if it is wrong, submit a request to change your associated region. Both links are Google’s own. One person reported that working, on 25 May 2026 in the gemini-cli issue thread, after choosing a country where Antigravity was allowed.

The two pages currently ranking as dedicated fixes, apipod.ai/blog/how-to-fix-antigravity-location-error and apidog.com/blog/fix-antigravity-not-eligible-error/, both read on 17 August 2026, name region as the only cause. Both pages tell readers to route through a VPN into a supported region and to leave the VPN unmentioned when filing Google’s form. I am not repeating that as advice, and the FAQ elsewhere treats unusual access paths as a suspension risk.

”Why is my age unverified?”: the Antigravity age gate

Antigravity is closed to under-18 users, and Google’s FAQ points anyone above that age at Google’s own age-verification page. On Google’s developer forum this is the only cause in the eligibility family with a resolution the person who asked came back and confirmed.

Google’s wording, read 17 August 2026, is short: “At the moment, Antigravity is unavailable to under-18 users.” The sentence that follows offers the route, and Google’s own link on the words “verify your age” goes to myaccount.google.com/age-verification.

On 19 April 2026 a forum user posting as tozores opened a thread titled “Account not eligible, possible ban”, reporting the error on a Pro account and assuming they had been banned. The next day they answered themselves:

“Solved, the problem is the age verification mechanismo”

The typo is theirs. That reply is marked as the accepted answer on the thread, and it is one of only three accepted answers across every eligibility thread I counted.

One caution before you go hunting for an age-related error string. Plenty of people search the words “you must be 18 years old”, yet on 17 August 2026 nothing Google publishes carried them: not the FAQ, and not any product string quoted on the forum. What the record holds instead are user-reported wordings: on 24 February 2026 a Google One AI Pro family member described two accounts showing “Your current account is not eligible for Antigravity. Verify your account to continue.”, and a 9 February 2026 thread reports “Further action is required to use Antigravity. Please verify your account, then sign in again to continue”. Neither string is in the FAQ.

”Because we cannot determine your account’s location”: work and school accounts

Google’s documented answer for a Workspace or school account is to try an @gmail.com address instead. The separate message about a location Google cannot determine hits the same accounts, and the advice on record for it is about VPNs, proxies and corporate firewalls rather than about the account itself.

The FAQ question is “Why can I not authenticate into Google Antigravity?”, and the whole answer, read 17 August 2026, is two sentences: “Google Antigravity is currently available for personal Google accounts in approved geographies. Please try using an @gmail.com email address if having challenges with Workspace Google accounts.”

That is a real answer and a limit at once. It does not say when Workspace support arrives, or whether an administrator can change anything.

The related message reads “Your current account is not eligible for Antigravity, because we cannot determine your account’s location.” A thread opened on 21 January 2026 shows the pattern: the person who opened it had a company account and had already submitted the country form several times, and two of the four who followed said the same about their Workspace accounts. On 10 February 2026 the thread’s only substantive answer came from a replier carrying the user title Google on their profile, an account the forum’s own record marks as neither staff nor moderator:

“If you are using a VPN, proxy, or corporate firewall, it may be masking your true IP address and preventing location verification. Please try connecting directly via your ISP.”

The same reply adds that an administrator may need to enable specific services, and that a browser blocking location services for the Antigravity domain can cause it. Nobody in the thread reported any of it working, and it has no accepted answer as of 17 August 2026.

”PERMISSION_DENIED (code 403)”: when the block is a suspension

A Terms of Service block is a suspension, and it prints a different message: PERMISSION_DENIED (code 403), with the words violation of Terms of Service in it. Signing in again will never clear it. The route is an appeal, and the one behavior Google’s FAQ warns may cost you the account is using third-party clients on the Antigravity login.

On 24 June 2026 a user posting as Josh_Hoffman opened the antigravity CLI and got this:

“Eligibility check failed: PERMISSION_DENIED (code 403): This service has been disabled in this account for violation of Terms of Service. Please submit an appeal to continue using this product”

Read the words. The account has been disabled and the instruction is to appeal. Switching Google accounts, clearing caches or changing your Terms of Service country addresses none of that.

Google’s FAQ names one behavior directly, under the question about third-party software, read 17 August 2026: “Using third party software, tools, or services to access Antigravity is a violation of our Terms of Service, and severely degrades the experience for legitimate product users. Such actions may be grounds for suspension or termination of your account…” The examples in Google’s own question heading are Claude Code, OpenClaw and OpenCode. Google’s suggested alternative there is a Vertex or AI Studio API key.

The thread also shows what the appeal is like in practice. Josh_Hoffman reported no email and no appeal link inside the CLI or IDE, contrary to what support had told them to expect. Another user posted a link to an appeal form covering Terms of Service suspensions for Antigravity, Gemini CLI and Gemini Code Assist. That link is a forum post rather than a Google-published URL, so it is described here and not reproduced: find the current appeal route from Google’s own support pages before typing account details into a form you found on a forum. On 25 June 2026 Josh_Hoffman reported that access had returned and credited that form. Two others in the thread said they had never connected a third-party tool.

When Antigravity cannot see the plan you paid for

A paid Google AI plan that Antigravity does not recognize is a third kind of problem: sign-in works, the plan does not attach, and the app runs on free-tier limits. Paying more does not fix an eligibility block, and an eligibility fix does not attach a plan.

This is the case most likely to be mistaken for the sign-in error. Of the 64 eligibility threads I counted on Google’s forum, 13 name Google AI Pro or AI Ultra in the title, counting only the titles that use one of those plan names. All 13 are Pro: individual subscribers, a family-group member, two Google One bundles and one subscription managed by a mobile carrier. A thread opened on 30 July 2026 says it in its own title, mail-header prefix and all: “Subject: Google AI Pro subscription not recognized in Antigravity (Account incorrectly marked as ineligible)”.

The tell that separates the two is whether you got in. If Antigravity opened, you have a plan-recognition problem, and the fix path runs through Google’s subscription and billing side. If Antigravity refused the login, the plan is beside the point, and buying a bigger one changes nothing.

What Google’s own forum shows about how often this gets fixed

On 17 August 2026 I searched Google’s developer forum at discuss.ai.google.dev through its public search API for antigravity ineligible, antigravity "not eligible" and antigravity eligibility, paging each query to exhaustion, which returned 155 distinct topics. Keeping only topics whose title matches ineligib, not eligible, eligibility or NOT_ELIGIBLE left 72, and removing the 8 whose titles are about rate limits or quota, which are a different error, left 64 sign-in eligibility threads opened between 10 December 2025 and 11 August 2026.

Three of those 64 threads carry an accepted answer.

The monthly split is 5 threads in December 2025, 8 in January, 5 in February, 3 in March, 5 in April, 7 in May, 17 in June, 11 in July, and 3 in the first eleven days of August 2026. A forum count measures complaints, not incidents, so June’s 17 says people posted more that month and nothing about how many accounts were hit. What it does establish is that this never tailed off. Of the 64, 12 name a location, region or country word in the title, one fewer than the 13 naming a paid plan.

Three limits on that number. It counts threads on one forum, not users and not incidents. The forum’s search is not guaranteed exhaustive, so 64 is a floor. And title matching misses any thread whose author described the problem without using one of those words.

The fix that ranks highest deserves the same treatment. GitHub issue google-gemini/gemini-cli#15986 carries the error string as its title. Read through GitHub’s public API on 17 August 2026, it was opened at 10:26:54Z on 6 January 2026 and closed at 10:31:23Z the same morning, four and a half minutes later, with a state reason of completed. It has 8 comments, and every one carries an author association of NONE, so not one came from a maintainer or anyone with write access to that repository.

The most-copied fix there tells you to open your Google account’s security settings, find Antigravity under third-party access, remove access and sign in again. A commenter with no association to the repository posted it on 10 February 2026. The next person to reply, on 21 February 2026, said:

“that’s absolutely do nothing. error still appears every time i’ve try to login in antigravity.”

The spelling is theirs. They added that other Google AI Pro features still worked, and Antigravity was what they had paid for.

In the search pull I ran on 16 August 2026, rank 1 for this error was a Reddit thread in r/google_antigravity whose title begins “Fixed my antigravity”, and whose snippet gives that same unlink-third-party-access sequence. Everything in that sentence comes from the search result, because the thread itself stayed shut to me: a fetch on 17 August 2026 returned the site’s empty shell and none of the posts. So the thread is unread here and nothing is quoted from it. The fix it advertises is the one a non-maintainer posted to a closed GitHub issue.

What to do once you are in

Start from the exact message. If it names your location, check the country on your Terms of Service page. A message asking you to verify points at age verification on your Google account. If it names Terms of Service and a 403, stop retrying and file an appeal. If you are on a work account, Google’s own answer is a gmail.com address.

Once the sign-in works, the next surprise is usually the quota, and what Google Antigravity costs on each plan is a separate answer with its own tiers, its own refresh rules and its own reasons a paid plan can feel smaller than expected.

Working access settles the sign-in and nothing else. Antigravity runs as an agent, so the questions waiting on the other side of the login are about permission and exposure: whether your employer or your client allows this tool on that machine at all, and where the repository ends up once you point it there. Those belong to the safety review of Antigravity, and a fixed login answers none of them.

Common questions about the Antigravity eligibility error

Why does Antigravity say my account is not eligible?

Because one of several checks failed, and the message does not say which. Google documents four: the account’s region, its age verification state, the account type where Workspace and school accounts are unsupported, and a location Google cannot determine, though for that last one the network fixes on record are user-reported and unconfirmed. A fifth message, PERMISSION_DENIED with a Terms of Service line, is a suspension. Read the exact words on screen before trying any fix.

Why is Antigravity sign in with Google not working?

The sign-in itself usually works. What fails is the eligibility check that runs after Google hands the login back, which is why the browser step completes and the app still refuses you. Match your message to one of the strings above and treat it as its own problem. In the threads read for this page, clearing caches and re-signing in was suggested and did not resolve the case it was suggested for; the fixes that were reported to work were a region correction and, after a suspension, a successful appeal.

How do I fix “your current account is not eligible for Antigravity, because it is not currently available in your location”?

Check the country listed on your Google Terms of Service page. Google’s FAQ note says to do that first, and if the country is wrong, to submit a request through Google’s country-association form. If the country is right, the next variable is the network you sign in from, since a VPN, proxy or corporate firewall can put your traffic somewhere your account is not.

Does paying for Google AI Pro fix the Antigravity eligibility error?

No. An eligibility block happens before any plan is consulted, which is why 13 of the 64 forum threads counted here carry a title that names a paid Google AI plan. Paying changes your quota. It changes nothing about your region, your account type or your age verification state.

What does “Please verify your account to continue using Antigravity” mean?

It is Google’s age and identity check under a different wording. Google’s FAQ states that Antigravity is unavailable to under-18 users and links to its own age-verification page for anyone who meets the requirement. Users have reported two wordings on Google’s forum, one asking you to verify your account to continue, one saying further action is required before signing in again.

Can I use Antigravity with a work or school Google account?

Not as of 17 August 2026. Google’s FAQ says Antigravity is currently available for personal Google accounts in approved geographies, and its documented advice is to try an @gmail.com address if a Workspace account is giving trouble. Google publishes no timeline for Workspace support and no administrator setting that changes it.

What is “There was an unexpected issue setting up your account”?

The public record on this one is thin. As of 17 August 2026, Google’s Antigravity FAQ does not name the string at all. Two forum threads report it, one from 24 February 2026 describing a login that fails on one Google account while others work on the same machine, and one where it appears alongside the verify-your-account message. Nobody has published a cause, so treat any confident explanation with suspicion.

Why does Antigravity say I am ineligible for higher rate limits when I have a paid plan?

Because that message means the opposite of the sign-in error. It means Antigravity let you in and is running you on the free quota because your subscription has not attached. The sign-in error means Antigravity never let you in at all. If you are inside the app and working, treat it as plan recognition on Google’s billing side and leave eligibility alone.

Is the Gemini Code Assist eligibility error the same thing?

They share a check. Google’s forum carries PERMISSION_DENIED (code 403) reports naming Gemini Code Assist rather than Antigravity, and the appeal form a user posted in the Terms of Service thread covers Antigravity, Gemini CLI and Gemini Code Assist together. This page does not attempt the Gemini Code Assist version, which has its own account rules.

Has Google said when this will be fixed?

Not that I could find as of 17 August 2026. Across the 64 eligibility threads counted on Google’s own forum, 3 carry an accepted answer, and the replies from accounts carrying a Google forum title restate the error’s own advice rather than name a cause or a date. Google’s FAQ documents the rules and never addresses the accounts that meet every published rule and still fail the check.