Location eligibility gate gives different verdicts to two consumer accounts at the same location

[oMempty]

Filed as antigravity-cli issue: [Bug]: All models gated behind a retired "Gemini Code Assist for individuals" eligibility check - verdict differs between two accounts at the same location · Issue #1016 · google-antigravity/antigravity-cli · GitHub

Short version, all measured on one machine with one IPv4 egress, two consumer Google accounts, minutes apart:

	Account A	Account B
Eligibility check	passes	blocked - “not eligible for Gemini Code Assist for individuals because it is not currently available in your location”
Gemini, default backend	400 FAILED_PRECONDITION - “User location is not supported for the API use”	eligibility error
Claude (claude-sonnet-4-6), default backend	200 OK	eligibility error
Gemini, production backend via CLOUD_CODE_URL	429 RESOURCE_EXHAUSTED, no location error	eligibility error

Two things look wrong:

1. A location-based gate should not give two different answers to two accounts at the same location.
2. Antigravity is enforcing the eligibility rules of Gemini Code Assist for individuals - a product retired on 2026-06-18 whose documented migration target is Antigravity itself.

agy 1.2.2, Antigravity IDE 1.107.0 (stable), Windows 11. No VPN or proxy; single residential IPv4, no IPv6 route. GOOGLE_CLOUD_PROJECT is ignored - applyAuthResult logs quotaProject= (empty) with or without it. Full logs, transcripts and error IDs are in the GitHub issue.

Same symptom reported earlier with no replies on any of them:

All Gemini models fail in Antigravity with FAILED_PRECONDITION: User location is not supported for the API use AI Studio works normally

Environment Google AI Pro account US IP (AWS Oregon) Google AI Studio works normally Same account Same IP Problem All Gemini models in Antigravity fail immediately. Claude works normally. GPT works normally. Only Gemini fails. Error HTTP 400 FAILED_PRECONDITION User location is not supported for the API use. Trajectory ID 6726ab62-7e3e-49c5-b80a-adb5bbf326.. Trace ID 0x7a66aa248e51a3.. This appears to be an Antigravity Gemini provider routing issue because AI Studio works correct…

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

Hello, I would like to report what appears to be an incorrect location classification when using Google Antigravity. I have reproduced the issue using both: Antigravity IDE (latest version) Antigravity CLI 1.1.1 Environment: Ubuntu 22.04.5 LTS Windows 11 Google AI Pro subscription Public IP: 185.112.249.237 Public IP location: Slovakia The issue is fully reproducible. Authentication succeeds successfully. The CLI is able to: authenticate my Google account; detect my Google AI Pro sub…

Antigravity CLI intermittently rejects Gemini requests with false “User location is not supported

Product: Google Antigravity CLI CLI version: 1.1.10 OS: macOS Network egress observed: Singapore, AS21859 (Zenlayer Inc) Account authentication: OAuth succeeds normally Issue: Gemini requests in Antigravity CLI intermittently fail with: FAILED_PRECONDITION (code 400): User location is not supported for the API use. The CLI UI only shows: Agent execution terminated due to error. This is not a stable account or network failure. The same authenticated CLI process, same machine, and same n…

This may be the same root cause as the recent “Entitlement Desync” / “showing as Starter Quota” reports in this category, which are also eligibility-lookup failures rather than genuine plan or location limits.

[chunduriv]

Hi @oMempty,

Welcome to the Forum,

The location eligibility check for Antigravity is evaluated based on the registered home country/region associated with your Google Account profile, rather than your current IP address alone.

If two accounts on the same machine receive different eligibility verdicts, it indicates that the accounts have different country profile settings or age verification statuses in their Google Account profiles.

To resolve this issue and enable Antigravity on both accounts:

• Check Account Country Region: Visit the Google Terms of Service page at https://policies.google.com/terms while signed into each account to view the registered country associated with the account. If the listed country is incorrect or unsupported, submit a request to update your region as detailed in the official Antigravity FAQ | Google Antigravity Docs

• Verify Age Eligibility: Antigravity requires age verification for personal Google accounts. Confirm that your account age is verified at https://myaccount.google.com/age-verification

• Refresh Local Auth & Claims Cache: Open Antigravity IDE, press Ctrl+Shift+P (or Cmd+Shift+P on macOS), and run Antigravity: Reset Onboarding

• Model Differences: Gemini models enforce regional availability checks at the API gateway level, whereas Claude models route via separate authorization paths. Once your Google Account region is verified as supported, Gemini models will function normally