Google spent years telling developers that the IDE was the right place to put AI assistance. At I/O 2026, it changed that answer. The IDE is now just one surface. The agent harness is the product.

The Problem It's Solving

The original Antigravity - released alongside Gemini 3 in November 2025 - was essentially an AI-native IDE. Useful, but still IDE-shaped: reactive, session-based, closed when you closed your laptop. It made the model smarter inside the editor without rethinking what a developer tool is actually for.

Google is moving its developer tooling away from IDE-centric assistance and toward multi-agent workflow management as the primary abstraction. That's a genuine architectural shift. The question it forces is: if an agent can plan, execute, and iterate across tools in the background without you watching, why should the editor be the center of gravity at all?

Antigravity 2.0 is Google's answer to that question - and the answer is that it shouldn't.

How Antigravity 2.0 Actually Works

Google Antigravity is built around a single agent harness exposed through four surfaces: Antigravity 2.0 (the agent-first desktop application), the Antigravity CLI (a terminal interface rebuilt in Go, successor to Gemini CLI), the Antigravity SDK (programmatic access to the harness for building custom agents), and the Antigravity IDE (the original Antigravity from December 2025). Because all four share the same harness, improvements to agent behavior land across every surface at once.

That shared-harness architecture is the key decision here. It means Google isn't shipping four separate products with four separate codebases - it's shipping one execution layer with four access patterns. A fix to how agents handle context, retries, or tool calls propagates everywhere simultaneously.

The desktop application itself is built around parallel agent orchestration. It acts as a base for agent interaction, allowing developers to orchestrate multiple agents and execute tasks in parallel, with dynamic subagents for parallelized workflows, scheduled tasks for background automation, and ecosystem integrations across Google AI Studio, Android, and Firebase.

The scheduled tasks piece is the one most developers will underestimate initially. Rather than manually prompting an agent each time, developers can define tasks that invoke agents automatically in the background - converting the agent from a single-turn tool into something closer to a persistent automation pipeline. That's the conceptual leap from assistant to infrastructure.

On the CLI side: Antigravity CLI preserves the most critical features of Gemini CLI - Agent Skills, Hooks, Subagents, and Extensions - the last of which are now rebranded as Antigravity plugins. And migration isn't optional: on June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro and Ultra, as well as those using it free of charge. If you're still on Gemini CLI, the clock is running.

What Developers Are Actually Using It For

The five surfaces together form a stack that covers meaningfully different deployment shapes. The desktop app handles human-in-the-loop orchestration - you watch agents work, intervene when needed, route tasks across parallel subagents. The CLI handles automation and CI: a terminal binary that runs the same agent harness as the desktop app, without the GUI, designed for power users, automation, and CI pipelines, and different from Claude Code in that it supports dynamic subagents natively.

The most developer-significant addition is Managed Agents in the Gemini API. With a single API call, a developer can spin up an agent that reasons, calls tools, and executes code inside an isolated Linux environment. Sessions are stateful and resumable - files and context persist across turns - so developers don't have to write their own context management plumbing. The pricing model matches the execution model: pay-per-run rather than per-token.

The SDK closes the loop for regulated environments. The SDK gives programmatic control over the harness, which means a development organization can deploy the agent loop on its own infrastructure rather than depending on Google's hosted runtime. That matters for regulated industries, data-residency constraints, or anyone who simply does not want the agent's execution context sitting on a vendor-managed sandbox.

On model support: Antigravity runs Gemini 3 Pro and Gemini 3.5 Flash by default, plus Anthropic's Claude Sonnet 4.5 and OpenAI's GPT-OSS. The platform is optimized for Gemini, which means lower cost and lower latency on Google's model family.

Why This Is a Bigger Deal Than It Looks

The immediate story is that Google shipped a better dev tool. The actual story is that Google externalized its internal agent infrastructure.

Antigravity 2.0 and Managed Agents represent Google's clearest public statement yet about how it plans to make Gemini the default layer underneath products it didn't build itself. When the same harness that runs Gemini Spark's background task execution is the same harness you call from the SDK, you're not integrating with a developer tool - you're plugging into the same plumbing that powers Google's consumer products. That's a different kind of lock-in than an SDK. It's platform gravity.

For teams building on MCP: the Antigravity stack is explicitly MCP-compatible. The Skills and plugin system in the CLI are the same mechanism Spark uses to connect to Canva, OpenTable, and other external services. That means custom MCP servers you build today will integrate into Antigravity's orchestration layer as Antigravity's third-party ecosystem grows.

The Gemini CLI deprecation is also worth reading carefully. Listening to developer feedback made one thing clear: Google can serve developers best by pouring energy into a single product built for today's multi-agent reality. That's not just a product consolidation announcement - it's a commitment that multi-agent orchestration, not individual model completions, is the interface developers are expected to build on going forward.

Availability and Access

Antigravity 2.0 is available now. The base Pro tier is included with existing Google AI Pro subscriptions. The Ultra plan is $100 per month with 5x Pro limits. Ultra Premium is $200 per month (reduced from $250) with 20x limits. The Antigravity CLI is available to everyone starting today. Gemini CLI and Gemini Code Assist IDE extensions sunset on June 18, 2026. The Antigravity SDK and Managed Agents in the Gemini API are available through the standard Gemini API access tiers.

The IDE isn't dead - it's just been demoted from center to surface. The harness is the product now, and everything else is a way to reach it. That's the architectural bet Google made at I/O 2026, and it's the most consequential shift in how the company thinks about developer tooling since it open-sourced Kubernetes.

Follow for more coverage on MCP, agentic AI, and AI infrastructure.