HTTP 429 "Resource Exhausted" in local Antigravity (Windows) despite full quota - SSH to same account works

Google Antigravity
1

Hi everyone,

I’m running into a baffling 429 Resource Exhausted error while using the Google AI Antigravity app on my local Windows machine.

The Error:
Whenever I try to use Antigravity locally, I get hit with this immediately:

{
“error”: {
“code”: 429,
“message”: “Resource has been exhausted (e.g. check quota).”,
“status”: "RESOURCEEXHAUSTED"
}
}

TraceID: 0xcd9f969581eb7…*
Date: Tue, 05 May 2026 04:19:13 GMT

Why this is strange (Troubleshooting so far):

  1. My quota is full: I checked my model quota dashboard and my limits (Gemini 3.1 Pro / Flash) are completely untouched.

  2. Remote SSH works perfectly: If I use Antigravity to SSH into a remote Linux machine using the exact same account, the exact same app, at the exact same time, it works flawlessly. This proves my account is not rate-limited.

  3. It is not a simple IP ban: My first thought was that my local public IP got temporarily banned/rate-limited. However, I completely switched to a different Wi-Fi network and my local Windows machine still gets the 429 error.

Environment:

  • OS: Windows (Failing locally) / Linux (Working via SSH)

  • Plan: Google Ultra

  • App: Antigravity

Could this be a machine-level hardware/fingerprint block, a Windows networking/SSL inspection issue masquerading as a 429, or a corrupted local cache?

Are any engineers able to look up the TraceID above to see exactly why the endpoint is rejecting this specific machine while allowing the SSH traffic?

Thanks in advance for any insights!

2

Hi Trung; I’d like to corroborate that I’m experiencing the same issue. I was using the system just fine on Mac OS yesterday, and have been entirely locked out of any usage today, with the same RESOURCE_EXHAUSTED errors. Clearing the cache didn’t resolve the error, but after about 10 minutes of reattempting to solicit a response, I was able to receive feedback. The only notable change I made was switching to Claude Opus (which gave the same error), and switching back.

I hope this helps! Good luck!