Google Antigravity 2.0: What Changed in the Agentic IDE

Google Antigravity has become one of the most searched terms by developers in recent hours — and for good reason. At Google I/O 2026, the company transformed what started as an agentic IDE into a full-fledged AI-powered development platform. In this guide, I explain what Google Antigravity 2.0 is, what changed from the first version, and why it affects those who write code every day.

TL;DR — what you need to know

• Google Antigravity is no longer just an IDE: Antigravity 2.0, announced at Google I/O 2026 on May 19, has become a platform with five usage surfaces.
• The surfaces are the desktop app, Antigravity CLI, SDK, Managed Agents in the Gemini API, and the Enterprise Agent Platform.
• The default model is now Gemini 3.5 Flash, which — according to Google — surpasses Gemini 3.1 Pro in nearly all benchmarks while running four times faster.
• Gemini CLI will be discontinued on June 18, 2026; users need to migrate to Antigravity CLI before then.
• There is a free tier included in Google AI Pro, and an AI Ultra plan at $100 per month with five times the usage limits.

What is Google Antigravity 2.0

Google Antigravity was born on November 18, 2025, launched alongside the Gemini 3 model. At the time, Google presented it as its first agentic development platform — a term worth unpacking. Agentic describes software that not only suggests code snippets but plans and executes entire tasks on its own: opens files, runs terminal commands, tests in the browser, and checks its own results.

The first version was, in practice, a modified fork of Visual Studio Code, available for Windows, macOS, and Linux. What set Google Antigravity apart from a regular editor was the core idea: agents gained their own surface, the Agent Manager, with direct access to the editor, terminal, and an embedded browser. Instead of typing each line, the agent received a task, built a plan, and returned verifiable artifacts — implementation plans, task lists, walkthroughs, and screenshots showing what it had done.

Antigravity 2.0, announced at Google I/O 2026, takes the next step. It is no longer a simple IDE but becomes a standalone desktop application built entirely around agent orchestration. The IDE still exists within it, but has become just one piece of a larger ecosystem. This change in scope explains the spike in searches: many people want to know if they need to switch tools.

From IDE to ecosystem: what changed in version 2.0

If version 1.0 was an editor with embedded agents, version 2.0 is a command center for agents. The difference is not cosmetic. Here is what is new in Google Antigravity:

• Native voice commands. You create and trigger workflows by speaking, without typing — the same feature Google brought to Gmail and Docs.
• Dynamic subagents. A main agent splits a complex task into a tree of specialized subagents that run in parallel. Instead of a queue, you have multiple simultaneous workers.
• Scheduled tasks. You can schedule agents that run in the background — a nightly test battery or a scan for outdated dependencies.
• Ecosystem integrations. Antigravity 2.0 natively integrates with Google AI Studio, Android, and Firebase.

The Agent Manager has also matured. It allows you to observe and coordinate multiple agents asynchronously, tracking each one's progress without blocking your own work. In practice, the developer shifts from writing every line to reviewing and coordinating. It is a habit change as profound as switching programming languages.

This asynchronous model is what confuses those coming from a traditional editor. You don't wait idly for the agent to finish before doing something else. You launch three or four tasks, monitor them via the Agent Manager, and review each as it completes. Dynamic subagents take this further: instead of manually breaking down a large problem, the main agent decides how to divide the work and how many subagents to create. It works well when the task has independent parts; it stalls when everything depends on everything else.

The five surfaces of Google Antigravity 2.0

The biggest structural change is that Antigravity has become a platform with five usage modes. Each caters to a different developer profile:

Surface	Purpose	Best for
Desktop app	Orchestrate agents with full graphical interface	Daily individual use
Antigravity CLI	Create and run agents via terminal, no GUI	Automation, scripts, and CI/CD
Antigravity SDK	Program agent behaviors and host them anywhere	Teams wanting custom agents
Managed Agents (Gemini API)	Trigger agents with a single API call	Products embedding agents
Enterprise Agent Platform	Connect agents to Google Cloud projects	Companies with corporate governance

The SDK is perhaps the most strategic. It exposes the same agent mechanism that Google uses internally in its own products, optimized for Gemini models. Managed Agents run inside an isolated Linux environment and accept agent definitions written in markdown files — making behavior auditable and versionable like any other code.

Another detail worth highlighting about Managed Agents: each agent maintains state between sessions. Files, installed dependencies, and conversation context persist from one day to the next. You can pause a long task today and resume it tomorrow without the agent losing the thread. For something like migrating an entire project, this persistence makes a real difference.

The Enterprise Agent Platform rounds out the offering for corporate audiences. It connects agents to Google Cloud projects, enabling access policies, auditing, and centralized billing — requirements any mid-sized company demands before unleashing generative AI on engineering teams. For solo developers or small teams, the desktop app and CLI handle almost everything.

Antigravity CLI: the mandatory migration from Gemini CLI

Here is the part with a deadline. Alongside Google Antigravity 2.0, Google announced that Gemini CLI and the Gemini Code Assist IDE extensions will be discontinued. The key dates:

1. May 19, 2026 — Antigravity CLI becomes available to all users.
2. June 18, 2026 — Gemini CLI and Gemini Code Assist extensions stop serving requests on Google AI Pro, Ultra, and free plans.

Those with corporate Standard or Enterprise licenses for Gemini Code Assist are not affected for now. For all individual plans, however, migration is not optional — it is just a matter of doing it before or after the old tool stops responding.

The good news is that Antigravity CLI preserves what mattered in Gemini CLI. Agent Skills, Hooks, Subagents, and Extensions — the latter renamed to Antigravity plugins — continue to work. The common pitfall is leaving everything until June 17: if you use Gemini CLI in CI pipelines, test the migration early, because any incompatibility will break your production build at the worst possible time.

In practice, migration has three steps: install Antigravity CLI, run the import command that brings your Gemini CLI settings, and review the extensions that became plugins. The official guide published by Google covers each case, including GitHub integration, which will stop accepting new installations after June 18.

Gemini 3.5 Flash: the models behind Google Antigravity

Google Antigravity 2.0 ships with a new default model: Gemini 3.5 Flash. According to Google, it surpasses Gemini 3.1 Pro — the previous generation's most advanced model — in nearly all benchmarks while running four times faster. For an agentic workflow, speed is not a luxury: an agent making dozens of sequential calls feels every millisecond saved.

But Antigravity is not tied to Gemini. The platform also runs Gemini 3 Pro, Claude Sonnet 4.5 from Anthropic, and open models from OpenAI's GPT-OSS line. There is an important technical detail: Gemini models receive exclusive optimizations — prompt caching and tool call optimization — that third-party models do not benefit from. In other words, you can use Claude or GPT, but Gemini tends to be faster and cheaper within Antigravity.

Why this affects your budget

In agentic workflows, token consumption skyrockets. Every generated plan, every file reread, and every correction attempt costs. Choosing the right model for each task — Flash for volume, Pro for hard reasoning — is no longer a detail but a budget decision. Those who ignore this often discover the cost only when the bill arrives at the end of the month.

How much does Google Antigravity cost: plans and pricing

Google Antigravity 2.0 maintains an accessible entry level, but all prices are in dollars. What is confirmed so far:

Plan	Price	Usage limits
Pro	Included in Google AI Pro	Entry-level limits
AI Ultra	$100/month	5× Pro plan limits
Higher Ultra tier	$200/month	20× Pro plan limits

The AI Ultra plan at $100 is the most talked-about new feature — it is the sweet spot for heavy agent users without justifying the most expensive tier. This higher tier at $200 monthly was actually reduced from a previous price of $250. As a launch promotion, Google offered $100 in Antigravity credits for accounts activated by May 25, 2026.

Converting roughly for Brazilian developers, AI Ultra falls in the range of R$550 to R$600 per month, depending on exchange rates and international service taxes. This is not trivial — so it is worth measuring consumption on the free tier before upgrading.

Is Google Antigravity worth it? When to use and when to wait

Not every Google I/O novelty needs to enter your workflow tomorrow. Antigravity 2.0 shines in some scenarios and still requires caution in others.

Worth it when:

• You need to prototype quickly and final quality can be refined later.
• The task is repetitive and well-defined: mass refactoring, dependency updates, writing tests.
• Parallelization is possible — multiple subagents handling independent parts of the code.
• You are exploring an unfamiliar codebase and want a map before diving in.

Think twice when:

• The CLI is still in preview quality on Linux; in production, validate thoroughly before relying on it.
• The task requires subtle architectural decisions — the agent executes well but does not replace engineering judgment.
• You don't have time to review the output. Unverified agentic code is technical debt disguised as productivity.

A note on expectations: part of the technical community sees Google Antigravity less as a competitor capable of retiring Cursor and more as Google's bet to keep developers within the Gemini ecosystem. The verification artifacts — plans, walkthroughs, and screenshots — exist precisely for you to check the agent's work. Use them. Ignoring them throws away the tool's biggest advantage.

In my experience, the most expensive mistake is not the tool generating bad code — it is the developer accepting good code without understanding why it works. When something breaks three months later, no one on the team can explain the original decision. Treat the agent like a very fast junior colleague: great for acceleration, dangerous without careful review. This mindset applies to Antigravity and any competitor.

What Google Antigravity changes for developers in Brazil

My take, after more than fifteen years building software, is that agentic tools like Google Antigravity change the mechanical part of the work, not the hard part. They accelerate the kind of custom development we deliver daily — from customized Moodle apps to system integrations — but they don't decide what should be built, or why.

An agent can scaffold a screen in minutes. It doesn't tell you, however, whether the end user actually needs that screen. Decisions like choosing between the official Moodle app and a custom app remain human judgment, informed by business context that no AI model has.

If you code, the advice is straightforward: install Antigravity 2.0, spend a few hours on the free tier, and form your own opinion before June 18 — the date Gemini CLI goes away. And if your company is evaluating how generative AI fits into the product roadmap, this is a good time to talk to those who are already hands-on. The technology has leveled up; what hasn't changed is the need for someone with judgment at the helm.