X discussion: Anthropic's head of platform engineering says a team with no Rust developers had Claude port the whole Messages API to Rust, cutting CPU by roughly 40-50%
Katelyn Lesse, Anthropic's head of platform engineering, said on the Latent Space podcast (published Oct 27) that a Rust version of the Messages API fully rolled out the previous week. The old system was a CPU-hungry Python monolith, the team started with "not a single Rust developer", humans designed and verified the system, Claude wrote the implementation, and shadow traffic compared outputs between the old and new versions. Her ballpark figures are roughly 40-50% less CPU and 10-20% better time to first token. A clip posted by Somi (@somi_ai) drew 1,000+ likes and about 140K views on X and was quoted by swyx and others, with the debate centered on whether "never do the big rewrite" is now outdated advice. These are X discussion views and spoken estimates; Anthropic has not published a written engineering report.
Key Takeaways
- The first-hand source is Katelyn Lesse speaking on the Latent Space episode "How Anthropic ships Claude with Claude", in the "56:05 Rebuilding the Messages API in Rust" segment
- Lesse said the move was driven by CPU becoming a bottleneck as usage surged; CPU now has to be capacity-planned in advance, and research sandboxes, product sandboxes and CI all draw from the same pool inside Anthropic
- The team forked the entire API in Rust in one go, ran shadow traffic to confirm the Python and Rust outputs matched, then turned it on gradually, deliberately adding no new features during the port
- Her ballpark is about 40-50% CPU savings and 10-20% better time to first token, with larger gains on longer-running workloads; these are spoken estimates from the podcast, not a formal benchmark
- On X, Somi called "never do the big rewrite" dead advice and swyx said Anthropic "vibecoded their entire backend to Rust"; the latter is an exaggeration, since Lesse only discussed the Messages API
