Home / Blog / Pricing

Pricing

Antigravity Error 400: "User location is not supported", INVALID_ARGUMENT and Bad Request

Antigravity shows error 400, "User location is not supported" or INVALID_ARGUMENT? Which 400 you have, what Google's docs say, and the legit fixes.

By Engineer Foodie Desk ✓ Sources checked Nov 5, 2026

8 min read

Error strings quoted from five issues on Google’s official antigravity-cli GitHub repo: #1155, #1178, #919, #1125 and #1110 (all verified Nov 5, 2026). Location and Terms of Service wording checked Nov 5, 2026 in Antigravity’s FAQ. Error class meanings checked Nov 5, 2026 on Google’s Gemini API errors page. Every source is listed at the bottom. No affiliate links on this page (how we work).

Lead finding: “Antigravity error 400” is at least four different problems sharing one status code. The most common one in Google’s repo right now is a location rejection that hits Gemini models while Claude and GPT-OSS keep working on the same account. As of Nov 5, 2026, Google hasn’t posted a fix for it. Its only reply so far is “check your account country”. The fix depends on which 400 you have, so read the message after the code.

The exact errors: FAILED_PRECONDITION (code 400): User location is not supported for the API use.

Here are the 400s as they appear in the official repo (all verified Nov 5, 2026):

FAILED_PRECONDITION (code 400): User location is not supported for the API use.

That’s from the comments on #1155, titled “Gemini models rejected with false “User location is not supported” (400) while Claude/GPT-OSS return 200 on the same account”. The desktop app shows the same thing in a longer form, quoted in #1178:

HTTP 400 Bad Request
Status: FAILED_PRECONDITION
Message: "User location is not supported for the API use."

The other three:

  • HTTP 400 Bad Request / INVALID_ARGUMENT on long sessions, “even on basic text inputs” (#919).
  • “The server cannot process the request because it is malformed.” That’s a browser HTTP 400 when you click the account verification link (#1125).
  • SelfAssignLicense failed (HTTP 400): {"error":{"code":400,"message":"Precondition check failed.","status":"FAILED_PRECONDITION"}} for Gemini Enterprise licenses (#1110).

One-line answer: a 400 means Google rejected the request itself, not that you ran out of quota. Google’s API errors page defines failed_precondition (400) as “a prerequisite is not met (for example, disabled billing)” and invalid_request (400) as a malformed payload (verified Nov 5, 2026). Whichever prerequisite failed decides the fix.

Which 400 do you have?

MessageLikely causeFix
User locationAccount regionCheck ToS country
INVALID_ARGUMENTLong sessionNew conversation
Malformed linkVerify linkVerify in-app
PreconditionEnterprise licenseAdmin + issue

User location is not supported (FAILED_PRECONDITION). Google’s FAQ says “Your account must be associated with a country or territory where Antigravity is available,” and lists them by region (verified Nov 5, 2026). More on this one below, because it’s the messy one.

INVALID_ARGUMENT on long sessions. The #919 reporter (Antigravity 2.11.0) describes long agent runs piling up tool schemas and command output until the app keeps resubmitting a bloated conversation and gets 400 INVALID_ARGUMENT “loops”. The workaround in the issue: “discard their broken chat histories and orchestrate a manual context handoff to a fresh chat window.” In plain English, start a new conversation and paste in a short summary of where you were. In the CLI, /clear (alias /new) will “Clear the terminal and reset active conversation contexts” (CLI reference, verified Nov 2, 2026). #919 is a feature request for a /compact command, still open with no reply on Nov 5, 2026. So there’s no built-in compaction to lean on yet. Rewriting your context by hand in 2026 is a weird way to spend an afternoon.

Verification link returns HTTP 400. In #1125 (CLI 1.2.12, Google AI Pro), the CLI said “Eligibility check failed. Verify your account to continue.” and the link it printed opened a Google 400 page. It’s open with no replies. That’s really a verification problem, and Antigravity verification required walks through the documented checks (age, country, account type, in-app verification).

Enterprise license FAILED_PRECONDITION. In #1110, a Gemini Enterprise license assigned to a Workforce Identity Federation user is never detected. The CLI’s SelfAssignLicense call then fails with 400 for global, us and eu. The reporter saw a 403 SERVICE_DISABLED first, until they enabled businessaicode.googleapis.com, which they say the enterprise setup guide doesn’t mention. Other teams have added the same symptoms, and there’s no Google reply as of Nov 5, 2026. If this is you, it’s an admin and Google Cloud support ticket, not a laptop fix. Add your details to #1110.

“User location is not supported” in a supported country

This is the one that makes people want to throw their laptop. Look at who’s reporting it:

  • #1178: account region Uzbekistan, on Antigravity 2.19.1 for Windows. Uzbekistan is on the FAQ’s supported list (verified Nov 5, 2026).
  • #1155: a Google AI Pro subscriber whose Gemini requests fail while Claude Opus 4.6, Claude Sonnet 4.6 and GPT-OSS work on the same account. The reporter says Gemini worked from May 20 to Sep 30, 2026 and has been refused since Oct 3, 2026.
  • #1155 comments: other users report the same 400 with their Google Terms of Service country set to the United States and a US network (Oct 4, Oct 13 and Oct 26, 2026), and with Malaysia (Oct 17, 2026), which is also on the supported list.

It’s Viktor Navorski in The Terminal: the paperwork says your country exists, the gate says it doesn’t, and you live at the airport now.

What Google has said: a collaborator replied on #1155 (Oct 5, 2026) pointing to the supported locations list. They advised you to “verify the country listed on the Google Terms of Service page” and, if it’s wrong, submit a request to update your region. On #1178, a collaborator said the repo “is exclusively for the Antigravity CLI” and sent desktop app issues to the Antigravity Community Forum (Oct 6, 2026). Both issues were still open with the “awaiting response” label on Nov 5, 2026.

So, in order:

  1. Check your Google account’s country. Open policies.google.com/terms while signed in to the same account. If it’s wrong, file the country-association form. This is Google’s documented advice.
  2. Try a plain connection. One #1155 commenter’s theory is that the app’s model requests can leave your machine by a different network route than the browser does. That’s a user theory, not Google’s. The safe test is one try on a normal home or office connection with no proxy and no VPN.
  3. Use a model that works while you wait. In #1155, Claude and GPT-OSS models kept returning 200 on the same account. Antigravity removed Claude Sonnet 4.6, Claude Opus 4.6 and GPT-OSS-120b on Nov 2, 2026 (models docs, verified Nov 3, 2026). So check what your plan lists now before assuming the workaround still holds.
  4. Report it in the right place. CLI: add your version, OS, plan and ToS country to #1155. Desktop app: the community forum, per Google’s reply on #1178.

What not to do: don’t use a VPN to look like you’re somewhere else, and don’t route Antigravity through third-party tools to dodge the check. Google’s FAQ says using third-party software to access Antigravity “is a violation of our Terms of Service” and “can result in suspension or termination of your account” (verified Nov 5, 2026). As Dwight Schrute put it, “Identity theft is not a joke, Jim.” Pretending to be in another country is the light version, and it puts the account at risk.

I’ll be honest, this one is frustrating. People paying for Google AI Pro are getting a location error on Google’s own models, in countries Google lists as supported. A month of “awaiting response” isn’t good enough.

400 vs 403 vs 429 in Antigravity

CodeUsually meansRead next
400Request rejectedThis page
403Not verifiedVerification post
429Quota used upQuota post

There’s no Antigravity status page listed in Google’s docs index (checked Nov 2, 2026).

Is a 400 a usage limit?

No. Limits show up as quota errors, not 400s. The #1155 reporter even checked and found their Gemini quota almost untouched while the 400s kept coming. Upgrading won’t clear a location or license 400 either. The #1155 and #1178 reporters already pay for Google AI Pro. If you’re wondering what the free plan actually includes, see Is Antigravity free?. If you’re done waiting on Google, Antigravity vs Cursor and AI coding tools compared are where I’d look next.

Here’s what I’d do

Read the text after “400”. Location: check your ToS country, try once on a plain connection, use a working model, then add your details to #1155 (CLI) or the forum (desktop). INVALID_ARGUMENT on a long session: start a new conversation with a short handoff note. Verification link 400: follow the verification post’s steps. Enterprise license: get your admin to open a Google Cloud ticket and add to #1110. Skip VPNs and wrappers. They risk the account, and nothing Google publishes says they fix it.

FAQ

What does Antigravity error 400 User location is not supported for the API use. mean? Google’s server decided your account isn’t in a supported location, so check the country on your Google Terms of Service page and request a change if it’s wrong.

Does a VPN fix Antigravity error 400? No; Google’s FAQ ties access to your account’s country and says third-party access tools can get the account suspended, so fix the account country instead.

Is Antigravity error 400 a usage limit? No; usage limits are quota errors, while a 400 means Google rejected the request itself.

How do I fix Antigravity 400 INVALID_ARGUMENT on a long chat? Start a new conversation with a short summary of your work, as described in issue #919, since Antigravity has no compact command as of Nov 5, 2026.

Has Google fixed the Antigravity location 400? Not as of Nov 5, 2026; issues #1155 and #1178 are open, and Google’s only advice is to check your account country.

Sources

  1. antigravity-cli issue #1155 (Gemini “User location is not supported” 400 while Claude/GPT-OSS work; collaborator reply Oct 5, 2026; open): https://github.com/google-antigravity/antigravity-cli/issues/1155 (verified 2026-11-05)
  2. antigravity-cli issue #1178 (“HTTP 400 Bad Request”, FAILED_PRECONDITION, desktop 2.19.1; redirected to forum Oct 6, 2026; open): https://github.com/google-antigravity/antigravity-cli/issues/1178 (verified 2026-11-05)
  3. antigravity-cli issue #919 (INVALID_ARGUMENT 400 loops on long sessions; feature request for /compact; open): https://github.com/google-antigravity/antigravity-cli/issues/919 (verified 2026-11-05)
  4. antigravity-cli issue #1125 (verification link returns HTTP 400; open): https://github.com/google-antigravity/antigravity-cli/issues/1125 (verified 2026-11-05)
  5. antigravity-cli issue #1110 (Gemini Enterprise SelfAssignLicense 400 FAILED_PRECONDITION; open): https://github.com/google-antigravity/antigravity-cli/issues/1110 (verified 2026-11-05)
  6. Google Antigravity FAQ (location rule, supported countries, third-party software and Terms of Service): https://antigravity.google/docs/faq (verified 2026-11-05)
  7. Gemini API, API errors (400 failed_precondition and invalid_request definitions): https://ai.google.dev/gemini-api/docs/api-errors (verified 2026-11-05)
  8. Antigravity CLI reference (/clear alias /new): https://antigravity.google/docs/cli/reference (verified 2026-11-02)
  9. Antigravity models (Nov 2, 2026 removals): https://antigravity.google/docs/models (verified 2026-11-03)
  10. 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 and #1155, verified 2026-11-05)
  11. Antigravity Community Forum (desktop app issues, per Google’s reply on #1178): https://discuss.ai.google.dev/c/antigravity/64 (link from Google’s reply on #1178, verified 2026-11-05)
  12. Antigravity docs index (no status page listed): https://antigravity.google/llms.txt (verified 2026-11-02)

Related reading