It's been two days since Google I/O 2026. I was rewatching the keynote and got curious — is Antigravity already installed on my machine?
$ defaults read /Applications/Antigravity.app/Contents/Info.plist CFBundleShortVersionString
1.23.2
It was. Version 1.23.2. So I opened it up. This post is what I found.
What Is Antigravity 2.0 — The Short Version
Announced at Google I/O 2026, Antigravity 2.0 is an "agent-first development platform." It bundles a desktop IDE, a CLI (agy), an SDK, a Managed Agents API tier, and an enterprise deployment path through the Gemini Enterprise Agent Platform into a single product family.
Where the original Antigravity was essentially a Cursor clone with Gemini under the hood, version 2.0 aims to integrate multi-agent orchestration at the platform level.
And Gemini CLI is shutting down on June 18, 2026. AI Pro, AI Ultra, and free-tier users all get the same message. Google is forcing a migration from open source to closed software with a usage cap and a hard deadline.
Three Things That Actually Matter
I almost wrote this off as "another Cursor clone with a new skin." Three things changed my mind.
Gemini CLI retirement: Gemini CLI was open source. Tens of thousands of developers contributed to it, forked it, built on it. Replacing it with a closed product is a strategic signal — Google is moving developer tooling into its monetization stack.
GEMINI.md and .agents/ directory: If you've used Claude Code, you know CLAUDE.md and .claude/agents/. Antigravity uses the same pattern. Agent definition files live in the project directory and behave like a build system. This convention is converging across platforms.
Gemini 3.5 Flash pricing: $1.50/MTok input, $9.00/MTok output. 1M token context. This price table determines whether Antigravity is actually cost-competitive.
What I Found Inside the App
Antigravity is an Electron app built on VS Code 1.107.
$ cat /Applications/Antigravity.app/Contents/Resources/app/product.json
# version: 1.107.0
# nameShort: Antigravity
The extension list:
/extensions/antigravity/ ← Core agent extension (v0.2.0)
/extensions/antigravity-code-executor/ ← Executes code generated by Cascade
/extensions/antigravity-dev-containers/ ← Remote container support
/extensions/antigravity-remote-openssh/ ← SSH remote work
The jsonValidation entry in package.json was the most interesting thing I found:
{
"fileMatch": "**/mcp_config.json",
"url": "./schemas/mcp_config.schema.json"
}
MCP config schema baked in. Antigravity natively supports the MCP ecosystem for agent tool extensions.
The command list also had notable entries:
antigravity.importCursorSettings
antigravity.importWindsurfSettings
antigravity.importVSCodeSettings
antigravity.importCiderSettings
Four competitor products' settings can be imported out of the box. "Remove migration friction" is the obvious intent — and it works. Anyone who's spent an afternoon re-configuring keybindings after switching IDEs will appreciate this.
The Cascade panel (cascade-panel.html) is the agent interface. The antigravity-code-executor extension runs the code Cascade generates.
The agy CLI is not yet publicly available. npm install -g @google/antigravity returns a 404. Homebrew Cask installs the desktop app only. I'm switching to Source Review for the feature analysis below.
Antigravity 2.0 Features — Based on Docs and Official Examples
Multi-Agent Parallel Execution
A lead agent takes a high-level goal and delegates to specialist subagents running in parallel. Each subagent has its own context window, model, prompt, and tool set. Google's public examples describe four subagent types:
- Architect Agent: Structure and design patterns
- Coding Agent: Implementation details
- Testing Agent: Unit and regression tests
- Documentation Agent: Auto-updating technical docs
This is essentially the same pattern as running parallel agents with Claude Code using Git worktrees. The difference is that Google wraps it in a GUI where you can watch the agents work side-by-side.
GEMINI.md and the .agents/ Directory
GEMINI.md at the project root gives all agents shared context. .agents/agents.md defines subagent behaviors. .agents/skills.md declares reusable capabilities across agents.
If you've been following multi-agent orchestration routing patterns, these conventions are familiar. The industry appears to be converging on this file-based agent configuration model regardless of which platform you're on.
The agy CLI — Announced, Not Yet Deployed
Google announced agy as the replacement for Gemini CLI. Theoretically you'll be able to type agy new-agent at a terminal and spin up an Antigravity agent from the command line. Agent Skills, Hooks, Subagents, and Extensions from Gemini CLI are all supposed to carry over.
The problem: as of May 21, 2026, agy doesn't exist on any public package manager. The Register's headline put it plainly: "Bye-bye, Gemini CLI; Google nudges devs toward Antigravity." The feature replacement isn't ready, but the shutdown date is set.
Gemini 3.5 Flash API — Price Analysis
The engine powering Antigravity 2.0 is Gemini 3.5 Flash, which went generally available on May 19, 2026.
| Metric | Value |
|---|---|
| Input price | $1.50 / 1M tokens |
| Output price | $9.00 / 1M tokens |
| Context window | 1,048,576 tokens (~786K words) |
| Max output | 65,536 tokens |
| Speed | ~4x faster than comparable frontier models |
Compare that to Claude Opus 4.7 at $15/$75 per MTok — that's 10x cheaper on input. The model capability gap is real, but Gemini 3.5 Flash outperforms Gemini 3.1 Pro on five separate benchmarks: Terminal-Bench 2.1 (76.2%), GDPval-AA (1656 Elo), and MCP Atlas (83.6%).
For coding agents that make many small calls — writing tests, fixing linting errors, generating boilerplate — Gemini 3.5 Flash's price point starts to look compelling. This is where I think Antigravity's actual competitive advantage sits.
GEMINI.md vs CLAUDE.md — Same Pattern, Different Ecosystem
I use Claude Code daily. The CLAUDE.md / .claude/agents/ / .claude/skills/ structure is my normal workflow. Antigravity's GEMINI.md / .agents/ / skills.md is structurally identical.
The execution model differs:
Claude Code: Terminal-first CLI. No GUI. Compose agents through code and prompts. High transparency — you can read exactly what each agent is doing.
Antigravity: GUI-first IDE. Parallel agents are visualized in the interface. Better for onboarding non-terminal users; worse for power users who want fine-grained control.
MCP support: Both platforms support MCP, but Antigravity bakes the schema validation in at the extension level. From what I saw in the file structure, it's more first-class than in Claude Code.
Cascade by Another Name — Not a Coincidence
Antigravity's agent panel is called Cascade. Windsurf's is also called Cascade. I confirmed this in the official docs of both products.
Windsurf (originally Codeium) built its market position on Cascade — agentic coding differentiated from Cursor's autocomplete-focused approach. Antigravity using the same name is a direct signal that Google is targeting Windsurf's user base. The antigravity.importWindsurfSettings command in the built-in list confirms the intent.
When I compared Cursor, Claude Code, and Windsurf, I wrote about a three-way competition. That analysis needs updating now. The IDE war just added a fourth serious player backed by Google infrastructure and Gemini model pricing.
Enterprise Users Get a Pass
One important carve-out: the Gemini CLI shutdown does not apply to organizations with Gemini Code Assist Standard or Enterprise licenses. Google Cloud's Gemini Code Assist for GitHub is similarly unaffected.
This matters because it tells you where Google's priorities are. Enterprise contract revenue is protected. The migration pressure falls on individual developers, small teams, and startups — exactly the population that built Gemini CLI's open-source community.
I find this more troubling than the technical decisions. Open source tooling thrives when the community of builders trusts the platform. Once that trust is broken by a forced migration, it doesn't come back easily.
My Take: This Is Progress, With Real Caveats
Antigravity 2.0 is a serious product in a way that the original wasn't. Multi-agent orchestration baked into the IDE, a competitive model with strong pricing, and MCP-native tooling are the right moves.
The execution is the problem. Deprecating Gemini CLI without a ready replacement. Usage caps on a product replacing an unlimited open-source tool. A hard June 18 deadline before the CLI ships. This is a go-to-market decision that prioritizes conversion metrics over developer trust.
My plan: I'm not switching from Claude Code as my primary environment. But I'm going to start using Gemini 3.5 Flash API for cost-sensitive pipelines immediately — $1.50/MTok input is hard to argue with for high-volume, lower-stakes tasks. Antigravity 2.0 itself gets a proper evaluation once agy ships and the usage policy stabilizes.
Google entering the agent IDE market seriously is ultimately good for developers. Competition between Claude Code, Cursor, Windsurf, and now Antigravity means all four will keep improving. But the way you enter matters. The open-source reversal is a mistake that will take time to forgive, even if the product turns out to be excellent.
Executability Assessment (Source Review Lane):
- Antigravity 2.0 desktop app: Installed (v1.23.2), internal structure directly analyzed
-
agyCLI: Not yet publicly distributed as of 2026-05-21 - Gemini 3.5 Flash API: Official pricing ($1.50/$9.00 per MTok) confirmed via Google DeepMind
- Multi-agent features: Based on official announcements and Google Codelabs; not directly executed
Sources:
Top comments (0)