Google Antigravity 2.0 launch

The headline framing of Antigravity 2.0 is 'a new desktop app.' The real story is what Google removed. Antigravity 1.0 was a complete development environment, editor, terminal, browser, and agent workspace fused into one product, explicitly positioned as Google's answer to Cursor ^[1]. Antigravity 2.0 strips all of that out. The new desktop has no code editor, no terminal, and no source-control panel by default; it is a mission-control dashboard for orchestrating multiple agents that work simultaneously on a project ^[2].

This is not a UI refresh. It is a thesis. Google is telling its own users that the surface area of coding is shifting from 'write and edit' to 'dispatch and review.' MarkTechPost frames the architecture as 'a standalone desktop application built entirely around agent orchestration' ^[3], and the platform now exposes four distinct surfaces, desktop, CLI, SDK, and the legacy IDE, all sharing a single agent harness on Gemini 3.5 Flash ^[4]. The bet is that orchestration, not editor ergonomics, is where the next decade of developer leverage gets won. If Google is right, the IDE itself is now a legacy artifact for power-users who don't trust the agent loop yet.

Within 24 hours of the I/O keynote, the developer community on the r/google_antigravity subreddit erupted. The top thread asked 'WTF is Antigravity 2.0? Where did my IDE go?' and crossed several hundred upvotes, with its author writing that the update felt like Google 'gutted' a functional IDE into 'a glorified chat wrapper.' A second high-engagement thread titled 'Antigravity 2.0 is a mess. What were they thinking??' echoed the same frustration. Techloy reports developers calling the rollout 'a massive step backward,' with complaints that it 'reeks of non-technical people shipping code to production' ^[5].

The operational damage is concrete: existing Antigravity users were auto-updated mid-workday, losing terminals, source control, and access to their editor; settings, MCP integrations, and extensions silently broke because the new app reads from a different AppData folder. The community-discovered recovery path, uninstall both apps, download the separately-distributed Antigravity IDE, then manually copy the old AppData Antigravity folder into the new Antigravity IDE folder, has had to be pinned in subreddit threads as the de facto fix. The lesson for any platform shipping breaking agent-era pivots: developers will tolerate radical product redefinitions, but only if you ship them as new products, not as an update.

The desktop redesign is what the internet is arguing about. The structurally important release is Managed Agents inside the Gemini API. Per MarkTechPost, a single API call now spins up an agent that 'reasons, uses tools and executes code in an isolated Linux environment' ^[3], with 'persistent isolated environments' where 'each interaction creates an environment that can be resumed in follow-up calls with all files and state intact' ^[3]. That is Google selling, on tap, the same agent harness powering its own products, and it is the part competitors should be reading closely.

Before this, building production agents on top of Gemini required teams to assemble sandboxing, state management, tool brokering, and resumability themselves. With Managed Agents, Google absorbs that infrastructure cost and exposes the agent loop as an API primitive. Pairing it with the Gemini Enterprise Agent Platform, which connects Antigravity 'directly to Google Cloud projects' ^[3], gives Google a vertically integrated stack from research model (Gemini 3.5 Flash) to agent runtime (Managed Agents) to enterprise deployment (Gemini Enterprise) — the kind of stack a single competitor like Cursor or Windsurf cannot match without partnering with a cloud provider.

Buried in Google's transition post is the line that gives away the strategy: Gemini CLI and Gemini Code Assist IDE extensions stop serving AI Pro/Ultra and free-tier requests on June 18, 2026 ^[6]. Gemini CLI shipped less than a year ago. Now Google is retiring it for paying individual developers and routing everyone through the Antigravity CLI, written in Go, sharing the same harness as the desktop, and explicitly preserving Skills, Hooks, Subagents, and Extensions to make the migration tolerable ^[6].

The carve-out is the tell: enterprise customers on Standard/Enterprise licenses keep Gemini CLI access untouched ^[6]. In other words, Google is willing to break the workflow of its individual and Pro-tier developer base to consolidate the agent stack, but unwilling to touch the contracts where customers can actually push back through procurement. That is a much more revealing decision than any keynote slide. It tells you Google has internally accepted that some short-term developer ire is the cost of unification, and it tells competitors where Google sees the durable revenue, not the $20 Pro tier, not the new $100 Ultra tier, but the Gemini Enterprise Agent Platform contracts that the Antigravity stack now funnels into.

TechCrunch's coverage flagged the new $100/month AI Ultra plan offering 5x the Pro plan's Antigravity usage, and noted that Google's top tier dropped from $250 to $200 while keeping 20x Pro limits ^[1]. Headline tier prices are the part the press writes about. The part developers actually feel is the quota redesign underneath them.

Discussion on r/google_antigravity describes quotas being unified across models and surfaces, meaning the same dollar that used to buy you a generous Gemini CLI session now spreads across desktop, CLI, SDK, and IDE usage simultaneously. Multiple Pro users report hitting rate restrictions within a couple of hours of active work, with refresh windows pushed out by a week. The new $100 Ultra tier isn't a luxury upgrade for power users; for any developer doing real multi-agent orchestration, it's effectively the floor. That is a quiet, ~5x effective price increase for serious individual users, executed through quota math rather than a sticker-price hike, and it tightly couples revenue to the new desktop's central design choice: spawning multiple agents in parallel.