Agentic coding is straining CI. Here’s how we scaled test impact analysis at Anthropic
- ID
- 24374
- Status
- summarized
- Published
- 14 Sep 2026, 8:00 AM
- Fetched
- 15 Sep 2026, 5:49 AM
- Provider
- Claude
- Category
- ai-labs
- Original URL
- https://claude.com/blog/agentic-coding-is-straining-ci-heres-how-we-scaled-test-impact-analysis-at-anthropic
- Source URL
- https://raw.githubusercontent.com/leontloveless/ai-rss-feeds/main/feeds/claude.xml
Summary
- Score
- 7.5
- Created
- 15 Sep 2026, 5:49 AM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Anthropic reports a 25x increase in CI job volume over 6 months as Claude now authors 80% of their code and engineers ship 8x as much per quarter compared to 2021-2025. Their test impact analysis service required three escalating patches (lasting 70 days, 29 days, then less than a day) before they fully redesigned the architecture, concluding that incremental scaling buys diminishing time while full redesigns are now cheaper since code generation is no longer the bottleneck.
Why it matters
If you are shipping with agentic coding tools, expect your CI pipeline to become the next bottleneck as PR volume and test counts multiply. Plan for exponential CI load growth now rather than relying on quick fixes like bigger machines or parallelization, which Anthropic found bought progressively less time. The shift means architecture redesigns are now faster to execute than incremental patches because AI handles the code-writing.
Discussion angle
How soon will Malaysian dev teams using Claude Code or similar agents hit CI bottlenecks, and should they invest in test selection services preemptively rather than reactively?