Over the past few weeks, Antigravity has gone from a promising developer tool to a system that feels fundamentally broken. And judging from the flood of reports in this forum—multi‑day quota lockouts, workspace failures, slash commands disappearing, IDE crashes—this is no longer an isolated issue. It’s systemic.
What’s most frustrating is that they seems to have forgotten what it originally promised to paying users.
Google Antigravity Documentation
1. The advertised 5‑hour quota refresh has silently turned into a 167‑hour (7‑day) lockout
When many of us subscribed to Google AI Pro, the official messaging was clear:
- Quota refreshes every 5 hours
- Stable access for Pro users
- 1000 credits that replenish frequently
But today?
- Pro users are locked for ~167 hours
- Ultra users (paying 10× more) are also locked for 7 days
- Flash models are the only ones unaffected
- Even zero usage can still trigger a multi‑day lockout
How does a $20 Pro subscription end up offering less usable time than a $10 Claude plan?
How does a $250 Ultra subscription justify a week‑long cooldown?
If this isn’t a regression, what is it?
2. Antigravity 1.20.x introduced catastrophic breakages
These aren’t minor bugs. These are core‑functionality failures that make the IDE unusable.
Workspace detection is broken
In 1.20.3/4/5, the underlying workspace path detection engine was damaged.
Even when your project is open, the Customizations panel loses access to the local directory and throws:
ConnectError: [unknown] no workspaces found
Slash commands no longer appear
Because the workspace cannot be detected, every workflow under .agent/workflows/ disappears from the input box.
No /brainstorm, no /fix, no nothing.
Creating new Rules or Workflows fails
Clicking “+ Workspace” in the UI cannot write to disk.
It simply throws a red‑cross error and refuses to create anything.
These issues make Antigravity’s core developer experience collapse entirely.
3. Google’s public messaging makes the situation worse
What shocked many of us wasn’t just the bugs—it was the response.
4. This is not instability. This is a full‑scale regression.
Just look at the front page of this forum right now:
- 144–168 hour lockouts
- Quota dropping to zero overnight
- Workspace detection failures
- Slash commands missing
- Rules/Skills failing to import
- IDE crashing on basic actions
- Quota logic completely inconsistent
This is a paid product that cannot perform its core functions.
5. We’re not asking for special treatment. We’re asking them to honor its own commitments.
What paying users want is simple:
- Restore the 5‑hour quota refresh that was advertised
- Fix the 1.20.x workspace and slash‑command failures
- Provide a clear explanation and timeline
- Stop silently reducing quotas without announcement
Google, your developer community is not asking for miracles.
We’re asking for reliability, honesty, and respect.
Antigravity is not progressing—it’s regressing
We subscribed because we believed in the product.
We believed in the roadmap.
But right now, Antigravity is losing the trust it worked so hard to build.
This isn’t anger.
This is a warning about trust that is rapidly eroding.
