Hello Antigravity Support Team,
My Antigravity agent is failing immediately with Agent execution terminated due to error, even when I submit a simple prompt:
Reply with OK. Do not read files or execute commands.
My displayed agent usage limit shows 100% remaining, but the request returns:
-
HTTP status: 429 Too Many Requests
-
Error status: RESOURCE_EXHAUSTED
-
Message: Resource has been exhausted (e.g. check quota).
Diagnostic details:
-
Trajectory ID: 7cd1d64a-3765-4281-b963-be25b3*****
-
Trace ID: 0xb49058bfc07*****
-
Timestamp: 18 October 2026, 11:47:28 UTC
-
Server: ESF
Since this happens even with a basic prompt, it does not appear to be caused by my project files or harness instructions.
Could you please investigate whether this is caused by an account entitlement issue, a model-specific or rolling rate limit, quota synchronization, or a backend service problem?
Please advise what is required to restore agent execution while my displayed usage limit remains available.
Thank you.
Hi @skhacker105,
Thank you for reaching out.
When a simple prompt immediately returns HTTP 429 RESOURCE_EXHAUSTED while your usage meter displays 100% remaining, it is typically caused by an outdated client build, a model-specific entitlement mismatch, or a stale OAuth session token (Plans).
Please try the following steps to resolve this:
- Update to the Latest Release:
- Ensure you are running the latest version of Antigravity (Antigravity App
v2.24.0, Antigravity IDE v2.5.5, or Antigravity CLI v1.4.2 — Changelog). Older client versions return persistent 429 RESOURCE_EXHAUSTED errors on all requests until updated.
- Test With Gemini 3.8 Flash & Refresh Your OAuth Session:
- Start a new conversation (
+) and select Gemini 3.8 Flash (Low or Medium) in the model picker (Choose a model), as separate quota pools and plan rules apply to different model families.
- Sign out and sign back in to refresh your entitlement token (in Antigravity IDE, press
Ctrl+Shift+P / Cmd+Shift+P → Antigravity: Reset Onboarding; in Antigravity CLI, run /logout then /login).
- Also verify that your Google Terms of Service country (country association form) and your Google One billing profile at pay.google.com both match a supported country/region.
- If the
429 Error Persists:
- Please reply with: (1) your Antigravity product and version, (2) the exact model selected when the
429 occurs, and (3) a screenshot of your Models & Usage tab (or submit an in-app feedback report).