429 RESOURCE_EXHAUSTED on ALL models despite full quota (Antigravity 1.23.2, RHEL 9.7)

Gemini API
1

Body:

I’m experiencing a persistent HTTP 429 RESOURCE_EXHAUSTED error blocking every model in Antigravity, despite my Model Quota dashboard showing availability across the board.

Environment:

OS: Red Hat Enterprise Linux 9.7

Antigravity version: 1.23.2 (Release 1776330658.el8, x86_64)

Architecture: x86_64

Error details:

Trajectory ID: 9cf9f8a9-b360-491f-a3d8-f40f8bf7..

TraceID: 0xa29a113a26911..

X-Cloudaicompanion-Trace-Id: a29a113a2691125f

{

“error”: {

"code": 429,

"message": "Resource has been exhausted (e.g. check quota).",

"status": "RESOURCE_EXHAUSTED"

}

}

Models affected (all of them, not one specific model):

Gemini 3.6 Flash (High/Medium/Low)

Gemini 3.1 Pro (High/Low)

Claude Sonnet 4.6 (Thinking)

Claude Opus 4.6 (Thinking)

GPT-OSS 120B (Medium)

What I’ve already tried (none resolved it):

Retrying / starting a new conversation

Switching between every available model

Fully quitting and relaunching the app

Signing out and back in (fresh auth token)

Clearing local Cache, Code Cache, CachedData, GPUCache, DawnGraphiteCache, DawnWebGPUCache folders

Switching to other premium accounts on the same machine — same error persists regardless of account

My Settings → Models page shows quota available on every model, so this doesn’t appear to be a genuine quota exhaustion — it looks like a backend desync between quota tracking and enforcement, or possibly a machine/session-level block rather than account-specific, since the issue persists across multiple premium accounts. I noticed a similar report referencing an internal bug ID AG-859 that may be related.

Would appreciate any insight into what’s causing this or an ETA on a fix.

Worth noting: that detail actually shifts the diagnosis a bit — if it fails on multiple accounts from the same machine, it’s more likely something tied to your machine/network fingerprint (IP, device ID) than a single account’s quota bug. Good to flag both possibilities in the post like I did above.

2

Ran into the exact same issue on Fedora with 100% quota remaining. The recent builds (including 1.22.x and 1.23.2) appear to have a broken handshake/endpoint.

Since this is linux, you can simply downgrade to working version. (1.20 seems to be working fine)

  1. sudo dnf downgrade antigravity-1.20.6-1773706953.el8.x86_64
  2. close IDE
  3. pkill -f antigravity
  4. rm -rf ~/.config/antigravity ~/.cache/antigravity /tmp/antigravity* 2>/dev/null

Optionally you can do sth like ‘sudo dnf versionlock add antigravity’

Kind regards,
Przemek

3

Trajectory ID: 1b26d352-7571-4ef7-b683-ffd4a2614a06
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0xf33f02645b8940..
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 05:53:46 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=1111”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“f33f02645b8940..”],“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”
}
}

4

Me too…:worried:

All models. Fresh install. Never used Antigravity before. Gemini Pro account.

Trajectory ID: 0fc6e350-3f6a-4b27-ba05-c47078e61f..
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0xebe6da825a1d18..
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 15:26:07 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=219”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“ebe6da825a1d18..”],“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”
}
}

Antigravity Version: 1.23.2
VSCode OSS Version: 1.107.0
Commit: 15487b3041e65228cae24980a3f796c905ef582c
Date: 2026-04-16T08:28:19.366Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 7.0.0-30-generic
Language Server CL: 900566399

5

FYI, I just found the answer. It may only be an Ubuntu problem (not sure about that). But this works for me. Apparently it’s a cert problem as detailed on this thread (Persistent HTTP 429 "Resource Exhausted" error despite available quota (Antigravity 2.9.1) - #2 by praveen_murugesan)

NODE_TLS_REJECT_UNAUTHORIZED=0 /usr/share/antigravity/antigravity %F

6

yes it worked :+1:
NODE_TLS_REJECT_UNAUTHORIZED=0 /usr/share/antigravity/antigravity