At Google I/O 2026, Google's Antigravity team ran a demo that stopped the AI engineering world mid-scroll: a fleet of 93 AI subagents, powered entirely by Gemini 3.5 Flash, autonomously wrote a working operating system from scratch. Kernel, memory manager, filesystem, video drivers, keyboard drivers. No human in the code path. Twelve hours later, they booted Doom on it.

The numbers are precise and verifiable. It took 93 subagents, 15,314 model calls, and over 339M input tokens , with cache reads, output, and thinking, that number goes to over 2.6B tokens. The total API cost came in at less than $1K. More precisely, $916.92.

What Antigravity 2.0 actually is

Antigravity 2.0 is Google's AI agent development platform, announced at Google I/O. It replaces the previous Antigravity code editor with a five-component platform , desktop app, CLI, SDK, managed agents API, and enterprise Cloud path , built around parallel AI agent orchestration powered by Gemini 3.5 Flash.

Google repositioned Antigravity from a tool that helps developers write code into what it calls an "agent control tower" , a platform for supervising multiple AI agents working on a project simultaneously. The shift is architectural: rather than crowding a single context window with a massive array of instructions, a primary agent defines and deploys dynamic subagents to execute narrow, specialized subtasks in parallel. These subagents process their workloads independently in the background, generate verifiable deliverables called artifacts, and report their refined findings back to the main agent.

The 7-role team that built an OS

The most reusable idea from this demo isn't the scale , it's the role structure. The team only reused core agent primitives available in Antigravity 2.0, such as parallel-running subagents, asynchronous tasks, and hooks. There was no special version of the product used. Instead of a single agent wearing many hats, they created a series of subagent types with specialized goals and constraints.

Three of the seven roles never write a single line of code. Their job is to think, plan, and verify. Here's the full breakdown:

• Sentinel , the "front-desk manager." Structures user intent, spawns the Orchestrator, and supervises overall task completion. No code written.
• Orchestrator , dispatch-only manager. Decomposes requirements into milestones and kicks off subagents. No code written.
• Explorer , analyzes requirements and previous logs to write formal strategies for the Orchestrator to act on, but never writes code itself.
• Worker , the actual coder that implements the strategies, builds the code, and runs tests.