Antigravity 1.23.2 - 429 Error since last night

[Ronit_Vishwakarma]

I was using 1.23.2 it was working well then it stopped and started to throw 429.

• It wasnt quota cause same pro account in 2.5.x version is making calls properly.
• I would prefer to keep using 1.23.2 to avoid checkpoint compression of context.
  Important - I have not exhausted Quota. a friend in Singapore hit the identical error on 1.23.2.

the error is for all models. the working blinks for about 14 seconds then agent terminated for all models. reinstalled after clean wipe threw same error.

Trajectory ID: 174627e3-c53b-4a65-a0d***********
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0x536699fd2a**********

Headers: {“Alt-Svc”:[“h3=”:443"; ma=2592000,h3-29=“:443”; ma=2592000"],“Content-Length”:[“139”],“Content-Type”:[“text/event-stream”],“Date”:[“Fri, 04 Sep 2026 21:23:57 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=689”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“536699fd********”],“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”
}
}

[p1ln]

Same Issue
Trajectory ID: 1c77e6f4-c5a6-4490-ac8a-4***********
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0x1434726cb**********
Headers: {“Alt-Svc”:[“h3=”:443"; ma=2592000,h3-29=“:443”; ma=2592000"],“Content-Length”:[“139”],“Content-Type”:[“text/event-stream”],“Date”:[“Sat, 05 Sep 2026 14:46:11 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=1250”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“1434726cb*******”],“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”
}
}

persists across two accounts, both on a pro plan and two networks.

[RichardT]

Same here, happening for me on my Google Workspace and personal Gmail account. I am using Antigravity IDE Version: 1.23.2 on Ubuntu Linux. Here is my console error

Trajectory ID: a2b3d7ed-421c-4d62-bc69-f***********
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0xee944b5dbf******
Headers: {"Alt-Svc":["h3=":443"; ma=2592000,h3-29=":443"; ma=2592000"],"Content-Length":["139"],"Content-Type":["text/event-stream"],"Date":["Sat, 05 Sep 2026 15:18:59 GMT"],"Server":["ESF"],"Server-Timing":["gfet4t7; dur=130"],"Vary":["Origin","X-Origin","Referer"],"X-Cloudaicompanion-Trace-Id":["ee944b5dbf*****"],"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"
}
}

I recently switched from Google AI Pro Max to Google AI Pro for my personal account. I thought that might have been the reason, but both Google Workspace and personal Gmail are not able to use Antigravity at the moment. I can use Claude Code inside of Antigravity, and other AI tools like Hermes are working, but Antigravity is just totally broken. Hope to have this fixed soon!

[Ronit_Vishwakarma]

@RichardT @p1ln

Adding another data point.

Anything above 1.23.2 (2.x+) doesn’t show this 429 for me, but introduces a different issue instead — aggressive context summarization/compression on long sessions, which loses earlier context. Only tested this with Gemini models on 2.x+ (never saw a need to test it on 1.23.2, since 1.23.2 never gave me this issue in the first place and thats why i prefer to be in 1.23.2).

How I isolated the two:

• 429 (1.23.2): confirmed via 2-Antigravity Quota.log under %APPDATA%\Antigravity\logs\...\exthost\output_logging_...\ — every quota poll during the failure showed healthy remaining %, ruling out an actual exhausted quota.
• Compression (2.x+, Gemini only): attach a doc, ask the agent to recall a fact from deep in it after several turns — works fine always with claude and gemini pro, but once a Gemini flash turn gets mixed in mid-session, it loses access to the original document, and every model afterward inherits that gap too.

So right now it’s pick-your-poison: 1.23.2 gets the 429, 2.x+ gets the compression/context-loss problem (at least on Gemini). Haven’t found a version with neither yet — if anyone has, would be good to know.

[Garv_Gupta]

Facing the same issue… 1.23.2 was running butter smooth until last night.. I woke up this morning to find this issue… im not even sure how long would it take for the tech team to figure the problem and fix it.. im stuck…

[RichardT]

@Bitu79 How is this relevant to the issue being discussed? I am not seeing the connection. What results are you getting on other computer with Antigravity installed? I am able to connect to my account in Antigravity on my Macbook Pro without any issues, but I am still unable to connect from my primary Ubuntu workstation. Are you guys seeing the same or different behavior?

[Ravi_Bro]

Here’s a ready-to-post reply:

---

Adding another data point with a more specific underlying error, which might help narrow down the root cause.

Environment:

• OS: Ubuntu Linux
• Antigravity IDE version: 1.107.0 (build 15487b3041e65228cae24980a3****)
• CLI (agy) version: 1.1.27 (freshly reinstalled)
• Account: Google Pro plan, quota confirmed not exhausted

What I’m seeing: Instead of a plain 429 in the chat, every agent request fails after a few seconds with “Agent execution terminated due to error.” Digging into the logs shows the actual root cause is a local language server failure, not a real quota/rate-limit issue:

[ERROR]: LS check error: [internal] certificate has expired
http: TLS handshake error from 127.0.0.1:XXXXX: EOF

This repeats every second, hitting the LS’s own loopback (127.0.0.1) HTTPS endpoint — it looks like the language server is failing its own internal cert self-check, unrelated to any Google Cloud backend call. Meanwhile cloudcode.log shows loadCodeAssist and fetchAvailableModels calls succeeding normally, so the actual API/auth layer seems fine — this is purely a local LS-to-LS handshake failing.

What I’ve already ruled out:

• System clock/timezone: correct and NTP-synced (confirmed via timedatectl)
• Stale local cert file: none found anywhere on disk (find for .pem/.crt/.key turned up nothing)
• Stale cache/config: fully wiped ~/.config/Antigravity, ~/.antigravity, ~/.gemini/antigravity, then did a clean reinstall of the CLI — identical error persisted afterward
• Outdated build: already on 1.107.0 (GUI) / 1.1.27 (CLI), both reported as latest by the installer

Given this happens on a version above the 1.23.2/2.x range discussed here, and survives a full wipe + reinstall, it seems like this may be a broader/different manifestation of the same underlying issue rather than a client-side cache or quota problem. Wanted to flag the more specific cert error in case it helps your team pinpoint what’s actually failing on the LS side.

Happy to provide more logs if useful.

[Abid_Hossain_Sifat]

I’m also facing this issue today. Has anyone found a solution?

[vinoth_sowndarya21]

Hi Google Antigravity team,

I am experiencing a persistent HTTP 429 RESOURCE_EXHAUSTED error in Google Antigravity.

The error occurs even when sending a very simple prompt such as:

hello

Error:

HTTP 429 Too Many Requests

Status:
RESOURCE_EXHAUSTED

Message:
Resource has been exhausted (e.g. check quota).

Trajectory ID:
1aa3ea46-1603-44f5-b54b-182*********

TraceID:
0xa07e6b029*******

X-Cloudaicompanion-Trace-Id:
a07e6b0293*******

Date:
September 6, 2026

Environment:
Windows

Network:
Mobile Hotspot

I have already performed extensive troubleshooting:

1. Uninstalled Antigravity completely.
2. Installed Antigravity again from a fresh installation.
3. Logged in using a DIFFERENT Gmail/Google account.
4. Created a completely new conversation.
5. Tested with a simple “hello” prompt.
6. Reset/cleared the .gemini directory.
7. Reset/cleared the .antigravity directory.
8. Reset Antigravity-related AppData.
9. Restarted Windows.
10. Logged out and logged in again.
11. I am using a mobile hotspot rather than an office/Wi-Fi network.

Most importantly, I tested multiple available models, and ALL of them produce the same error:

• Gemini 3.6 Flash (High)
• Gemini 3.6 Flash (Medium)
• Gemini 3.6 Flash (Low)
• Gemini 3.1 Pro (High)
• Gemini 3.1 Pro (Low)
• Claude Sonnet 4.6 (Thinking)
• Claude Opus 4.6 (Thinking)
• GPT-OSS 120B (Medium)

The error is therefore not limited to a single model.

The same issue also occurs with a completely different Google account after a fresh Antigravity installation.

Because the issue persists across:

• Different Google account
• Fresh installation
• New conversation
• Multiple models
• Simple prompts
• Mobile hotspot connection

I suspect this may be related to an Antigravity backend/service-side issue, quota synchronization issue, or account/backend routing issue rather than a local installation problem.

Could you please investigate the Trajectory ID and TraceID above and check the backend logs/quota state?

I have attached a screenshot showing the available models and the agent execution error.

Thank you.

[Min-Jin_Kim]

Same issue here, and in my case the quota is at 100% — completely unused.

Reference: AG-859

Trajectory ID: 0fff530b-e1b3-436e-a3c3-95********* (2026-09-05 11:47 GMT)
Trajectory ID: 5df13583-3372-479a-9488-a8******** (2026-09-06 04:00 GMT)
TraceID: 0x69208500******/ 0xe2bb230fc*****

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

Ongoing for 25+ hours. Everything below has been ruled out:

1. QUOTA IS FULL. Dashboard shows every model at “Refreshes in 5 hours,
   0 minute” with full bars — quota had just reset and was 100% unused.
   Sent one request immediately after: still 429. (screenshot attached)
2. Brand new conversation, prompt was literally “hi” (2 characters).
   Fresh trajectory ID. Still 429.
3. ALL model groups fail — Gemini 3.6 Flash (High/Medium/Low),
   Gemini 3.1 Pro (High/Low), Claude Sonnet 4.6, Claude Opus 4.6,
   GPT-OSS 120B. These draw on separate quota pools.
4. Server-Timing dur=179ms / 188ms — rejected before model execution.
5. NO Retry-After header in any response.
6. No VPN, no proxy. Windows.
7. Signed out, signed in with a different Google account, signed back in.
   No effect.

SECOND BUG — AI Credit Overages does not fire:
“Enable AI Credit Overages” is ON and I have 1,784 credits available,
but the credit activity log shows ZERO deductions since Aug 31, 2026.
The credits page also states that plan-included AI credits have been
“replaced by product-based usage limits”. So the documented fallback
(“Antigravity will use your AI credits once you’re out of model quota”)
never happens — requests just hard-fail with 429 instead.

Antigravity version: __
Plan: __

This is an account-level lockout, not a quota issue. Please investigate.
Also requesting service credit for the downtime.

[Reyner_WilliamsLiong]

is there any updates yet? I’m also facing the same thing since this morning

[Rushiraj_Pandya]

Experiencing the exact same issue today on Ubuntu 22.04 with an active Pro subscription. Even after clearing the IDE cache and resetting configuration files, requests immediately fail with 429 RESOURCE_EXHAUSTED. Multiple members on my team are hitting this simultaneously.

Trajectory ID: 72c2c712-6f76-471d-962b-7d1*********
Error: HTTP 429 Too Many Requests
Sherlog:
TraceID: 0xa1aece********
Headers: {“Alt-Svc”:[“h3=”:443"; ma=2592000,h3-29=“:443”; ma=2592000"],“Content-Length”:[“139”],“Content-Type”:[“text/event-stream”],“Date”:[“Mon, 07 Sep 2026 04:54:52 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=639”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“a1aece9fdf******”],“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”
}
}

[Salman_Aashif_M]

what version you use? latest or share any version that you use?

[Salman_Aashif_M]

Can all share you version of antigravity to check is there any issue with updated version or all version.Kindly share.

[Reyner_WilliamsLiong]

i use 1.23.2, and on pro plan

[Salman_Aashif_M]

1.23.2 - i currently use same version that you use , faced that issue. If others share thier version we can find is any issue in versions.

[MAX721]

i use 1.23.2, and on pro plan too

[awais305]

I was facing this issue for the last 2-3 days. I think it’s time to say goodbye to v1.23.2 and say Hello to v2.0 Antigravity IDE.

After installing IDE, press Migrate/Copy and follow the steps.

If your old chats aren’t showing up, don’t panic. You can recover them from the old Antigravity data.
For reference,

<https//www.reddit.com/r/google_antigravity/s/hFcp5UqQO7>

I wasn’t updating due to the Agentic Window because I didn’t wanted to lose control over what to keep and what to discard.

The new IDE works the same way. You still have full control when reviewing changes, you can keep or reject individual lines of code.

[RichardT]

Hmm interesting I am on v1.23.2 on Linux… I tried to update to v2, but it did not seem to work… I’ll try totally removing the current version of Antigravity tomorrow and reinstalling v2.0