Antigravity’s extensions bring the agent into existing editors, but editor availability and enterprise support are separate questions. The current documentation also lists Xcode, which the original article omitted.
Check the editor and the account together
The extension announcement and current documentation list VS Code, Visual Studio, JetBrains, Zed and Xcode. Visual Studio is in preview; enterprise support for JetBrains, Zed and Xcode is also labeled preview in the documentation. JetBrains starts at 2026.2.1; the Xcode announcement specifies 27 beta 6 or later.
An extension's existence is not a claim that every enterprise feature has the same availability in every editor. Record the editor version and authentication route when comparing capabilities.
Personal Google sign-in uses the individual's plan. Enterprise sign-in uses the organization's identity and selected Cloud project. The enterprise data and governance statements should not be silently applied to a personal-account session merely because both sessions appear inside VS Code.
Spending and permissions answer different questions
Google's enterprise announcement describes pooled quotas, project-level spend caps and optional overages, while per-user and team controls are presented as later rollout work. It also describes centralized workspace, browser and MCP policies and opt-in logging of prompts, responses and metadata.
A budget controls spending; it does not define which files an agent may access. An editor extension provides a surface; it does not demonstrate that the session inherited the intended corporate policy. Treat those as separate checks in a rollout.
See the actual administration surface
Google's video below demonstrates Gemini Enterprise's AI developer tools settings, including the security and logging sections. It is an official publisher demonstration, not a recording of the user's account or proof that a particular organization's policies are configured correctly.
Gemini Enterprise: AI developer tools settings
Official presentation from Google. The YouTube player loads only when you request it.
Watch on YouTube · Maintainer’s announcement. Loading the player connects to YouTube, which applies its own privacy policy.
A small, observable evaluation
For an original pilot worksheet, use a disposable repository with one deliberately failing test and a short requested repair. Record the signed-in identity, project, editor version and permissions before starting. Inspect the proposed diff and run the relevant test; do not equate the agent's success message with a verified repair.
Then check the expected administrative evidence: which usage is charged to the project and what appears in the configured audit log. If prompt logging is enabled, decide who can read it and how long it should be retained before using confidential repository material.
This is a proposed evaluation, not a claim that PeopleAreGeek installed every extension or audited Google's controls. It helps distinguish a working editor integration from a deployment whose identity, cost and access rules are actually understood.
Distinguish editor availability from enterprise preview and account policies; include Xcode and official admin demo, omit unrelated corporate speculation.