Loading page…
The change removes a separate licensing step for eligible customers, but its practical value will depend on whether shared identity, controls and context hold up across mixed developer toolchains.
Listen to this story
Google is turning Antigravity from a separately managed agentic-coding capability into an entitlement within eligible Gemini Enterprise Standard and Plus plans. That gives IT and engineering teams one provisioning and governance path for agents that can inspect codebases, run terminals, operate browsers, and execute multi-step work. Administrators can constrain permissions, budgets, sandboxes, and audit logs, while Google promises enterprise-boundary handling and no training on customer code.
Eligible Gemini Enterprise Standard and Plus customers receive Antigravity without add-on licenses or standalone accounts.
Administrators can manage workspace isolation, browser and MCP permissions, pooled quotas, overages, and centralized logs.
Workforce Identity Federation and Application Default Credentials reduce reliance on manually configured API keys.
Google has added Antigravity to eligible Gemini Enterprise Standard and Plus subscriptions, making its agentic coding system available without separate add-on licenses or standalone accounts. The operational shift is that enterprises can deploy agents that work with code, terminals and browsers while keeping access, spending and audit controls in the same subscription environment.
Antigravity is designed for work beyond code completion. Google says its agents can research codebases, run local builds, operate browsers and carry out end-to-end tasks. Bringing that capability into Gemini Enterprise changes who can provision it: IT and engineering leaders can enable it under a single subscription rather than asking developers to acquire a distinct product license.
Google says enterprise users can authenticate through Workforce Identity Federation and Application Default Credentials, using an existing enterprise identity instead of manually setting up API keys. That arrangement is meant to make the agent available as part of the organization’s existing access model, rather than as a separately managed developer account.
The tradeoff in agentic development is clear: an agent that can inspect local code, execute terminal commands or actuate a browser has more ability to complete a task, but also needs firmer boundaries. Google says Gemini Enterprise administrators can set those boundaries at the workspace, permission, budget and audit layers.
Google also says enterprise activity remains within the customer’s enterprise boundary under Google Cloud Terms of Service, and that customer code is not used to train its base models. It further says enterprise sessions respect existing IAM policies and VPC Service Controls. Those assurances are product-policy commitments from Google, not an independent assessment of an organization’s implementation.
Alongside the subscription change, Google announced Antigravity extensions for VS Code, Visual Studio 2026, JetBrains IDEs and Zed. The extensions offer side-panel conversations with agents, inline diffs, plan inspection and delegation of multi-step work without requiring developers to leave their IDE.
A single Antigravity account works across supported editors and shares session context with the standalone Antigravity application. That is the more consequential part of the IDE rollout for organizations with varied stacks: developers can change editing environments without starting a separate agent relationship or losing the work context held by the service.
VS Code extensions are available on macOS, Linux and Windows. JetBrains support covers IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion and Rider beginning with version 2026.2.1, while Visual Studio 2026 support for .NET solutions is in preview. Enterprise support for JetBrains and Zed also remains in preview.
The rollout’s central test is therefore not simply whether an agent can appear in another editor. It is whether the promised continuity of account, context and enterprise controls works consistently for teams that use several editors and include preview-supported environments in their development workflows.
Editorial analysis
This is less a new code-assistant feature than a bid to make enterprise governance portable across developer environments. Google’s differentiator is not that VS Code, JetBrains, Zed and Visual Studio can host an agent; those are different working surfaces for the same identity, session context and administrative policy model. The next proof point is the rollout quality in mixed-editor organizations, especially while enterprise support for JetBrains and Zed remains in preview. If that continuity is reliable, Antigravity can become an organizational layer rather than another isolated IDE plugin.
Loading discussion...
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.