Google I/O 2026 ran today, May 19th. If you missed the keynote or have been skimming headlines trying to figure out what actually matters for your workflow, you are in the right place.

This is the definitive breakdown of what Google Antigravity 2.0 is, what changed, why those changes matter, and how the developer community is responding. No fluff. No speculation. Just what is real and what you need to know to make informed decisions about whether and how to adopt it.

Let’s get into it.

What Is Google Antigravity (For Anyone Still Getting Up to Speed)

Google Antigravity launched in public preview in November 2025. It positioned itself not as another AI code assistant bolted onto an existing editor, but as an agent-first IDE where autonomous AI agents handle the planning, execution, testing, and verification of your development tasks.

The core idea was a departure from the traditional model. Instead of AI that suggests the next line of code, Antigravity aimed to give you AI that finishes entire features.

That original release built its interface around two views. You have the Editor View, which feels like a stripped-down VS Code (because it is built on a VS Code fork), and the Manager View, which functions as mission control for spawning and overseeing multiple agents working in parallel on distinct tasks. Developers could drop in with Gemini 3 Pro, Gemini 3 Deep Think, Claude Sonnet, or Claude Opus and let the agents loose.

It was genuinely impressive. It was also genuinely rough around the edges. Rate limits bit hard, sessions dropped at the worst moments, and the free tier proved virtually unusable for sustained work. We covered the quota problem in depth in our breakdown of Antigravity’s rate limit crackdown, which means the frustration was real and widespread.

Today’s announcement is the answer to many of those complaints, though it comes with its own set of trade-offs.

If You Just Want the IDE, Here’s Where to Get It

Before getting into everything that’s new, let’s address the immediate question a lot of people are going to have: the original Antigravity IDE (the VS Code-based code editor) is still available and is not going away.

Google has not killed the editor experience. It has repositioned it as one component within a larger suite. If your workflow lives in the IDE and you have no interest in a separate orchestration app, you do not need to change a thing.

Download the Antigravity IDE directly from: antigravity.google

From the download page, select your operating system:

  • Windows: x64 or ARM64 .exe installer
  • macOS: Apple Silicon or Intel .dmg, or via Homebrew (brew install --cask antigravity)
  • Linux: .deb and .rpm packages available

Sign in with your Google Account on first launch. Your extensions, keybindings, and workspace settings carry over from VS Code if you are migrating. The editor continues to be updated, still ships with both Editor View (your familiar coding interface) and Manager View (the multi-agent dashboard), and still supports Gemini 3.5 Flash, Claude Sonnet 4.6, and Claude Opus 4.6.

The rest of this guide covers what is new and different with the 2.0 platform expansion. If you are happy with the IDE as it is, bookmark this and revisit when you are curious about the broader suite.

Antigravity 2.0: The Program Just Became a Platform

The biggest headline from Google I/O 2026 is this: Antigravity is no longer just an IDE. It is a full development platform, and the IDE component is now a separate program within that suite.

That distinction matters, and it creates some immediate confusion worth clearing up right now.

The Old Antigravity vs. the New Antigravity

The original Antigravity was fundamentally an IDE. It sat alongside tools like Cursor or Windsurf as a code editor with unusually powerful AI integration. If you used it, you launched it, coded in it, ran your terminals in it, and left.

Antigravity 2.0 reframes everything. The platform now includes:

  • Antigravity (the Desktop App): A new standalone application purpose-built for agent orchestration that is not primarily a code editor
  • Antigravity IDE: The VS Code-based editor environment, still available and maintained, but now a component within the broader suite rather than the product itself
  • Antigravity CLI: A command-line interface for developers who prefer terminal-based workflows
  • Antigravity SDK: Programmatic access to the same agent harness Google uses internally

If you have been using the editor and you see references to “Antigravity 2.0,” you are not losing your IDE. But the product is bigger now, and the IDE is no longer the centerpiece.

How to Get the New Standalone App

The new Antigravity desktop application is available now at antigravity.google.

Windows users: Download the .exe installer for x64 or ARM64, run it, and follow the prompts. Sign in with your Google Account on first launch to activate AI features.

macOS users: Grab the .dmg for Apple Silicon or Intel. Drag to Applications. Alternatively, power users can install via Homebrew:

brew tap google/antigravity
brew install --cask antigravity

The new app requires a Google Account. Your existing workspace context, settings, and any configured integrations will carry over if you were already using the previous version.

The New Features, One by One

1. Gemini 3.5 Flash: The Engine Under the Hood

The model powering Antigravity 2.0 is Gemini 3.5 Flash, announced alongside the platform at I/O. Google’s benchmarks put it at 12x faster than comparable frontier models for agentic tasks, with output speeds around 289 tokens per second.

Here is what this means for your daily coding workflow:

  • Agents that previously stalled for 20–30 seconds between steps are completing those same steps in under three seconds
  • Multi-step workflows that required you to sit and watch are now running fast enough to context-switch away and come back to results
  • The speed improvement compounds across parallel agents, which is where the gains are most noticeable

Gemini 3.5 Flash also outperforms Gemini 3.1 Pro on coding-specific benchmarks. If the previous model felt like it occasionally needed to think too hard about things that should have been straightforward, this is the fix.

The multi-model setup is still intact. Claude Sonnet 4.6, Claude Opus 4.6, and an open-source GPT variant remain available. Gemini 3.5 Flash is now the recommended default, but you can still switch models per conversation.

2. Dynamic Subagents: Parallelization Without the Manual Overhead

The original Manager View let you manually spawn agents for different tasks. You picked the task, assigned the agent, and managed the queue yourself.

Antigravity 2.0 introduces dynamic subagents, where your primary agent can spin off specialized subagents on its own, without you explicitly directing it.

Here is how this works in practice: you hand the main agent a complex task, like “refactor our auth module, update the corresponding tests, and document the API changes.” Under the old model, you would likely be running three separate agents in Manager View and coordinating their outputs yourself. Under the new model, the primary agent breaks that task into components, spawns subagents for the test update and documentation pieces, and those subagents run asynchronously in isolated contexts.

The main conversation thread does not stall while subagents work. You get notified when they complete, and their outputs come back into your primary thread as structured results.

The isolation is important. Subagents do not share state with each other or clutter your main thread with debug logs and intermediate steps. This addresses one of the most common complaints from Antigravity’s early heavy users: complex tasks generated so much agent chatter that the conversation thread became hard to follow.

3. Scheduled Tasks: Cron for Your Agents

This update is underrated in the coverage I have seen so far.

Antigravity 2.0 introduces a scheduled task layer that gives agents cron-like functionality. You can now configure agents to run on a timer, either once at a future point or on a recurring schedule, without you being in the session at all.

Here are a few ways to put this to work:

  • Run a nightly test suite and have the agent file a summary report when you open the app in the morning
  • Schedule a weekly dependency audit that checks for outdated packages and flags security vulnerabilities
  • Set up a recurring code quality scan that runs every Monday before the team’s standup

This is not just a novelty. For anyone using Antigravity for development operations beyond pure feature work, scheduled agents close the gap between what the platform can do and what a properly configured CI/CD pipeline provides. You are no longer limited to synchronous, session-bound work.

4. New Slash Commands: Sharper Control Over Agent Behavior

The slash command system has been expanded. These are not gimmicks; they change how you interact with agents in meaningful ways.

/goal Tells the agent to run to completion without stopping for intermediate check-ins. If you have a well-scoped task and you trust the agent’s judgment, /goal removes the back-and-forth. The agent executes until done or until it hits something it cannot resolve, at which point it surfaces the blocker clearly. Best for tasks where you are comfortable reviewing output at the end rather than inline.

/grill-me Inverts the dynamic. Instead of you asking the agent questions, the agent asks you clarifying questions before starting execution. If your requirements are ambiguous and you know it, this is the command that forces the agent to surface those ambiguities before they cause problems. Think of it as the agent doing scoping work that you would otherwise skip.

/schedule Surfaces the scheduled task interface directly from the conversation. You can define a recurring job or a one-time future execution inline without navigating to a separate scheduling view.

/browser This command comes with a policy shift. In the original Antigravity, agents could independently decide to open a browser and interact with web content. Google has moved away from that autonomous browser access model. The /browser command is now an explicit toggle. Agents only use browser primitives when you say so. This is a deliberate choice to give developers more control over what their agents are doing, which is important for anyone working with production environments where unexpected external requests could cause problems.

5. Project-Based Context: Conversations That Span Multiple Folders

The original Antigravity tied conversations to a single repository or workspace. If your work touched multiple codebases, you were managing context manually and hitting limits on what the agent could see.

Antigravity 2.0 introduces project-based context. Conversations are now organized into projects that can span multiple folders and carry their own permission sets. Your project context persists across sessions, so you are not re-establishing what the agent knows about your codebase every time you open the app.

This matters most for:

  • Monorepos with multiple service directories
  • Microservice architectures where a change in one service requires coordinated updates in others
  • Full-stack projects where front-end and back-end live in separate repositories

Projects also support granular permission scoping. You control exactly which files and directories each project can access, which is important if you are using Antigravity in an environment with sensitive data or IP you do not want passing through model context.

6. The Antigravity CLI

The Antigravity CLI replaces the previous Gemini CLI for agentic terminal workflows.

If you were using Gemini CLI and wondering what happens to your existing setup, Google is actively encouraging migration. The Antigravity CLI runs the same underlying agent harness but is purpose-built for the agentic context of Antigravity 2.0 rather than for general Gemini API interaction.

The CLI is aimed at developers who want to invoke agents without a GUI, integrate agentic workflows into existing scripts and build pipelines, or work in headless server environments. You can trigger agent tasks, monitor their execution, and pull results from the terminal.

Early documentation from Google positions this as the right entry point for DevOps engineers integrating Antigravity into automated deployment and review workflows.

7. The Antigravity SDK

The Antigravity SDK is the most developer-facing piece of the new suite for teams who want to go beyond what the built-in agents offer.

The SDK provides programmatic access to the same agent harness Google uses internally, meaning the same infrastructure that powers the autonomous agents inside Antigravity 2.0 itself. You can define custom agent behaviors, build specialized agents tailored to your internal tooling, and host them on your own infrastructure.

What this unlocks for teams:

  • Custom agents that know your internal API conventions without you having to explain them every session
  • Specialized security review agents trained on your compliance requirements
  • Custom agents that interface with internal databases, project management tools, or proprietary build systems

The SDK ships with Model Context Protocol (MCP) support out of the box, which means external tool connections (databases, APIs, internal services) follow a standard integration pattern rather than requiring custom plumbing for each.

8. Ecosystem Integrations

Antigravity 2.0 lands with three primary integration expansions:

Google AI Studio: You can now export projects directly from AI Studio into the local Antigravity app while retaining conversation context. If you prototype in AI Studio and then want to move the project into a proper agentic development environment, there is a native path for that.

Firebase: Direct Firebase integration means agents can manage, test, and deploy Firebase resources from within Antigravity workflows without external tooling.

Android: Google has added what it is calling vibe coding capabilities for Android development, which is an agent-assisted Android development workflow that can scaffold, prototype, and iterate on Android projects using the existing Antigravity agent harness.

What the Community Is Saying

Let’s look at how the community is actually reacting to these updates.

The r/GoogleAntigravityIDE and r/google_antigravity subreddits are active. The announcement threads are long.

The speed improvement from Gemini 3.5 Flash is getting the most immediate positive response. Developers who had written off agentic workflows as too slow to be practical are coming back around. One heavily upvoted comment captured the sentiment: the model latency was the biggest invisible tax on the agentic workflow model, and cutting it by 12x changes the calculus.

The scheduled tasks feature is getting less attention than it deserves. A few automation-focused users caught it and are excited, but it has not broken through to the mainstream discussion yet. Expect that to change as people actually start using it.

The /browser command policy shift (removing autonomous browser access in favor of explicit control) is drawing mixed reactions. Privacy-conscious developers are relieved. Power users who relied on autonomous browser interaction for their testing workflows are frustrated. The frustration is understandable but Google’s reasoning is sound. Agents that can autonomously access external URLs in production environments introduce risks that are hard to manage.

Twitter/X: Debates and Early Takes

Twitter users are actively debating whether Antigravity 2.0 as a standalone app represents a challenge to Cursor and Windsurf’s position in the market.

The general view is that Antigravity’s integration depth with Google’s broader stack (Firebase, AI Studio, Android) gives it an advantage for teams already invested in that ecosystem, while Cursor’s polish and Windsurf’s collaboration model maintain their appeal for teams that are not. The subagent parallelization is also generating sharing: people are immediately thinking through what becomes possible when agents can spawn specialized workers without manual direction.

The Confusion That Needs to Be Addressed

A note on something circulating in developer communities that is causing confusion: earlier in 2026, several open-source “AntiGravity Kit 2.0” projects appeared on GitHub. These are third-party community projects, not official Google releases. They have no affiliation with the Antigravity 2.0 announced at I/O today.

If you are looking at GitHub repositories claiming to be “Antigravity Kit 2.0” or similar names, those are community experiments. The official platform lives exclusively at antigravity.google. Do not download Antigravity from third-party mirrors or file-sharing sites.

What Changed If You Were Already Using Antigravity

Here is the practical summary for existing users:

Your editor environment is not going away. The IDE component is still there and still maintained. You do not need to abandon your current workflow immediately.

Your model access changes. Gemini 3.5 Flash is now the primary model. Claude Sonnet 4.6 and Claude Opus 4.6 replace the previous 4.5 versions. Quotas for the new model tier are reset at launch, so if you were hitting limits regularly before, now is the time to re-evaluate whether the platform works for your use case.

Your conversation history does not carry into the new project-based context system automatically. You will need to set up your projects manually in the new app. This is a one-time migration effort, not an ongoing cost.

The Gemini CLI is being deprecated in favor of the Antigravity CLI. If you have automation built around Gemini CLI commands, start planning your migration now. Google has not announced a hard end-of-life date yet, but the messaging is clear: new development is moving to the Antigravity CLI.

The Honest Assessment

Antigravity 2.0 is a step forward. The Gemini 3.5 Flash speed improvement alone addresses the most fundamental UX problem with the original release. Dynamic subagents, scheduled tasks, and the expanded slash commands address the feedback Google has been collecting from developers who pushed the platform hard.

By separating the desktop app, the CLI, and the SDK, Google is signaling that it thinks about Antigravity as a long-term infrastructure investment rather than an experimental IDE. That matters for enterprises and teams evaluating whether to build internal workflows on top of it.

The big remaining question is quota management. The rate limit problems we documented before have not been solved yet. They have been improved by a faster model that consumes credits differently, but the underlying infrastructure constraints have not evaporated. If you were hitting walls regularly before, test your workflows before committing. The experience will be better, but whether it will be good enough for your use case depends on your consumption patterns.

Today’s announcement moved Antigravity from promising experiment to serious contender. The gap between what Cursor, Windsurf, and Antigravity offer has narrowed. For teams already in the Google ecosystem, the integration depth now tips the scales.

If you have not tried Antigravity since the early chaotic days of the preview, the Gemini 3.5 Flash launch is the right reason to go back and re-evaluate.

Resources and Next Steps

Last updated: May 19, 2026 — the day of the Google I/O 2026 Antigravity 2.0 announcement.