Google has folded Antigravity, its autonomous coding agent, into eligible Gemini Enterprise plans at no additional cost. Capabilities that previously required separate procurement and standalone account management now ride on an existing subscription. Extensions for the major code editors landed at the same time, so the same agents can be reached without opening a dedicated app.
No More Separate License Procurement
The change covers Gemini Enterprise Standard and Plus. Organizations holding either license get Antigravity within the scope of that contract, and developers can start using it without waiting on add-on approvals.
Agentic development tools tend to clear a departmental pilot easily and then stall at company-wide rollout, where licensing becomes the bottleneck. This adjustment removes that step outright. On the administrative side, usage visibility, security governance, and cost management all collapse into a single place.
Sign-in has been tidied up as well. Every surface natively supports Workforce Identity Federation (WIF) and Application Default Credentials (ADC), so engineers authenticate with the enterprise identity they already use. There is no step where someone manually provisions an API key and hands it to an agent.
Called Directly From the Editor You Already Use
IDE extensions shipped alongside the bundling. Supported environments are Visual Studio Code, Visual Studio, JetBrains IDEs, and Zed. Enterprise support for Visual Studio, JetBrains, and Zed is currently in preview. The standalone Antigravity 2.0 app and the command-line version remain available, which makes it easier to standardize the entry point across teams running different setups.
What Antigravity handles sits a step beyond code completion. The agents research a codebase on their own, run local builds, actuate a browser, and carry a task through end to end.
Reins on Autonomous Execution
Once agents are running terminal commands, reading local code, and driving a browser, the organization needs controls. This release gives administrators several:
- Sandbox and policy settings. Workspace sandboxing can be enforced, and browser or MCP (Model Context Protocol) server permissions restricted, so agents operate only inside authorized environments.
- Budget caps and pooled quotas. Monthly thresholds can be set per project, per team, and per individual in Google Cloud Billing. Purchased capacity can be routed to the teams that need it rather than sitting idle.
- Overage controls. Overages can be enabled with hard caps, so an in-flight workflow is not cut off mid-task when a quota runs out.
- Audit logging. A single toggle captures prompts, agent tool executions, and generated artifacts in full.
On data handling, agent activity stays inside the enterprise boundary and falls under Google Cloud Terms of Service. Google also states plainly that submitted code is not used to train its base models.
An Early Case, and What Is Still Unclear
The named early adopter is the airline AirAsia. Its engineering teams reportedly generate more than 50 percent of their production QA code with Antigravity. Testing carries a high share of repetitive work, which is where agent output shows up in numbers most readily.
Several operational details remain hard to pin down from what has been published: the fine print on which licenses qualify, the unit pricing of pooled token quotas, and how organizations already holding a separate add-on contract are treated. Anyone sizing this for a company-wide rollout will want those answers first.
Summary
Google Antigravity is now included in Gemini Enterprise Standard and Plus at no additional cost. Extensions for major IDEs including VS Code, JetBrains, Visual Studio, and Zed arrived with it, and authentication runs on existing enterprise identities. Together with sandboxing, budget caps, and audit logging, the package reads as groundwork for lifting agentic development out of departmental pilots and into company-wide operation. Whether the payoff holds will depend on figures like AirAsia's showing up in other industries.
