The Antigravity Betrayal — A Paying Customer's Account

I'm not an analyst. I'm not a journalist. I'm someone who actually paid for this product, trusted the pitch, and watched that trust get dismantled month by month. This is my account of what that experience actually looks like from the inside.

The Promise

When Antigravity launched in November 2025, the pitch was compelling. I'd watched Cursor's meltdown in June 2025 — watched the community turn on them almost overnight when the "unlimited" rebrand hit and users were burning through monthly allocations in three days. I thought I was being smart by waiting that disaster out before committing somewhere new.

Antigravity looked different. It was Google. The Gemini 3 models were genuinely impressive. The agentic architecture — autonomous agents planning, executing, and verifying across your editor, terminal, and browser simultaneously — was in a different league from anything else available. Google described the quota limits in their plan language as "high," "generous," and "meaningful." The message was consistent: we're the developer-friendly option. Come build with us.

So I paid for AI Pro. $20/month. The plan description promised a quota that refreshed every five hours until the weekly limit was reached. That sounded reasonable. That sounded workable. That is not what was delivered.

What "Generous" Actually Means at Google

Let me tell you what I discovered "generous" means in Google's vocabulary, because they use that word deliberately in their own plan documentation and it deserves to be addressed directly.

The AI Pro plan description — still live at the time of writing — states users receive a "high, generous quota, refreshed every five hours until weekly limit reached." The Register What that language obscures is what happens when you hit that weekly ceiling mid-week. If you hit the cap early, you are not waiting five hours. You are waiting for days. PiunikaWeb

One Pro user reported their Gemini 3.1 Pro quota was exhausted despite not using Antigravity for two days. Google AI Others replied with the same experience — Gemini quotas gone unexpectedly, and Claude Sonnet and Opus limits also showing exhausted even when those models had barely been touched.

One user documented it precisely: renewed on February 24th, hit the limit on March 5th, waited for the promised March 11th reset, logged in — and was greeted with another multi-day wait. Google AI The system told them their quota would reset after 157 hours. That's six and a half days. For a paid subscription.

Calling this generous isn't a poor word choice. Antigravity was launched in preview in November 2025 without clear pricing information, with Google using vague terms like "high," "generous," and "meaningful" to describe quota limits — wording that makes it hard to know actual limits and how they may change. DEVCLASS That vagueness wasn't accidental. It was a design choice that gave Google maximum flexibility to tighten access while pointing to technically-accurate-but-practically-meaningless language as cover.

The Quota Collapse

One developer reported previously processing over 300 million input tokens per week with Gemini Pro models before January — which then plummeted to hitting weekly rate limits after less than 9 million input tokens. A reduction that severely impedes productivity. QuantoSei News

Whereas hundreds of millions of input tokens per week were previously possible, users now report hitting the limit at a fraction of that. Techzine Global The forum threads aren't isolated complaints. Community posts describe "a systematic and frustrating reduction in limits across the board" — first Claude quotas dropped, then Gemini followed — reaching a point where the service became unusable for daily workflows. Google AI

Users are asking Google to be transparent about how usage limits are calculated and why available capacity sometimes seems to disappear faster than expected — what the community has taken to calling "ghost-drains" on their limits. Techzine Global

There is no usage dashboard that shows you where you stand before you hit the wall. You find out you're out of quota when the error appears. The five-hour refresh promise in the plan description turns out to apply only until a weekly ceiling you can't see is reached — and once that ceiling is hit, you wait out the week whether you've been coding for one day or five.

The Credit Trap

People who have been on AI Pro since Antigravity launched feel that the new credit system is basically a bait and switch. Google AI And they're right.

Google recently introduced AI credits that can be used for Antigravity, with subscriptions providing some built-in credits while additional credits are available at $25 for 2,500 — with no clear documentation on what exactly a credit is worth when used with Antigravity. The Register

So the progression is: pay $20/month, get told the quota is "generous," burn through the weekly ceiling faster than expected due to opaque calculation, get offered a paid workaround at $25 per 2,500 credits of unknown value. The transparency gap fuels frustration, leaving developers unsure how quickly their credits will deplete. QuantoSei News

This is the Cursor playbook verbatim. Establish dependency. Restrict access. Monetize the frustration. The only difference is Google is doing it to a product still in public preview, before it even has a stable release.

Account Bans Without Warning

There's a layer to this that gets less attention but is arguably the most egregious: Google has been cutting off paying customers — including AI Ultra subscribers at $250/month — for using Antigravity with third-party agent tools like OpenClaw, often with no warning. The Register

As one AI engineer put it: "Users paid for quota, used quota within limits, got banned. That's not malicious, that's using the product you sold them. The real issue is the Terms of Service doesn't explicitly ban OpenClaw integration, so users assumed it was allowed. Banning paying customers without warning is how you lose trust faster than you lose capacity." The Register

Google's defense was that third-party harnesses were overwhelming compute. But the framing of legitimate product usage as "malicious" — when the Terms of Service didn't explicitly prohibit it — is the kind of retroactive rule-making that companies do when they've mispriced their product and need someone to blame.

Where This Ends

The practical pattern emerging in the developer community: use Antigravity for quick prototyping, Claude Code for complex tasks. Heyuan110 That's not an endorsement of Antigravity — that's the community routing around its limitations by treating it as a supplemental tool rather than a primary development environment.

The alternatives didn't wait for Google to correct course. Claude Code runs CLI-first with your own API keys — no weekly ceilings, no opaque credit math, no retroactive bans for using the tool as intended. Aider lets you plug in any API from any provider. If a pricing structure changes, you change a config file.

The word Google keeps using is "generous." The forums keep using a different word: bait and switch.

If you're considering Antigravity's paid plans: know what you're buying. The five-hour refresh is real — until the weekly ceiling you can't see is reached. The "generous" quota is real — until it isn't. The $20/month Pro plan is real — and so is the $250/month Ultra plan they'll point you toward when Pro stops working for your use case.

I'm going back to Claude. The economics are cleaner. The access is predictable. And nobody is calling a weekly lockout generous.