Pro account hitting 429 RESOURCE_EXHAUSTED despite quota showing available, persists after full reinstall

Google Antigravity
,
1

Hey team,

I’m on a paid Antigravity Pro account and my agent suddenly stopped mid-session with a 429 error. The UI model/quota section shows quota as available — this isn’t showing as a normal “quota finished” state, but the actual request is getting rejected anyway.

Error details:

Trajectory ID: c071901c-c0a2-419c-aa*************
TraceID: 0xbea842ed2f*******
X-Cloudaicompanion-Trace-Id: bea842ed2f*******

Error: HTTP 429 Too Many Requests
{
  "error": {
    "code": 429,
    "message": "Resource has been exhausted (e.g. check quota).",
    "status": "RESOURCE_EXHAUSTED"
  }
}

Troubleshooting already done:

  • Logged out and back in
  • Fully uninstalled and reinstalled the app
  • Issue persists exactly the same after both

Since this survived a full reinstall, it doesn’t seem to be a local/cache issue — looks like it’s server-side, possibly an entitlement/quota sync issue on the backend not reflecting correctly in the UI.

Would appreciate someone from the team looking into my account’s entitlement status. Happy to provide more details if needed.

Thanks!

2

This is happening to me too since 7th September with Antigravity-IDE.
I tried Antigravity-x64 and it worked.
I downloading it from Google Antigravity - Download (direct link: storage.googleapis.), and unzipped it to ../Downloads/antigravity/Antigravity-x64.

Then I executed in the terminal of my Antigravity-IDE (after granting the file exec permissions):

`“$HOME/Downloads/antigravity/Antigravity-x64/antigravity”`

and the Agent Manager opened.
Now I work with both Antigravity IDE and the Agent Manager:

image
image1600×549 102 KB

It seems Antigravity IDE and Antigravity-x64 use different endpoints to the servers.
I hope this gets fixed soon but at least it’s working right now until the solution comes.

3

Hi @great_onweazu ,

Thank you for providing the details.

Could you please try the following steps to get unblocked:

  1. Start a Fresh Chat Session: Long conversation histories re-send huge payloads on each turn, easily spiking per-minute limits. Starting a new session resets this payload and usually clears the 429 immediately.
  2. Switch Models: Different models route through separate serving pools. If you are on Pro, try switching to Gemini 3.8 or Gemini Flash, which have independent rate limits.
  3. Update to the Latest Build (v2.14): Ensure you are on the latest release with updated endpoint routing by downloading the installer from Google Antigravity - Releases (changelog: Google Antigravity - Changelog).

If the issue persists , please reach out back to us.