Google’s Antigravity 2.0 Update Burned Its Users — The Vision Is Right, the Rollout Wasn’t

So. Google shipped Antigravity 2.0 at I/O 2026 on May 19 and, yeah.

Thousands of paying users woke up to a broken workflow.

No code editor.

No terminal. No file explorer. The product they knew just… vanished. Replaced by something called an Agent OS. If you didn’t know to dig for the legacy download link, you’d think your tool spontaneously combusted.

Here’s the weird part: the tech underneath might actually make sense.

The numbers aren’t fake

Gemini 3.5 Flash pushes 289 output tokens per second on Artificial Analysis.

That’s the benchmark. For comparison, Claude Opus 4.7 hits 67. GPT-5.5 hits 71. Four times faster than the closest competitor. Not a sliver. A gulf.

Google claims 3.5 Flash beats Gemini 3.1 Pro on coding and agentic benchmarks. On paper, it’s a meaningful jump. And the new pricing? AI Ultra runs $100/month with 5x Pro limits. The flagship tier dropped from $250 to $200 and now throws in 20x Pro limits. Solo devs and small shops running heavy agentic workloads. The math roughly checks out.

But.

That staging bug in v2.0.0

Paid credits got torched. An internal Google endpoint was hammering user accounts before the hotfix in v2.0.1 landed. Auto-updater failed for a chunk of users too. Means they stayed on the broken version. Google confirmed it. Patched it. Trust? Already cracked.

Side note: their changelog for v2.0.1 says “various improvements.” Vague doesn’t begin to cover it.

The open-source thing is where it gets ugly

Gemini CLI. The open-source version. Is dead as of June 18. No warning, no migration path, no 1:1 replacement at launch.

Antigravity CLI dropped as a closed-source substitute, and The Register reported it’s missing capabilities the old tool had.

People built CI/CD pipelines around it.

Automation scripts. Internal tooling. All of it just lost its foundation. No documented way to port it forward.

And the Google developer forum thread? Titled “Antigravity v2.0: The worst IDE for development is an absolute disaster for actual development.” Hundreds of replies. Users hitting quotas in under 20 minutes.

Locked out mid-session with zero recourse.

The anger isn’t about features.

It’s about being blindsided.

Wait. There’s a rollback

Here’s what most users missed: the old Antigravity IDE didn’t disappear. It’s a separate download. Hidden. Force-migration happened without a clear “hey, here’s your escape hatch” button.

If you didn’t know to look, you’d assume there was no going back.

Is the IDE era actually over?

Honestly? Google read the trend right and the room wrong.

Agentic tools. Systems that plan, execute, and iterate across a codebase without constant hand-holding. That’s where things are heading. An IDE was built for human-authored code. When an AI writes, tests, and deploys autonomously, the editing interface becomes overhead. A real Agent OS doesn’t need a code editor cluttering the foreground.

But forcing that transition on paying users.

No rollback path, staging bug draining credits, open-source tool killed without parity. That’s how you lose the developers who’d actually champion the direction.

289 tok/s is real. The architecture is the right long-term bet.

Google built a future and forgot to build a bridge.

What to actually do

Download the legacy version now if you’re on Antigravity IDE. Don’t wait for the force-migrate. Evaluate Antigravity CLI as a test environment, nothing more. Don’t port critical workflows until someone publishes the feature parity gap and addresses it.

For anyone evaluating AI coding tools in 2026: test the exit ramp before you buy in.

A tool that moves your data one direction only?

That’s not a product. That’s a trap wearing a price tag.

The Agent OS era is coming. Google just stumbled into announcing it loudly. But stumble is the word — they broke things that didn’t need breaking. Developer trust doesn’t rebuild fast.