Exacte same thing, havent used Antgravity for 3 weeks, I log in, my Gemini pro usage il already at 80% and resets in 6days 6 hours…
Yet, my Claudes are available on the normal 5h refresh rate.
how can they brake such basic feature heh
Exacte same thing, havent used Antgravity for 3 weeks, I log in, my Gemini pro usage il already at 80% and resets in 6days 6 hours…
Yet, my Claudes are available on the normal 5h refresh rate.
how can they brake such basic feature heh
having the same exact problem…. used antigravity fairly well (was much better than cursor 60usd) for a while but in late february/march it become very frugal with those credits. it is really annoying. i am on pro sub, now just contacted the support. they asked me to check my settings, delete antigravity connection, then relogin then reinstall antigravity, nothing worked so far.
i had to wait 148 hours to get gemini pro back and after just short 1 hours of work (for which 3-4 times encountered errors and did nothing) i am down to 40%. i am kinda fucking sick of all this and thinking about buying a big ram mac studio and do local coding…
Thank you for this, i reverted to 1.19.6 gemni 3.1 is no longer retarded atleast. Not sure about quota yet haven’t messed with claude model yet. I am on ultra
if you have the Antigravity Cockpit extension and/or Windows Antigravity Cockpit Software installed, i believe you have a security risk - 100% serious check your accounts settings and see if you are named “Peter Pan”.
What Google does is cause complete disappointment: 5-10 messages on a pro account and you can go for a walk for 5 days, it’s terrible.
I’ve been working with Antigravity for several months now and have come to the conclusion that it’s unusable for such large scale projects. Well, maybe only for small scripts, but for a large project it’s hopeless. It’s a shame, because it worked fine at the beginning of the year, but now it’s a disaster.
entirely agree. my day job is as an assistant for a store, i am the onsite tech consultant. so big or small it ends up on my desk. antigravity is great for tasks like “i need the text from this image to be sorted by brand and flavor in a text document.” just stuff i don’t want to do by hand.
when it comes to complex stuff - like building websites, building inventory management software, these are largescale high data tasks that just can’t be trusted with antigravity. the quality of antigravity, is equivalent to using “canvas” mode of gemini.google.com . where gemini will often just design the whole thing from the ground up, truncate important things, treat the project like a code tutoring walkthrough session rather than as an autonomous agent.
so yes @racer1933 i totally agree with your usecase. its great for small stuff, like disposable mock up projects or creating simple tools that will be used once and deleted afterwards, or simple evaluation of a project. but for developing and maintaining medium to largescale projects - its become increasingly less and less reliable as time goes on. i’ve been here since day 1 on antigravity the literal hour google went from 2.5 to 3.0 gemini, and while it may have been a bit of a struggle, it has gotten exponentially worse with the release of 3.1 and continues to trend in the direction of less usable as time goes on.
Even after full Canary + clean account isolation, Pro quota still gives 5~6 day reset after ~1 hour of use + Opus agent error drains quota on every retry
@DuctTapedGoat (and Google team)
I carefully followed your excellent guide (Chrome Canary as default browser + only Pro account logged in + aggressive clean reinstall). I also deleted the entire Chrome SxS\User Data folder to make sure there was zero leftover account data.
However, the issue persists:
After using about 1 hour (mostly Claude Opus 4.6 for agentic coding), the quota immediately jumps to multi-day lockout.
Current status (screenshot attached):
Gemini 3.1 Pro (High/Low) → Refreshes in 5 days, 17 hours
Even worse, when I try to continue my work with Claude Opus 4.6, I keep getting this error:
Agent terminated due to error
You can prompt the model to try again or start a new conversation if the error persists.
Every single retry consumes quota, but nothing actually progresses. So I’m burning through my limited quota just retrying the same failed agent.
I understand the Canary method fixes the old “account mismatch / 7-day security flag”, but it does not solve the current baseline quota behavior on Pro plan.
Pro is advertised as 5-hour rolling refresh, yet even light usage triggers 5~6+ day cooldowns.
Is this now the intended behavior after the Hybrid Quota change?
Or is there something else I should try? (Ultra upgrade? Overages only? Something new?)
Any advice or clarification would be really appreciated.
Thanks in advance.
You can prompt the model to try again or start a new conversation if the error persists.See our for more help. And this happens very often - a server overload error on the Google Cloud side.
oh heck - thats good its not kicking straight to 7 days after 7 days. but yeah - its straight painful testing the variants because of the duration it takes. its similar but you’re seeing that next level issue. i was finding this in some tests, which i found some resolution to in some related mac discussions a while back relating to bigint (more on that in a bit). so its possible the context is just full up - but normally, its actually supposed to compact/compress AUTOMATICALLY but this has been an issue regarding the Claude models in Antigravity from what i can see for a longer time than the 8+ day loops that surfaced in March. but theres another thing too which could be just large libraries in your working folder being added to the inherent context - so using a .gitignore file can help a lot if thats possible. since theres only 200k context available, it can get full up quick. (i should add though, i have talked with some people who have found issues conflicting with antivirus or vpn - so if you haven’t tried operating antigravity with those disabled, that might be worth a look, additionally i have also heard that the “first week back” is not fully back, but the following week was the final purgatory, this whole error is a mega pain).
you can try running the compress/compact manually with
/compact
but that wasn’t enough for me when i found myself facing a similar issue with larger context and consistent fails. i fabbed up this patcher to help address some of the outlier auth issues. i’ll put a blurb after the link to describe how it might help. it absolutely helps me on this exact thing - i would get that error, or “servers are busy” or a straight error 429, sometimes 503.
The term for how the BigInt patcher helps is Client-Side Serialization Fix.
Even though your data passes through Google and Anthropic, the problem occurs locally on your machine before the data ever leaves the Antigravity application.
Why the Header Size and BigInt Matter
The BigInt Serialization Error: Antigravity uses
JSON.stringifyto package your login tokens and session metadata into the HTTP request headers. In JavaScript,JSON.stringifycannot handle BigInts and will throw a fatal error.The 427/400 Header Limit: When your account has specific metadata (like a large Organization ID or a complex OAuth state), Antigravity tries to serialize it. If it fails, it can either crash the app or produce a malformed, overly large header that Google’s servers reject with a
400 Bad Requestor427error.How the Patcher Helps: It modifies the internal
main.jsfile to convert these massive BigInt numbers into Strings. Strings are smaller and “safe” for JSON. This keeps your request headers under the server’s size limit and prevents the local code from breaking.Summary of Impact
The patch doesn’t change how Anthropic or Google process the data; it simply ensures that your local Antigravity app can package the data correctly so it can be sent in the first place without hitting a “Request Header Too Large” wall.
How the Patcher Helps with 429 and 503
The 429 (Rate Limit) Fix: When the BigInt bug is active, the Antigravity client often gets “stuck” in a silent loop. It tries to send a message, fails locally because it can’t serialize the data, and then immediately retries—hundreds of times a second. Google’s servers see this as a bot attack and slap you with a 429 Too Many Requests. The patch stops the local failure, ending the infinite retry loop.
The 503 (Service Unavailable) Fix: A 503 usually means the server is overloaded, but in Antigravity, it often happens when your Request Headers are so bloated and malformed (due to unpatched BigInts) that the gateway server simply gives up on trying to parse them. It assumes the “service” (the part of the app that talks to the LLM) is broken and returns a 503.
After about 15-20 corrections, the Flash model starts to hallucinate, inserting edits wherever it wants. Comrades, I completely stopped feeling that I have a Pro account. What’s going on, google awww?
You have a valid point here. Since it became so restricted that I could not get much done anymore using Antigravtiy Pro plan previous month I moved (like many) to Claude Code $20 plan. And a week later usage limit restrictions came there as well, although not nearly as bad as Antigravity level where the $20 almost equals the free plan. Now using a Claude code $20 subscription in combination with Codex/Coplit $20 subscription. When locked out in one I continue with the other, this is currently enough for me to get through the week.
Although I do not just vibe code but do other things as well in the mean time that require minimal AI support. I think if you do vibe coding fulltime you at least need a $100 Claude or Codex plan to have enough nowadays. While in the past any $20 plan would get a long way. And most alternatives fro AG seem to be way less buggy and more powerfull anyway, meaning gettings thing done the first time saves also time and credits.
At least that is what I noticed, the main selling point for AG was kind of that you got a lot of credits to use (the plan mode and agentic processing now everybody supports) but since it is now reversed that AG provides maybe the least amount credits of all mayor systems that advantage is gone.
Feel free to disagree or provide other insights, I do however still like the Antigravity UI. And that it is way easier to switch between agents and see what is going on in which sessions. All other UIs I have seen are a bit lacking in this aspect.
I’d previously signed up and ditched a few months ago, usage limits were pretty good but didn’t need at the time. I signed up ‘again’ a few days ago and exactly same issue as above. Very light usage a few tweaks to a Godot plugin and no have to wait a week, something definitely not right.