Google's Antigravity agent moves into VS Code, JetBrains and Zed — with admin controls attached, signalling AI coding tools are being built for procurement, not just developers
Google has expanded its Antigravity AI coding agent out of its standalone desktop app into extensions for VS Code, JetBrains IDEs and Zed, tying it to Gemini Enterprise for admin budget and access controls — a sign that AI coding tool vendors are now designing for the person who buys the tool, not just the developer who uses it.
24 August 2026
Google has released extensions that bring its Antigravity AI coding agent directly into VS Code, JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider) and Zed, rather than requiring developers to move their project into a separate Antigravity desktop app. The VS Code extension is live now on Microsoft’s marketplace across macOS, Linux and Windows; JetBrains support starts with version 2026.2.1; a Visual Studio 2026 extension is in preview. Crucially, the same Antigravity account works across every environment, and the whole thing now sits under Gemini Enterprise — giving IT admins budget caps and access controls over who in an organisation can use it and how much they can spend.
The technical move — plugging an agent into editors developers already use instead of asking them to switch — is now standard playbook (Cursor, Windsurf and Copilot have all done versions of it). The more telling part is the enterprise wrapper. A year ago, AI coding tools were bought by developers on a personal card and expensed. Increasingly, they’re being bought by IT and engineering leadership with budget controls, access policies and procurement sign-off attached — the same governance layer that’s long existed for cloud spend or SaaS licensing. Google tying Antigravity to Gemini Enterprise admin controls, right as CodeRabbit launches AI-code governance tooling and Anthropic pushes Claude for Government and enterprise spend controls, is the same signal from a third direction: AI coding tools are graduating from developer toy to line item.
So what
If you’re commissioning software and your team (or your outsourced dev partner) is using AI coding agents, ask who controls access and spend on those tools — not just which one they’ve picked. A team with no governance around AI tool usage is a team that hasn’t thought about the risk surface either. We build with AI-assisted tooling deliberately, inside a process with the same access and quality controls we’d apply to any engineering practice. See how that works in our AI-assisted development approach, or get in touch to discuss your project.