Persistent HTTP 429 RESOURCE_EXHAUSTED on Agent and /usage across multiple PCs, accounts and networks

Google Antigravity
1

Hello,

I am experiencing a persistent HTTP 429 RESOURCE_EXHAUSTED error in Google Antigravity.

The issue occurs even with a completely new conversation and a simple prompt such as “hello”.

The /usage command also fails with the same HTTP 429 RESOURCE_EXHAUSTED error.

I have tested the following:

  • Multiple Windows PCs: same issue
  • Multiple Google accounts, including a newly created account: same issue
  • Simple “hello” prompt: same issue
  • /usage and /quota: same HTTP 429 error
  • Same PC, same Antigravity installation and same Google account through USB tethering with a completely different public IP: same issue
  • Proxy environment variables are not configured
  • WinHTTP is configured for direct access
  • DNS resolution for cloudcode-pa.googleapis.com and daily-cloudcode-pa.googleapis.com works normally
  • HTTPS connectivity to the endpoints is successful

The latest /usage error is:

Trajectory ID:
40378bec-3a46-4748-b401-8e0dc******

TraceID:
0x3fd399b5e1******

X-Cloudaicompanion-Trace-Id:
3fd399b5e1*****

Timestamp:
Tue, 08 Sep 2026 01:26:14 GMT

HTTP 429 Too Many Requests

Status:
RESOURCE_EXHAUSTED

Message:
Resource has been exhausted (e.g. check quota).

Could someone from the Antigravity team please check this Trajectory ID / Trace ID on the backend?

Since the issue persists across multiple PCs, Google accounts and even a completely different network/public IP, I would like to know whether this is an account entitlement/quota issue, backend capacity issue, quota enforcement issue, or Cloud Code/Antigravity routing issue.

Thank you.

2

Hi @bonobono,

Welcome to the Forum,

Thank you for reporting. Could you please confirm if you are still experiencing this issue?

To help us diagnose this further, a couple of quick things to check:

  • Which version of Antigravity do you currently have installed? (If it’s an older version, updating to the latest release might be worth a quick check)

  • Could you provide your full, unmasked Trajectory ID?

3

how to solve this issue i am facing the same