Building a C compiler with a team of parallel Claudes
01:00 · February 5, 2026 · Antropic Engineering Blog

We tasked Opus 4.6 using agent teams to build a C Compiler, and then (mostly) walked away. Here's what it taught us about the future of autonomous software development.
Summary
Nicholas Carlini, a researcher on Anthropic’s Safeguards team, describes an experiment in which 16 parallel instances of Claude Opus 4.6 worked autonomously on a shared Rust repository to produce a 100,000-line C compiler. Over roughly two thousand model sessions and $20,000 in API usage, the resulting compiler reached a 99 percent pass rate on major test suites and successfully built a bootable Linux 6.9 kernel for x86, ARM, and RISC-V targets, as well as several large open-source packages.
The central contribution lies in the scaffolding required to sustain long-running agent teams without continuous human oversight. Each agent runs inside its own Docker container mounted against a bare upstream Git repository; when an agent finishes a task it pushes its changes and immediately pulls the next available item. A lightweight locking scheme prevents concurrent work on the same file or bug, while extensive READMEs and progress logs allow freshly spawned agents to orient themselves quickly.
Test design proved decisive. Early in the project, agents could be assigned independent failing tests, but once the suite reached high coverage the remaining work collapsed into a single interdependent task—compiling the Linux kernel. To restore parallelism, the harness used GCC as an oracle: most files were compiled with the reference compiler and only a random subset with the agent-built compiler, allowing different agents to isolate and repair distinct defects. Additional agents were later specialized for duplicate-code removal, performance tuning, and documentation.
The compiler itself remains limited. New features frequently regressed existing functionality, and the model was unable to produce a compact 16-bit x86 backend that satisfied Linux’s size constraints for real-mode boot code; that phase still delegates to GCC on x86. These shortcomings illustrate both the current ceiling of fully autonomous agent teams and the value of the harness techniques developed to reach it.
Why it matters
Directly demonstrates actionable agent-team workflows, test harness patterns, and parallelism techniques that Product Teams and Builders can adapt for complex software projects using current Claude APIs.




