- Consumer Google Account, signed in with a QQ email address (email redacted)
- Google Terms of Service shows “Country version: Japan” while signed into this same account
- Antigravity plan shown in the app: Starter Quota
Problem:
OAuth sign-in succeeds, but requests fail before producing a response. Gemini 3.8 Flash, Claude Sonnet 4.6, and GPT-OSS 120B all return the same eligibility error:
403 PERMISSION_DENIED
reason: UNSUPPORTED_LOCATION
error_number: 1008
“Your current account is not eligible for Gemini Code Assist for individuals because it is not currently available in your location.”
The language_server process has established connections to the configured local proxy. The proxy is configured for a Japan exit, though I cannot confirm how Google classifies that egress IP.
A recent request on 2026-10-27 at 16:19 Asia/Shanghai produced trace ID:
0x4cb1efa2d2a924f6
Could you check whether this is an account eligibility/provisioning issue or an egress-location classification issue, and advise on a supported recovery path? Please let me know if you need the account identifier privately.
This error is a location eligibility check and it is evaluated using the network location your requests come from, not only the country on your Google Account. Requests sent through proxies or VPNs can be classified differently from the exit country you selected, so the country shown on your Terms of Service page alone doesn’t determine the result.
If you are physically located in a supported country, please turn off the proxy or VPN and connect directly, then sign out from Settings → Account → Sign Out in the Antigravity App and sign in again.
Thanks for sharing the exact 1008 error payload and setup details, @yuchang_he. Building on @chunduriv’s point about network location vs. the Terms of Service page, when language_server on Windows 11 is connected to a local Japan proxy but still gets 403 PERMISSION_DENIED: UNSUPPORTED_LOCATION (1008) on every model, it almost always comes down to one of three split-routing or account-profile checks:
Rule-Mode Split Routing on daily-cloudcode-pa.googleapis.com and aicode.googleapis.com: Many local Windows proxy rulesets route *.google.com through the Japan node while sending *.googleapis.com (or direct UDP/QUIC HTTP/3 traffic) via DIRECT to speed up downloads. Switch your local proxy client from Rule mode to Global mode, disable UDP / QUIC on port 443 so Go’s language_server is forced over the proxied TCP tunnel, and verify the actual egress classification from PowerShell:
curl.exe -x http://127.0.0.1:<YOUR_PROXY_PORT> https://www.google.com/ihan
```IPv6 (`AAAA`) Bypass on Windows 11: If your local proxy only tunnels IPv4 or your TUN adapter has IPv6 disabled while Windows still has a native IPv6 address, `language_server` can resolve `googleapis.com` over IPv6 outside the Japan tunnel. Disabling IPv6 on the physical adapter (or enabling `ipv6: false` in your proxy DNS resolver so `AAAA` queries return empty) prevents that leak.
Google Play / Payments Country vs. `policies.google.com/terms`: Even when `policies.google.com/terms` displays *Country version: Japan*, Google's internal eligibility check also looks at the country tied to your Google Payments profile at `pay.google.com` (*Settings > Country/Region*) and the hard country association at `policies.google.com/country-association-form`. Making sure both match Japan and then running **Settings > Account > Sign Out** in Antigravity so a fresh token is issued should clear the `1008` block.