Antigravity 2.0 Dropped the IDE — And Most Developers Aren't Happy

An update many expected — but few wanted like this

On May 19, 2026, Antigravity pushed version 2.0. The update had been anticipated for weeks, with the community expecting improvements to the IDE experience — better AI models, faster performance, more stability. What landed instead was a complete rethink of the product.

The terminal is gone. The file tree is gone. The extension system is gone. Direct code editing inside the tool is gone.

Within hours of the rollout, the r/google_antigravity subreddit was flooded with posts from users reporting crashes on startup, broken workflows, and general disbelief at the scope of the changes. Over 300 comments in the announcement thread alone paint a picture of a community that feels blindsided — not by an update, but by a product pivot.

What Antigravity 2.0 actually is

The new model is what Google calls “agent-first.” You type an instruction in natural language. The AI interprets it, creates or modifies files, runs commands in a sandboxed environment, and presents you with the result. You approve, reject, or iterate.

If this sounds familiar, it should. OpenAI launched Codex with essentially the same architecture — a sandboxed coding agent that operates autonomously while the developer observes. The user provides intent; the machine provides execution. No file explorer. No terminal. No ability to Ctrl+click into a function definition and trace the logic manually.

The comparison is hard to avoid. For developers who had been using Antigravity specifically because it was not Codex — because it offered a proper IDE with AI built in — the 2.0 update feels like it moved in exactly the wrong direction.

What was lost

The features that were removed are the baseline of any professional development environment:

Terminal access. Every developer who ships production code relies on a terminal — not a sandboxed simulation, but a real shell with git, npm, docker, and direct process interaction. Without it, Antigravity 2.0 cannot be used for deployment workflows, server debugging, or any task that requires direct shell access.

File explorer. Navigating a project is not just about the file you are editing. It is about scanning directory structure, finding configuration files, and mentally mapping how modules connect. An agent that reads files for you is not a substitute for the spatial awareness a file tree provides.

Extensions. The extension ecosystem is what makes VS Code dominant. Linters, formatters, language servers, git integrations, database viewers — these are not luxuries. They are the infrastructure that turns a text editor into a professional development environment.

Direct code editing. Being able to open a file, read a function, understand its context, and make a targeted 3-character change — this is what coding is. An agent that rewrites blocks of code based on natural language prompts is useful for scaffolding, but it is a fundamentally different activity from precision editing.

The community response

What stands out most about the Antigravity 2.0 launch is the gap between what Google shipped and what developers actually wanted. The community was not asking for a new paradigm. They were asking for a better version of the tool they already had.

The sentiment on Reddit, Discord, and developer forums is remarkably consistent: people liked the IDE. They chose Antigravity over Cursor, over GitHub Copilot, over Windsurf, specifically because Google’s offering felt like a complete IDE with strong AI integration. Taking that away and replacing it with an agent-only interface leaves many users feeling like the product they invested time learning no longer exists.

The biggest concern is not even about today — it is about tomorrow. If the legacy Antigravity IDE installer gets discontinued, developers who downgraded to v1 will eventually be forced to choose between an agent-first tool they do not want or migrating to a competitor entirely.

Where the market stands now

The AI-assisted coding market has split into two clear camps:

Agent-first platforms — like Codex from OpenAI and now Antigravity 2.0 — that remove the developer from the editing loop. You describe; the machine executes.

Augmented IDEs — like Cursor, Windsurf from Codeium, GitHub Copilot in VS Code, and Trae AI from ByteDance — that keep the developer in control while adding AI capabilities on top. Terminal stays. Extensions stay. File explorer stays. The AI suggests; the developer decides.

Claude from Anthropic sits in an interesting middle ground — offering both an agent mode with autonomous tool use and traditional assistant capabilities that integrate into existing workflows rather than replacing them.

The tools winning developer loyalty are the ones that augment existing workflows without destroying them. Cursor in particular has become the default recommendation in many of the Antigravity threads, precisely because it offers deep AI integration inside a real IDE. It is, in many ways, what Antigravity 2.0 could have been.

What this means for teams in production

At Webxtek Studio, this is the kind of toolchain risk we evaluate when advising engineering teams. A tool that changes its interaction model overnight, without backward compatibility, creates real disruption for teams that had standardized on it for web application development.

The lesson is not that Antigravity 2.0 is bad — it may well serve a different audience. The lesson is about dependency. Developer tools are infrastructure. When your infrastructure vendor pivots without notice, your team absorbs the cost. The organizations that weather these transitions best are the ones that maintain flexibility in their toolchains and avoid deep coupling to any single product direction.

Looking ahead

Antigravity 2.0 may find its audience — product managers prototyping without code, entrepreneurs shipping MVPs, designers generating functional components. The “vibe coding” crowd that communicates intent and lets the AI handle implementation may genuinely prefer this model.

But the developers who made the original Antigravity IDE successful are largely still looking for what they had: a proper IDE with strong AI integration. Many are already installing the legacy version, switching to Cursor, or building custom workflows around Copilot. The update that was meant to be the future has, for now, sent a significant part of its community looking elsewhere.

To add to the uncertainty, Google recently announced that on June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions will stop serving requests for all individual users — not just free-tier, but also those paying for Google AI Pro and Ultra. Only organizations with enterprise-level Gemini Code Assist licenses retain access. For individual developers and small teams, this is not a free-tier cleanup — it is a clear signal that Google is repositioning its AI coding tools as enterprise products. The same blog post also references the transition from “Gemini CLI” to “Antigravity CLI,” which, combined with the 2.0 pivot, suggests the legacy IDE’s days are numbered.

Whether Google eventually listens to the community feedback — or fully commits to the agent-first, enterprise-first vision — will determine whether Antigravity remains relevant to the individual developers who built its early community.