Antigravity IDE: Persistent HTTP 429 (RESOURCE_EXHAUSTED) and "certificate has expired" across multiple accounts

Google Antigravity
1

Hi everyone,

I’ve been experiencing this issue for the past two weeks. Neither the Agent chat (any model) nor the AI commit message generator are working.

I have already tested with different Google accounts, and a colleague/friend of mine is facing the exact same problem on their setup as well.

Environment

  • IDE: Antigravity 1.107.0 (Debian package 1.23.2-1776332190)

  • OS: Linux x64 (Kernel 7.0.0-31-generic)

  • Endpoint: Pointing to [https://cloudcode-pa.googleapis.com](https://cloudcode-pa.googleapis.com)

1. Commit Message Generation Error

Fails immediately with:

Error generating commit message: [internal] certificate has expired

2. Agent Chat Error (All Models)

Sending any simple prompt (e.g. “Hello”) immediately triggers:

Trajectory ID: 7d7de981-9e12-45a9-8962-2****
Error: HTTP 429 Too Many Requests
Sherlog: 
TraceID: 0xba45d0f5****
Headers: {"Alt-Svc":["h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"],"Content-Length":["139"],"Content-Type":["text/event-stream"],"Date":["Wed, 16 Sep 2026 18:39:26 GMT"],"Server":["ESF"],"Server-Timing":["gfet4t7; dur=385"],"Vary":["Origin","X-Origin","Referer"],"X-Cloudaicompanion-Trace-Id":["ba45d0f5****"],"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"
  }
}

A friend is facing the exact same behavior on their machine. Please note that upgrading to Antigravity 2.0 is not an option for my workflow—I intentionally need to remain on the 1.x branch, so I’m looking for a solution that doesn’t simply rely on migrating to 2.0+.

Given that this has persisted for two weeks across distinct accounts, machines, and production endpoints, is there a known backend quota restriction or an expired mTLS/root certificate bundled within the 1.x Linux client? Any guidance on resolving this within 1.x would be greatly appreciated.

2

Hi @Wesley_Santos,

Welcome to the Forum,

Thank you for the detailed report. The errors you’re encountering ([internal] certificate has expired and HTTP 429 RESOURCE_EXHAUSTED) are happening because the bundled security certificates inside the legacy Antigravity 1.x Linux client have expired. When the client tries to establish a secure connection to our production backend, the TLS validation fails. Because of this failure, requests for AI commit message generation and Agent Chat are being rejected before they even reach the server.

I realize you have a strong preference to keep your workflow on the 1.x branch. However, since the 1.x builds are deprecated, the security certificate chains on that branch are no longer being maintained or patched. Because of this, there is no secure or officially supported workaround to restore connectivity on 1.x.

I’m sorry I don’t have better news regarding 1.x, but migrating to a supported 2.x release is the only way to restore your access to the agent and commit generation features.

3

Hi,

Thank you for the clear explanation regarding the expired TLS certificate chains bundled in the legacy 1.x builds. That completely explains the root cause.

Following your recommendation, I went ahead and migrated my Linux environment to the Antigravity 2.x release. Both the Agent chat and the AI commit message generation features are now working properly.

I appreciate the help, this issue can be considered resolved.