Claude Code Switches Its Runtime to Bun, Which Is Written in Rust

Claude Code now runs on Bun instead of Node.js. Bun is implemented in Zig and Rust and uses JavaScriptCore as its engine rather than V8. The switch means Claude Code's CLI inherits Bun's faster startup times and its built-in bundler and transpiler, removing several layers of toolchain overhead that came with the Node.js path.

For engineers running Claude Code as part of an automated pipeline or tight inner-loop workflow, the immediate practical effect is reduced cold-start latency. Bun's native TypeScript execution also removes the need for a separate transpilation step at runtime, which cuts down on process initialization complexity.

The architectural choice signals something about how Anthropic views the CLI's future surface area. Bun ships as a single binary with a built-in package manager, test runner, and bundler. Consolidating onto it reduces external dependency surface and simplifies distribution — relevant for teams that install Claude Code in CI environments or air-gapped setups where dependency resolution is a friction point.

This also puts Claude Code's runtime stack closer to what many TypeScript-native projects already use internally. Founders and small teams building on top of Claude Code's programmatic interface will find the dependency footprint leaner than before.

The move is consistent with a broader pattern in developer tooling: mature Node.js-era CLIs migrating to faster runtimes as Bun and Deno have stabilized. Bun in particular has reached a point where production adoption carries acceptable risk for tooling that does not require deep Node.js ecosystem compatibility.

No API surface changes are reported alongside this runtime shift. Existing integrations should continue to work without modification. Engineers who have patched or extended Claude Code's internals directly should verify compatibility against their local modifications.

Source