Bun Rewritten from Zig to Rust in 11 Days with 64 Parallel Claude Fable 5 Instances — Anthropic's Full-Stack AI Coding Showcase
> Event date: July 8, 2026 (blog post) / indexed by aihot on 2026-07-11 > Source: IT Home + aihot > aihot link: https://aihot.virxact.com/items/cmrg3syhp00l7iha7a3ansg62 > Original article: https://www.ithome.com/0/975/469.htm
The Event
Developer Jarred Sumner announced on July 8 that, with the help of Anthropic's Claude Fable 5 model, an "unlikely" engineering feat was completed in 11 days at a cost of $165,000: fully rewriting the JavaScript runtime Bun from Zig into Rust.
Key figures:
- 64 Claude instances running in parallel for 11 days;
- Over 1 million lines of code written;
- API costs of roughly $165,000;
- Sumner estimates a human team would need about 1 year for the same workload;
- Main motivation: Zig's memory errors and crashes were hard to fully fix, while Rust catches most of them at compile time;
- Bun v1.4.0 has been released as a Canary build, fixing 128 bugs and running 2-5% faster.
Deep Analysis
The author's first reaction to these numbers: this is the first concrete embodiment of Anthropic's "full-stack AI Coding strategy."
Anthropic directly acquired Bun in December 2025 — a different path from OpenAI's acquisition of Windsurf. OpenAI folded a coding IDE asset into its stack, while Anthropic folded in a coding runtime asset. Claude Code is an IDE; Bun is a JavaScript runtime — both are "foundational tools" in the AI coding workflow.
In other words, Anthropic now owns Claude Fable 5 (model), Claude Code (IDE), and a JavaScript runtime (Bun). Building all three layers means Fable 5 could validate its capabilities on the Bun Rust rewrite before release — both proving the Bun team's AI coding and making Bun a natural foundation for Claude Code.
The "scale mismatch" of 1 million lines in 11 days is the key. In traditional engineering terms, 11 days is not even enough for requirements analysis, let alone a million-line rewrite — but 64 parallel Claude instances turned the problem from linear to parallel. Each instance handled a module or feature, running countless fine-grained tasks like rewriting Bun's compile-time checks, HTTP server, and fs APIs in Rust.
The $165,000 API cost looks scary but is actually very cheap — a human team would cost at least $2-5 million per year (senior US engineers). $165K vs $2M ≈ 1/12; the efficiency gain is not 10x but 50x+. This is the first time large-scale AI-assisted rewriting has been quantified in real money.
Why It Matters
The event redefines the boundaries of AI coding on three levels:
Level 1: From "completing functions" to "refactoring million-line projects." The early AI coding narrative was "Copilot writes your next line"; recently it became "Cursor refactors across files"; the Bun case jumps straight to "million-line language migration." This is the combined product of model capability and harness engineering.
Level 2: From "single-threaded" to "AI workforce." 64 parallel Claude instances mean Claude Code can be used as a "team" rather than a "personal assistant." The next watershed in AI coding is not stronger models but higher parallelism.
Level 3: From "model cost" to "full-stack strategy." The $165,000 is not a price tag for Fable 5 but an "entry ticket" for an AI coding tool experiment after Anthropic acquired Bun. The paradigm can be replicated to any runtime (databases, web frameworks, compilers).
Notably, Sumner's post does not give the ratio of AI-generated vs human-guided work in the million lines. One can speculate that the truly "AI end-to-end" portion may only be 30-50%, with the rest being review, prompt guidance, and CI/CD validation. Even so, 11 days remains an impossible-seeming task — the real scarcity is not the soldiers but the person who can command them.
Risks and Open Questions
Risk 1: Canary ≠ GA. Bun v1.4.0 is a Canary build, not the final release. No regression test pass rate, production compatibility, or memory leak data has been published for the million lines of new code. It is unclear how much of the 2-5% speed gain comes from Rust itself versus genuine optimization from the rewrite.
Risk 2: The reverse cost of engineering. Rewriting a million lines is easy; the million lines of ecosystem dependencies, user migrations, and third-party plugin adaptations are not eliminated by AI. When can Bun v1.4.0 fully replace v1.3's ecosystem position? Sumner did not say.
Risk 3: Transferability of the Fable 5 experience. The 11-day success may rely heavily on the Bun team's domain expertise — they are Bun's authors and know what every module does. Whether Claude Fable 5 maintains this efficiency on an unfamiliar project is an open engineering question.
Most critically: this large-scale rewrite is a product of Anthropic's internal "self-sufficiency" — it does not directly prove that external teams can replicate the success with the same tools. It demonstrates "possibility," not a "replicable SOP." That distinction deserves the attention of every engineering team considering AI-driven refactoring of legacy projects.
*Note: The 30-50% AI end-to-end ratio and the 50x+ efficiency figures are the original author's speculation/estimates, not official figures.*