Subject: Persistent HTTP 429 / RESOURCE_EXHAUSTED despite 35,000 available AI credits

Google Antigravity
1

Hello Google Antigravity Support Team,

For the past few days, I have repeatedly encountered “Agent execution terminated due to error” when submitting requests in Antigravity. This is preventing me from working on my projects.

My account currently shows “Available AI Credits: 35000,” and “Enable AI Credit Overages” is switched on. Despite this, requests fail with HTTP 429 and RESOURCE_EXHAUSTED.

The attached screenshots show the failed request with Claude Sonnet 4.6 (Thinking) selected, along with my available credits and enabled credit overages.

The latest “Copy debug info” contains:

Trajectory ID: 8a38160d-cc25-46cf-940c***
TraceID: 0xe277484d*
Error: HTTP 429 Too Many Requests
Timestamp: 20 September 2026, 04:33:58 GMT
X-Cloudaicompanion-Trace-Id: e277484d3**

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

Please investigate why requests are being rejected while I have 35,000 available AI credits and credit overages enabled. If a separate rate limit, model quota, or service capacity restriction applies, please identify which restriction is affecting my account and explain when it resets.

Please also confirm whether my available credits can be used for the selected model and provide the steps needed to restore access.

A clearer error message explaining the specific restriction and expected recovery time would be very helpful.

Thank you for your assistance.

Best regards,
José María Cabeza Rodríguez

Open Google Antigravity and a local project.

  1. Select “Claude Sonnet 4.6 (Thinking)” and Plan mode.
  2. Confirm that “Enable AI Credit Overages” is enabled and the account shows “Available AI Credits: 35000.”
  3. Submit a prompt asking the agent to investigate a project issue.
  4. The agent stops with “Agent execution terminated due to error.”
  5. Click “Copy debug info.” The output shows HTTP 429 Too Many Requests, status RESOURCE_EXHAUSTED, and “Resource has been exhausted (e.g. check quota).”

Expected result: The agent processes the request, using available AI credits where applicable.

Actual result: The request fails despite 35,000 available AI credits and credit overages being enabled. This issue has occurred repeatedly over the past few days.

Screenshot from 2026-09-20 06-36-41
Screenshot from 2026-09-20 06-36-41691×1080 39.3 KB

2

Hi @Jose_Maria_Cabeza_Ro,

Thank you for reaching out and providing a detailed explanation along with the screenshot of your setup.

Please note that your available AI Credits represent your overall account credit allowance, whereas an HTTP 429 / RESOURCE_EXHAUSTED error indicates that a short-term, rolling rate limit (Tokens Per Minute) has been reached on the backend serving cluster for the selected model tier. High-reasoning models such as Claude Sonnet 4.6 (Thinking) enforce strict per-minute throughput limits. Multi-turn conversations or Plan mode runs transmit large cumulative prompt payloads that can temporarily saturate these rolling 60-second limits, even when your total credit balance is high.

To resolve this and continue working:

  1. Pause Briefly: Wait 60 to 120 seconds to allow the rolling per-minute token bucket (TPM/RPM) to reset.
  2. Start a Fresh Chat Session: Click New Chat (Ctrl+N on Windows/Linux or Cmd+N on macOS) to clear accumulated context history so subsequent requests transmit smaller prompt payloads.
  3. Switch Active Model Tier: For rapid or iterative coding tasks, select Gemini 3.7 Flash or Gemini 3.8 Flash from the model selector dropdown, as Flash models provide significantly higher per-minute throughput limits.
  4. Refresh Session Routing: If 429 errors persist across all models, open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P), select Antigravity: Reset Onboarding, and reload the window.
  5. Check for Updates & Share Diagnostic Logs: Ensure you are on the latest release via Help > Check for Updates (or Google Antigravity - Releases).

If the issue persists after trying the steps above, please provide your diagnostic logs dumped in a .txt file (from Help > Toggle Developer Tools > Console or View > Output > Antigravity Language Server).