Issues with Gemini in Antigravity

Google Antigravity
1

Trajectory ID: 0eab3bd6-3633-46b9-b5f3-b38c775c53..
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0x264c8afca7bed0..
Headers: {“Alt-Svc”:[“h3=”:443"; ma=2592000,h3-29=“:443”; ma=2592000"],“Content-Length”:[“139”],“Content-Type”:[“text/event-stream”],“Date”:[“Wed, 09 Sep 2026 17:44:58 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=1502”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“264c8afca7bed0..”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

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

2

Hi @campeon_real_madrid,

Welcome to the Forum,

The HTTP 429 Too Many Requests (RESOURCE_EXHAUSTED)error occurs when model generation requests temporarily exceed the account’s rolling 60-second limit or Token-Per-Minute for your active model.

To resolve this and continue working smoothly:

  1. Pause for 60 to 120 seconds to allow your rolling rate limit bucket to replenish.
  2. Switch to Gemini Flash models (e.g., Gemini 3.7 or 3.8 Flash) using the model selector at the top of the chat panel. Flash models have significantly higher rate limits and separate throughput allowances ideal for rapid development iterations.
  3. If you hold an active Google One AI subscription and suspect your tier claims are out of sync, open the Command Palette (Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS), select Antigravity: Reset Onboarding, and log back in to refresh your OAuth entitlement claims.
  4. Ensure you do not have multiple concurrent Antigravity instances or background agents making simultaneous requests on the same account.

If you continue experiencing persistent rate limit issues, please share your platform and Antigravity version details.