Google Antigravity 2.0 Broke Your Setup? What Changed and How to Recover

You opened Antigravity one morning and your editor was gone. No file explorer, no terminal, no source control panel. In its place: a chat-style interface for orchestrating agents, and a lot of confused profanity in your head. If that's you, you're not alone, and you didn't break anything. The May 19, 2026 rollout of Antigravity 2.0 did this to a large number of developers at once, and the fix is more about understanding what Google actually shipped than about repairing your machine.

This is a practical walkthrough: what changed, why your projects and history vanished, and the specific recovery paths depending on whether you want to embrace 2.0 or roll back.

A quick history of how we got here

Google launched the original Antigravity on November 18, 2025 as a free public preview, alongside the Gemini 3 model family. It was an agent-first IDE built as a fork of VS Code, and the initial preview shipped as version 1.11.2. It had two main views: an Editor view that felt like a normal VS Code-style IDE, and a Manager view that orchestrated multiple parallel agents. It ran on macOS, Windows, and Linux and supported a range of models including Gemini 3 Pro, Gemini 3 Flash, GPT-OSS-120B, and Anthropic Claude Sonnet/Opus 4.6.

So for roughly six months, "Antigravity" meant "an AI IDE." Muscle memory formed. Then I/O 2026 happened.

What Antigravity 2.0 actually is

At Google I/O 2026 on May 19, 2026, Google launched Antigravity 2.0 as a separate, standalone, agent-first desktop app. This is the critical detail that the rollout buried: 2.0 is not a version bump of the IDE. It shipped alongside an Antigravity CLI (written in Go), an Antigravity SDK (Python/TS/Go), Managed Agents in the Gemini API, and the Gemini Enterprise Agent Platform.

Antigravity is now a four-surface platform, all running on the same underlying agent harness:

The intended workflow is what Google calls dual-wielding: run Antigravity 2.0 for agent orchestration alongside an IDE of your choice (the Antigravity IDE or any other editor) for code editing. The IDE was never killed. It was just no longer the thing the auto-update left running on your screen.

The product still has an IDE. What Google shipped was a default-surface change with no warning, no in-app explanation, and no built-in rollback. That's a communication failure, not a feature removal — but on a Tuesday morning, the difference doesn't help you ship.

Why it broke so many setups

The update was pushed as an automatic update with no warning and no built-in rollback. For existing users it replaced their working IDE with the orchestration desktop app, which is why so many people opened it to find the editor, file explorer, terminal, and source control simply absent.

It got worse from there. The update split app data into separate, non-backward-compatible directories. On Windows the old IDE wrote to \Roaming\Antigravity, while the new version reads from \Roaming\Antigravity IDE. Same machine, different folder — so projects, conversation history, settings, and extensions all appeared to be missing because the new app was looking at an empty directory.

On top of that, the Google AI Developers Forum filled with reorganization bugs:

• Every conversation became its own new project
• Projects and conversations got mixed up
• URL-encoded text appeared in project names
• "Agent terminated due to error" crashes
• Disappearing UI and repeated credit popups
• "Selected model is not supported" errors

Quota handling was reportedly broken too. Some premium users were locked out after a single small change (one user cited a single CSS edit), and at least one reported burning an entire 5-hour daily quota in under a minute.

The reaction matched the disruption. Sentiment on the Antigravity subreddit, the developer forum, and DEV/Medium was strongly negative — one representative line called it "a massive step backward," another said it "reeks of non-technical people shipping code to production." Google's public response came via Logan Kilpatrick, who clarified that the product "still has the IDE, the experience is getting updated to make this more clear." No formal rollback mechanism was provided in the forum thread.

Recovery option A: stay on 2.0, get your IDE back

If you're willing to live with the new model (orchestration app plus a separate editor), this is the cleaner path:

1. Fully uninstall, then kill any lingering Antigravity processes.
2. Download the standalone Antigravity IDE from antigravity.google/download#antigravity-ide.
3. Restore your data by manually copying it from the old folder into the new one — on Windows, from \Roaming\Antigravity into \Roaming\Antigravity IDE. This brings back projects and settings.

You end up dual-wielding the way Google intended: 2.0 for parallel agent work, the IDE for hands-on editing with line-by-line accept/reject.

Recovery option B: full rollback to the old IDE

If you want the pre-2.0 experience back, you can downgrade. A widely shared Windows procedure pins version 1.23.2:

1. Back up ~/.gemini/antigravity.
2. Stop all antigravity processes.
3. Silently uninstall 2.0.
4. Download v1.23.2 from antigravity.google/releases and reinstall.
5. Restore your backed-up files.
6. Disable auto-update by setting "update.mode": "none" in settings.json (on Windows, %APPDATA%\Antigravity\User\settings.json).

On macOS, the shape is similar but the ordering matters:

1. Quit the app.
2. Download the target version .dmg (Apple Silicon or Intel) from antigravity.google/releases.
3. Move /Applications/Antigravity.app to the Trash.
4. Install the older .dmg.
5. Set Update Mode to none before launching — otherwise it auto-updates back to latest on the next launch.

If you hit auth errors on macOS after this, deleting ~/Library/Application Support/Antigravity/Session Storage and Local Storage has been suggested as a fix.

Disabling auto-update is the step people forget. Do it via Settings > Application > Update Mode (set to manual for notify-only, or none for no checks), or add "update.mode": "none" to settings.json. After a downgrade this is mandatory — skip it and the app silently re-updates.

The catch with pinning: "no longer supported"

There's a separate error you need to know about before you commit to a pinned old version:

This version of Antigravity is no longer supported. Please update to receive the latest features!

That is a server-enforced hard deprecation. Google enforces a minimum client version, and when your client falls below it the Gemini backend simply refuses the connection. The fixes are to update the client, log out and re-authenticate (old tokens become invalid after major updates), clear browser cache/cookies (auth runs through the browser), or do a clean reinstall.

Here's the tension: downgrading to escape 2.0 can later trigger this exact lockout once Google raises the server-side minimum. So a pinned old version buys you time, not permanence. If your workflow depends on staying on 1.23.2 forever, plan for the day the backend stops accepting it.

Fixing the smaller errors

• "Agent terminated due to error" / "selected model is not supported": these surfaced as launch-stability issues in the reorganized 2.0. Re-authenticating and keeping the client updated is the practical first move; if a specific model errors, switch models and retry.
• Login breaks after update (macOS): clear Session Storage and Local Storage under ~/Library/Application Support/Antigravity/, then re-authenticate.
• "No longer supported" on an old build: update or re-auth, as above. There's no way around a server-side minimum except meeting it.

What about Claude, the CLI, and pricing?

A few things people keep asking about, with appropriate hedging:

• Claude Code / Anthropic support: some users reported Anthropic model integration was removed or changed in 2.0. This is not confirmed by an official source, so treat it as unverified rather than a known removal.
• Gemini CLI shutdown: Google is asking previous Gemini CLI users to migrate to the new Go-based Antigravity CLI. One rollback guide claims the Gemini CLI stops working entirely after June 18, 2026 with IDE users unaffected — the exact date and scope are unverified, so don't plan around that specific deadline.
• Pricing/quota tiers: I/O 2026 introduced an AI Ultra tier at $100/month (roughly 5x AI Pro limits), and the former $250 top tier was reduced to $200 (roughly 20x Pro limits). The default model in the 2.0 stack is Gemini 3.5 Flash, with Gemini 3 Pro also available; agents plan, write, and run code in isolated Linux environments.

Bottom line

Antigravity 2.0 didn't delete your IDE — it changed which surface the auto-update left in front of you, split your data into a new folder, and shipped enough launch bugs to make it feel like a deletion. Two clean recovery paths exist: stay on 2.0 and reinstall the standalone IDE (then copy your data across folders to dual-wield), or roll back to an older build and immediately set update.mode to none. Just remember that a pinned old version is borrowed time, because the server-side minimum-version check can lock you out later with the "no longer supported" error. If you can stomach the new model, dual-wielding is the supported direction; if you can't, pin deliberately and keep a migration plan in your back pocket.