Claude Code quietly switched its runtime to a Rust build of Bun
Simon Willison found Claude Code v2.1.181 and later ship an unreleased Rust-compiled Bun canary build, verified by inspecting the binary directly. Startup got about 10 percent faster on Linux. Almost nobody noticed.
Claude Code's runtime quietly became a Rust build of Bun. Startup got 10% faster. Nobody noticed.
Simon Willison discovered that Claude Code v2.1.181 and later ship a Rust-compiled build of Bun instead of the original implementation, an unreleased canary build not yet in official Bun releases. He verified it by inspecting the binary directly.
How he found it
Willison found 563 references to Rust source file paths inside the Claude Code binary and confirmed the embedded Bun version, 1.4.0, is a canary build, meaning it is ahead of what Bun itself has publicly shipped. That canary build has since become available to developers directly through bun upgrade --canary.
What actually changed for users
Startup got roughly 10 percent faster on Linux. Otherwise, by Willison's account, barely anyone noticed. That is close to the point: a major runtime rewrite, shipped to millions of installs, with almost no visible disruption. The Bun team's own framing for this kind of change is that boring is good, and a rewrite this large landing this quietly is the evidence for it working in production.
Why a build studio cares
Claude Code is a tool our own workflow runs on daily. A runtime swap this significant landing without incident is a genuinely useful signal about how production ready Bun's Rust port actually is, not just a curiosity about our own tooling. It is also a clean example of the kind of infrastructure change worth making quietly: measurable improvement, no user-facing migration required.
Next step: read Simon Willison's full writeup for the binary inspection details. If a runtime or dependency swap in your own stack could ship this quietly, write to us at hello@gattyworks.com.