Skip to main content

Decision brief

Google Antigravity Review: Which Route, Which Surface, and What to Lock Down

Roll out Antigravity through Gemini Enterprise seats, keep engineers off personal Google AI plans, and change the admin defaults first. Which surface to standardize on, and what to lock down.

Reading time
4 min read
Sources
24 cited

GILD verdict

Adopt Antigravity on Gemini Enterprise seats if your organization runs on Google Cloud, after changing the admin defaults and setting a budget cap.

Keep it out of audited environments until Google lists SOC 2 and ISO 27001 coverage. It is Google's coding agent platform for engineers and teams, and Google is moving its other coding agents' users onto it. Gemini CLI's individual users moved in June 2026, and Google directs Code Assist customers to it through Gemini Enterprise.

Google Antigravity

AI Coding Agent by Google

−16 Mixed
Product page

Fit and limits

Who it fits

  • Your organization runs on Google Cloud and can license Gemini Enterprise Standard or Plus, which include Antigravity 2.0, the Antigravity CLI, and the IDE extensions with no separate Antigravity license.
  • You hold Gemini Code Assist subscriptions. Google stopped selling new ones on October 9, 2026 and names Antigravity in Gemini Enterprise as the path for agentic coding.
  • Engineers want to approve an implementation plan before the agent builds and read a walkthrough when it finishes. All 13 practitioners who discuss these artifacts value them.
  • You want Gemini and Claude models under one Google contract. Administrators can enable Claude Opus 5.5 and Sonnet 5.5, billed per token, beside Gemini 3.8 Flash and 3.1 Pro.
  • Front-end teams want the agent to check its own UI work. The browser agent opens the app, clicks through it, and saves screenshots and recordings.
  • Engineers work in VS Code, Visual Studio, JetBrains IDEs, Zed, or Xcode and do not want a new editor, since the August 2026 extensions bring the same agent there.

Where it falls short

  • Google states that Antigravity in Gemini Enterprise does not support SOC 1, 2, or 3, ISO 27001 or 42001, FedRAMP, IL4 or IL5, ITAR, or Access Transparency. It gives no date for adding them.
  • Several Gemini Enterprise defaults are permissive: terminal auto-execution is Always proceed, sandbox mode and logging are off, and browser and MCP access are uncontrolled until an administrator turns those controls on.
  • Quota rules changed four times between November 2025 and August 2026. Quotas and lockouts lead practitioners' concerns: 39 of 123 accounts discuss them, and 29 call them a problem.
  • Google split the product on May 19, 2026, and engineers report the update installing the Antigravity 2.0 app in place of the IDE. Google does not support the standalone IDE for enterprise, and its changelog lists no IDE release in the ten weeks after August 13, 2026.
  • Of 25 practitioners who compare it with Claude Code, Codex, Cursor, or Copilot, 20 judge it behind.
  • On personal Google accounts, Google records interactions, uses them to improve its products, and lets staff review them unless the user opts out. Using another tool with an Antigravity login can get the account suspended.

Implementation reality

  1. Choose the route before the surface

    Put engineers on Gemini Enterprise seats and off personal Google AI plans. Seats carry Google Cloud terms, keep code, prompts, and transcripts out of model training, and give administrators settings and logs. Personal plans run under consumer terms with Google's training preference on by default and no organizational tier.

  2. Change the defaults before day one

    In the Gemini Enterprise AI developer tools settings, set terminal auto-execution to Require review or Proceed in sandbox and turn sandbox mode on. Restrict browser access to an allowlist and limit MCP servers to an approved configuration. Turn on prompt and response logging if you need an audit trail; it stays in your project and is not used for training.

  3. Standardize on supported surfaces

    Use Antigravity 2.0 for parallel agents, the CLI for terminal and headless work, and the extensions for engineers who stay in their editor. Leave the standalone Antigravity IDE out of enterprise rollouts, since Google does not support it there. JetBrains, Zed, and Xcode enterprise sign-in are not yet generally available.

  4. Budget on the weekly pool

    Seat credit, US$10 per user per month on Standard and US$15 on Plus, is enforced as one weekly pool per edition and location with no rollover. Decide whether overage runs at pay-as-you-go rates, and set Cloud Billing budget caps. Approve Claude models only for teams with a budget, since they bill per token and Gemini keeps running in the background.

  5. Make plan approval and tests the review standard

    Set the artifact review policy to Request review, start larger tasks with /plan, and require a passing test or browser check before a walkthrough counts as done. Keep commits and pushes behind an Ask rule; practitioners report the agent acting on chat context even in Planning mode.

What to measure in your pilot

  • GILD found no SOC 2 or ISO 27001 date in Google's Gemini Enterprise docs, Antigravity changelog, or blog; get a written date from your Google account team before audited repositories use Antigravity.
  • GILD found no per-task credit figure in Google's quota docs or practitioner posts. Log the weekly pool balance for four weeks and move heavy users to Plus if it empties before day five.
  • Google's plans page gives no numeric Pro or Ultra quota and says limits can change; log lockouts per engineer weekly and move anyone locked out twice onto an Enterprise seat.

Sources

Official documentation
23
Public source
1
  1. Antigravity docs: Welcome to Google AntigravityOfficial documentationantigravity.google
  2. Antigravity docs: Antigravity 2.0 overviewOfficial documentationantigravity.google
  3. Antigravity docs: PlansOfficial documentationantigravity.google
  4. Antigravity docs: ModelsOfficial documentationantigravity.google
  5. Google Antigravity pricingOfficial documentationantigravity.google
  6. Google Antigravity Additional Terms of ServiceOfficial documentationantigravity.google
  7. Antigravity docs: FAQOfficial documentationantigravity.google
  8. Antigravity docs: Antigravity in Gemini EnterpriseOfficial documentationantigravity.google
  9. Antigravity docs: Agent permissionsOfficial documentationantigravity.google
  10. Antigravity docs: Artifact reviewOfficial documentationantigravity.google
  11. Antigravity docs: Antigravity IDEOfficial documentationantigravity.google
  12. Antigravity docs: IDE extensionsOfficial documentationantigravity.google
  13. Antigravity changelogOfficial documentationantigravity.google
  14. Antigravity blog: Changes to Antigravity plans (May 19, 2026)Official documentationantigravity.google
  15. Antigravity blog: Introducing Google Antigravity 2.0 (May 19, 2026)Official documentationantigravity.google
  16. Antigravity blog: Bringing Antigravity to Gemini Enterprise (Aug 20, 2026)Official documentationantigravity.google
  17. Gemini Enterprise docs: AI developer tools overviewOfficial documentationdocs.cloud.google.com
  18. Gemini Enterprise docs: Configure AI developer tools settingsOfficial documentationdocs.cloud.google.com
  19. Gemini Enterprise docs: Quotas and pay-as-you-go usageOfficial documentationdocs.cloud.google.com
  20. Gemini Enterprise docs: Compare editionsOfficial documentationdocs.cloud.google.com
  21. Gemini Code Assist docs: Gemini Code Assist Standard and Enterprise subscriptionsOfficial documentationdocs.cloud.google.com
  22. Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (May 19, 2026)Official documentationdevelopers.googleblog.com
  23. Google One: Google AI plansOfficial documentationone.google.com
  24. SWE-bench: Verified leaderboard (as of Oct 25, 2026)Public sourceswebench.com