Bring Antigravity Multi-Agent AI into Your IDE - Official Extensions Now Available

Google's Antigravity team has been building what they describe as an agent-first development platform since the original launch. The standalone Antigravity 2.0 app handles multi-agent coordination, end-to-end task orchestration, and multi-root workspace management. That part works well for high-level orchestration tasks, but developers who work in VS Code, JetBrains, or Zed all day have had to leave their editors to use it — for many teams, it's enough friction to just not bother. Antigravity has released official extensions for Visual Studio Code, Visual Studio, JetBrains, and Zed, bringing the platform's multi-agent capabilities directly into the environments where most developers spend the majority of their working hours.

The Thinking Behind This

The Antigravity team acknowledges that as AI models get more capable, software development will increasingly take place inside agent-first surfaces like Antigravity 2.0 or the CLI, but that there are still moments when a developer needs to drill down into implementation details, inspect specific lines of code, or step through complex logic with an interactive debugger inside an IDE. That's a much more grounded position than the usual "AI will replace everything" framing. The standalone app is good at orchestrating agents across large tasks. The IDE is good at precision — reading compiler diagnostics, making a localised edit, chasing down a weird bug in a specific function. These are not competing use cases; they're different moments in the same workflow.

Rather than turning traditional editors into heavy multi-agent hubs, the team built lightweight, high-performance integrations that give developers access to conversations, customisations, and multi-agent orchestration that shares context with the rest of the Antigravity ecosystem.

Shared context across surfaces is the part that matters most here. Agents working in the standalone app and the work happening in the IDE can now reference the same project state, which means less duplicated effort and fewer "wait, what changed?" moments when switching between the two.

How to Install on Each Editor

Installation is intentionally kept simple across all four supported environments, which is the right call. Complex setup is a real reason developers skip AI tooling even when they're curious about it.

For Visual Studio Code, the extension is available in the VS Code Marketplace — search for "Google Antigravity," install it, and sign in via the Antigravity icon in the Activity Bar.

Visual Studio users can find it through Extensions > Manage Extensions inside the IDE or through the Visual Studio Marketplace directly.

JetBrains support covers the full suite of IntelliJ-based IDEs — IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider, and more — starting from version 2026.2.1 with one-click installation inside the IDE. Enterprise support for JetBrains is currently in Preview.

Zed gets one-click install directly inside the editor, with Enterprise support also listed as Preview.

Full documentation with setup instructions, keyboard shortcuts, and configuration options is available on the official Antigravity docs page.

Individual vs. Enterprise - What's Different

Individual developers can sign in with any Google account on any Antigravity plan, including the free tier. That's a reasonable on-ramp for someone who wants to evaluate it before committing to anything.

The enterprise side is where the security specifics come in, and these details matter for teams working in regulated environments. Enterprise sessions run under the Google Cloud Terms of Service — data is never used to train foundation models, and all interactions respect the organisation's IAM policies and VPC Service Controls. For teams that have already cleared Google Cloud through their procurement process, this integration path is comparatively straightforward to approve.

Worth Watching

When Antigravity launched, the stated goal was to prove what software development looks like when built from the ground up around autonomous agents. These IDE extensions are a practical step in that direction — not by replacing the editor, but by making the agent layer available inside it without extra context-switching overhead. Whether the extensions hold up well in day-to-day use, especially in large codebases where context window management gets messy, is something developers will have to test for themselves. The positioning is sensible. The execution is worth watching closely over the next few months as the Preview features (particularly for JetBrains and Zed Enterprise) move toward general availability.