Google details results from Antigravity's /teamwork multi-agent system: a two-week campaign rewrote the rest of the Zircon microkernel into about 800,000 lines of safe Rust, and the tools are open to outside developers
The interesting part is not the proofs but how Google structures long-running coding agents: who verifies, how context is split, how migrations are ordered. For teams using agents for code migration or performance work.
// Key points
- The design pairs parallel exploration with falsifiers (the Lean 4 proof checker, unmodified test suites, execution simulators, hardware counters and others) to decide which candidates work; each agent gets only the files and tools its step needs, and critics re-check results from clean contexts without the producer's reasoning.
- A new rewrite pattern, coming to Antigravity, schedules each module only after its dependencies compile and links every leaf module against the original, unmodified test suite. Building on a 25% port, a two-week Argon campaign added about 800,000 lines of safe Rust that pass all kernel unit tests and boot on arm64 hardware.
- libgav1, Google's AV1 decoder, was rewritten into about 170k lines of Rust with 100% bit-exact parity on a broad conformance suite; it started about 4x slower than C++, and after /teamwork got profiling tools and a mandate to maximize speed it ended 20-30% faster than the original C++ and hand-optimized assembly on x86_64 and ARM.
- /teamwork and /boost are available in Antigravity today with Gemini 4 models; Google has also opened applications giving 10,000 academic researchers six months of free access to its highest usage tier.
Builder's takeThe method is what to copy, not the model: verify with tests the agent cannot edit, order work by dependencies, and give each agent only the context it needs. The failure mode the post names, stubbing out dependencies or changing tests so a broken port passes, is exactly what I see most when coding agents do migrations, so I would make the test directory read-only before letting one loose. The numbers are Google's own; try /boost on a real migration of one small module first.
// Background · from #Google
Full timeline →- Nov 15 Gemini connects to Google Wallet: US users can let Gemini read their spending for finance insights, but it cannot move money
- Nov 15 Gemini 4 Hydrogen is generally available in GitHub Copilot: billed at provider list price across IDEs, the CLI, the coding agent and the Copilot SDK
- Nov 15 Google AI Studio now handles Cloud credits in place: AI Pro and Ultra subscribers can apply monthly credits straight to the Gemini API