Antigravity CLI 1.4.2 — 403 location eligibility error for two Google accounts, including Google AI Pro

Google Antigravity
1

Description:

Hello,

I am experiencing a persistent location eligibility error when using Antigravity CLI on my VPS.

Environment

  • OS: Ubuntu 22.04.5 LTS

  • Antigravity CLI: 1.4.2 (agy update reports that this is the latest version)

  • Node.js: 22.23.2

  • Network: IPv4 and IPv6 are both functional

Observed behavior

The following error occurs when running a prompt:

Your current account is not eligible for Gemini Code Assist for individuals because it is not currently available in your location.

Error code: 403 PERMISSION_DENIED

The error occurs with both Gemini and Claude models, including claude-sonnet-4-6.

I tested two separate personal Google accounts:

  1. An account with an active Google AI Pro subscription. Its Google Terms of Service country is Belarus.

  2. A second account without a paid subscription. Its Google Terms of Service country is Netherlands.

Both accounts can authenticate successfully, and agy models lists the available models, but actual prompt execution fails with the same eligibility error.

The second account displays Antigravity Starter Quota in the CLI, yet prompts are still rejected.

Diagnostics completed

  • Updated/checked the CLI; it reports that version 1.4.2 is current.

  • Signed out and authenticated again.

  • Confirmed that IPv4 and IPv6 connectivity to Google, Gemini API, OAuth, and the Cloud Code hostname work.

  • Confirmed that Node.js resolves both IPv4 and IPv6 addresses.

  • Checked that no custom Google Cloud authentication environment variables are configured.

Could you please advise whether this is an account eligibility, account-region association, or backend entitlement issue? In particular, could the team verify why the same error occurs for two accounts with different Terms of Service countries?

I can provide error IDs and additional diagnostics privately if needed. I will not share OAuth tokens or authentication files publicly.

Thank you.

2

Hi @Paul_Durov,

This 403 PERMISSION_DENIED error happens because Antigravity checks both your Google Account’s associated country and the real-time network egress IP (IPv4/IPv6) of the machine sending the prompt against our approved countries list. That is why authentication and agy models succeed, while actual prompt execution is rejected on both accounts when running from your VPS.

To fix this:

  • For the account with Belarus Terms of Service: Belarus is not currently on the supported countries list, so prompts from that account are blocked regardless of subscription tier or IP. If you now reside in a supported country, check your region on the Google Terms of Service page and request an update via the Country Association Form.
  • For the Netherlands account on your VPS: While the Netherlands is supported, your VPS’s public IPv4 or IPv6 address is likely geolocating to an unsupported region or flagged proxy/datacenter subnet. Run curl -4 https://ipinfo.io and curl -6 https://ipinfo.io on the VPS to check where both addresses geolocate (many VPS providers register IPv6 blocks in a different country than IPv4), make sure your VPS egresses from an approved country, or run agy directly on your local machine in the Netherlands.
  • Verify age & refresh login: Ensure age verification is completed on the account, and once both your account country and network IP are in supported regions, run /logout followed by /login in agy.