All Gemini models fail with false "User location is not supported" in Antigravity — AI Studio and Claude work normally

Google Antigravity
, ,
1

I am consistently getting the following error with all Gemini models in Antigravity:

HTTP 400 FAILED_PRECONDITION: User location is not supported for the API use.

However, Claude models in Antigravity work normally, and Gemini also works normally in Google AI Studio using the same Google account and network.

Environment

  • Windows x64

  • Antigravity 2.8.1

  • Google account Country version: United States

  • Current US exit:

    • 198.204.234.107

    • AS33387 Nocix

    • Kansas City, Missouri, US

Affected models

I tested all currently available Gemini options in Antigravity:

  • Gemini 3.1 Pro

  • Gemini 3.5 Flash

  • Gemini 3.6 Flash

  • Gemini 3.7 Flash

All return the same location-related HTTP 400.

Meanwhile:

  • Claude Sonnet 4.6 works normally

  • Claude Opus 4.6 works normally

  • Gemini works normally in Google AI Studio with the same account and network

Latest confirmed reproduction

Simple prompt:

1+1

Result after about 1 second:

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

Latest server-side identifiers:

  • UTC time: 2026-08-14 06:22:28

  • Trajectory ID: 955a098f-3e2a-4952-ab6d-2117721479..

  • Error ID: 955a098f-3e2a-4952-ab6d-2117721479c1-3

  • Cloud AI Companion Trace ID: c85350c1deacc2..

Troubleshooting already performed

I have done extensive A/B testing.

Network path

Antigravity language_server.exe is confirmed to route through Mihomo and the configured US exit.

For both failed Gemini requests and successful Claude requests:

  • destination is daily-cloudcode-pa.googleapis.com

  • traffic goes through 127.0.0.1:7890

  • the same Mihomo routing rule is used

  • the same US exit is used

I observed:

  • no Google IPv6 connection

  • no IPv6 leak

  • no DIRECT/bypass connection from Antigravity

  • normal DNS and TLS connectivity

Different US exit / ASN

I also reproduced the same issue using another completely different US exit:

  • 142.249.37.26

  • AS153371

  • Los Angeles, US

The second exit used a different IP and ASN, but Gemini still returned exactly the same location error.

Antigravity versions

I tested versions from 2.8.1 down to 2.5.0.

The same Gemini location error occurs on all tested versions.

Cloud Code endpoint

I also performed a temporary A/B test between:

  • daily-cloudcode-pa.googleapis.com

  • cloudcode-pa.googleapis.com

The production endpoint did not change the result. Gemini still returned the same location 400, while Claude continued to work.

Why this seems abnormal

The Google account Country version is United States, which is a supported Antigravity region.

The issue is specific to Gemini requests inside Antigravity:

  • same account + AI Studio Gemini → works

  • same Antigravity + Claude → works

  • Antigravity + every Gemini model → location 400

  • two different US IPs/ASNs → same result

  • Antigravity 2.5.0 through 2.8.1 → same result

This makes it look like a Cloud AI Companion / Antigravity Gemini region or eligibility check is rejecting the account/request incorrectly.

I have also submitted an in-app Bug Report with Antigravity server logs attached.

Could someone from the Antigravity team please check the latest Trace ID / Trajectory ID above and see which region or eligibility check is causing this rejection?

I have found a few other recent reports that appear to describe the same or very similar behavior, especially cases where Claude or AI Studio continue to work while Antigravity Gemini requests fail with the same User location is not supported error.

屏幕截图 2026-08-14 144543
屏幕截图 2026-08-14 1445431047×926 20.1 KB

2

I have no particular domain knowledge, here, but after reading this, the first thing that comes to mind is: Google is cracking down on VPNs. I don’t see anything in the AG’s TOS, on this subject matter, but this is what this reads like. Antigravity is not available where you are, right?

3

Hello there.
There are two options to approach this issue.

Try to use a VPN that doesn’t reveal your real IP.
Then go to guest mode in google and create a google account there.
Then with that VPN on go and login to the account you have created.

Make sure your VPN is on.
Go to “https://policies.google.com/country-association-form?authuser=1&pageId=none”
Change the country to the one your VPN is connected to.
Wait a few hours for a respond By Google in your Email.
They mostly approve if your VPN is ON the whole time till you get the email.
Now your accounts region has been changed.
You’re good to go.

I recommend the second option since it has worked for many.

Have great day
-Artin

5

Thanks for the suggestions.

My Google account Country version is already set to the United States, so the country association option unfortunately does not seem applicable in my case.

I also considered testing with a newly created Google account, but Antigravity currently requires phone verification when I try to sign in with a new account, so I’m unable to perform a clean account-level A/B test at the moment.

Still, thanks for the ideas.

6

My previous problem was the same as yours. Everything is fine on my side now, and all functions have been restored. You can try updating to the latest version.

8

Hi @qingxuruogu,

Thank you for the detailed diagnostic breakdown.

Could you please update your Antigravity installation to the latest version and let us know if the issue is still reproducible on your end?

If you continue to experience any location errors after updating, please share your updated Trajectory/Error ID so we can investigate further.

9

I have the same issue on Windows with Google Antigravity 2.12.2.

Claude works normally in Antigravity, and Gemini works in Google AI Studio with the same Google account. However, every Gemini request inside Antigravity fails with:

HTTP 400 FAILED_PRECONDITION
“User location is not supported for the API use.”

I reset the local Antigravity profile and authentication state, tested different network configurations, and confirmed that the Cloud Code endpoint is reachable. The issue remains.

My Google Terms of Service page currently shows Ukraine as the account country/region.

Error details:

Trajectory ID: 13784fe0-9e2e-4733-9e59-ce8f2917c..
Trace ID: 0x763135b042766..
Timestamp: September 7, 2026, 09:30:46 UTC

The server response was:

{
“error”: {
“code”: 400,
“message”: “User location is not supported for the API use.”,
“status”: “FAILED_PRECONDITION”
}
}

Could this be an incorrect Cloud Code/Antigravity eligibility or account provisioning issue?