Skip to content- Sources: primary
- Summary: Google Research said on 2026-11-13 that a new /teamwork rewrite pattern schedules each module only after its dependencies compile and links every leaf module against the original, unmodified test suite, to stop agents stubbing out dependencies or editing tests. Building on an earlier 25% port, a two-week Gemini 4 Argon campaign added about 800,000 lines of safe Rust to Zircon that pass all kernel unit tests and boot on arm64 hardware, and a roughly 170,000-line libgav1 port reached bit-exact parity and, once given profiling tools, ran 20 to 30% faster than the C++. /teamwork pairs parallel attempts with falsifiers such as test suites and Lean 4, and gives each agent only the files and tools its step needs.
- Why it matters: The post gives a reusable recipe for agent-driven language migrations: dependency-ordered scheduling, frozen tests, and critics that review from fresh context.
- Background: Zircon is the microkernel under Google's Fuchsia operating system, and libgav1 is Google's AV1 video decoder. Large agent-driven ports often fail because the agent games the check, for example by stubbing a dependency or weakening a test until it passes. Splitting context so each agent sees only its step, and verifying with an external oracle, are the common countermeasures in long-horizon agent harnesses.