Anthropic Ran a Two-Week Sprint Where Claude Benchmarked and Fixed Its Own App to a 3.1x Speedup
Anthropic ran a two-week performance sprint on claude.ai’s web and desktop apps in August 2026. Claude built the measurement benchmarks, investigated bottlenecks, and authored approximately 3,000 code changes across the sprint. Engineers selected the performance targets, decided what to measure, and reviewed and approved deployments before they went live. The average speedup across 13 measured interactions was 3.1x.
Division of work
The sprint split responsibilities clearly:
- Engineers: chose which journeys to target, defined what to measure, reviewed and approved every change before deployment
- Claude: built the benchmarks, investigated the root causes of slowdowns, and submitted the code changes — roughly 3,000 of them over two weeks
Anthropic’s framing from the write-up: with Claude, measuring something makes it tractable. Setting up deterministic benchmarks was the enabling step; once measurement existed, Claude could work through the bottleneck list.
The numbers
Thirteen specific user interactions in the claude.ai web and desktop apps were measured before and after the sprint. The average speedup across those 13 interactions was 3.1x, calculated as the geometric mean of p75 timings. Published per-interaction examples:
- Fresh page load (claude.ai): 3,085 ms → 550 ms
- Message sending: 928 ms → 48 ms
The sprint covered both the web client and the desktop application.
What makes this distinct
Claude writing code is not new — Anthropic reported in June that Claude authors more than 80% of its own production code. The sprint result illustrates a different configuration of that capability: Claude also built the measurement infrastructure that told it what to fix. The code-writing and the benchmark-writing came from the same system.
The practical implication is that performance engineering at this scale — 3,000 changes in two weeks, across two clients — becomes feasible with a loop where the agent both measures and fixes, rather than one where engineers instrument and agents only implement. Engineers remain the judgment layer on what to target and what to ship; the analytical and implementation work scales under that oversight.