Google confirms Antigravity SDK parity

Google confirmed at I/O 2026 that the Antigravity software development kit offered to outside developers is the same underlying agent harness used in Google’s own products. The clearest public wording appears in a May 19 Google developer blog post, which said the “Antigravity SDK” provides programmatic access to “the same agent harness powering Google’s products.” PPC Land reported on May 23 that Google executives and developer materials at I/O framed that parity as part of a broader push toward agentic software tooling. Google’s own I/O pages and codelabs back the main product claims around Antigravity as an “agent-first” platform built to plan, code, test and manage multiple agents. The important point for developers is not just branding. Google’s public documentation says the SDK is not a stripped-down wrapper for external use, but access to the same core harness Google says powers its own products. (blog.google) That narrows the gap between internal tooling and what third parties can build on top of Google’s agent stack. (ppc.land) ### Where did Google say the SDK matches its internal tooling? Google said it directly in its I/O 2026 developer highlights post published May 19. In that post, Google described the Antigravity SDK as providing “programmatic access to the same agent harness powering Google’s products,” and said the SDK is optimized for Gemini models while letting developers define custom agent behaviors and host them on infrastructure of their choice. (blog.google) PPC Land’s May 23 report matched that reading and said the SDK available externally is the same one used by Google’s own Search team internally. I could verify Google’s wording from the company’s post; the more specific reference to the Search team comes from PPC Land’s account of I/O presentations and documentation. ### What is Antigravity supposed to do in practice? Google described Antigravity at I/O as an “agent-first development platform” that helps developers move from an idea to a production-ready application. (blog.google) The company said the new Antigravity 2.0 desktop app can orchestrate multiple agents in parallel, while the CLI offers a terminal-based surface for creating agents quickly. (ppc.land) Google’s getting-started codelab adds more detail. It says Antigravity is designed around autonomous agents that can plan, execute, validate and iterate on engineering tasks, and includes tools such as an Agent Manager, editor and browser. An I/O session page described the workflow in similar terms, saying developers can move from rapid prototyping in Google AI Studio to Antigravity for tasks such as planning architecture, writing multi-file features and performing end-to-end browser testing. (blog.google) ### What supports the claim about latency and tool-speed bottlenecks? Google’s May 19 I/O developer post tied its broader agent push to speed. (codelabs.developers.google.com) The company said Gemini 3.5 Flash was built to provide the “high-speed engine needed for real-world agentic workflows” and described it as running four times faster than other frontier models. (io.google) Google’s product and session materials also repeatedly emphasize parallel execution and fast iteration. The Antigravity 2.0 app is described as supporting dynamic subagents for parallelized workflows and scheduled background tasks, while the CLI is presented as a “high-velocity” surface. That does not amount to a single Google statement saying “latency is the bottleneck,” but it does support PPC Land’s reading that Google is designing agent tooling around speed constraints. (blog.google) That is an inference from Google’s emphasis on faster models, parallel subagents and automated task execution across the I/O materials. ### Why does SDK parity matter to outside developers? Google’s wording matters because it suggests outside developers are getting access to production-grade agent infrastructure rather than a separate public-only layer. The company said developers can define custom agent behaviors and host them on their own infrastructure, which points to broader deployment flexibility than a closed internal tool would allow. (blog.google) Google’s codelabs show how that stack is meant to be used. One codelab published April 30 walks developers through extending an ADK-based restaurant concierge agent with reservation booking using Antigravity’s spec-driven workflows, reusable skills and MCP-based tools. ### What can developers check next? Google’s Antigravity materials are already public. (blog.google) The May 19 I/O developer highlights post, the I/O 2026 session pages, and the Antigravity codelabs on Google for Developers provide the clearest primary-source record of what Google said and shipped around SDK access, agent orchestration and deployment workflows. (codelabs.developers.google.com)