Back to feed

How we made claude.ai 3x faster in two weeks

claude.dev

Sep 24, 2026

9/24/2026

AI-Driven Optimization Scales Through Human Governance and Incremental Risk Controls

How we made claude.ai 3x faster in two weeks · claude.dev

Science, Technology & Innovation · Sep 24, 2026

A human-governed deployment loop let AI deliver over 3,000 optimization changes in two weeks without reported customer incidents or rollbacks by combining automated review, human approval, testing, feature flags, telemetry, staged rollouts, and disciplined cleanup.


9/24/2026

AI-Assisted Optimization Requires Metrics Causally Linked to User Latency and Regression Safeguards

How we made claude.ai 3x faster in two weeks · claude.dev

Science, Technology & Innovation · Sep 24, 2026

AI-assisted performance work scaled by using causally validated, deterministic metrics as CI-enforced ratchets: optimizing instruction counts on two hot paths cut them 48% and 31%, reducing wall-clock time 78% and 44%, while preventing regressions and benchmark-only optimization.


9/24/2026

Prioritizing A Small Number Of Dominant User Journeys Delivers Significant Frontend Performance Gains And Daily Time Savings

How we made claude.ai 3x faster in two weeks · claude.dev

Science, Technology & Innovation · Sep 24, 2026

Claude.ai and the Claude desktop app became about 3× faster in two weeks by focusing on the four user journeys responsible for 95% of activity. Key 75th-percentile improvements included fresh claude.ai load-to-typeable time dropping from 3.1s to 0.55s, Claude Code session start from 0.8s to 0.3s, and Cowork cloud-session load from 2.6s to 0.73s. Techniques included server-rendering a static composer, precompiling a V8 code cache, preserving the composer during navigation, prefetching hovered sessions, and cutting sidebar rerenders by 90%, saving an estimated tens of thousands of user-hours daily.


9/24/2026

Deterministic Frame Budget Enables 120 Hz Rendering And Predictable Frame Pacing For Long Responses

How we made claude.ai 3x faster in two weeks · claude.dev

Science, Technology & Innovation · Sep 24, 2026

A deterministic 120 Hz Chrome rendering test enabled the team to eliminate streaming bottlenecks, reducing long-response main-thread blocking from ~750 ms to ~200 ms, cutting CPU use to one-third, sustaining 120 fps, and turning frame pacing into a nightly regression-tested property.