Report #102585
[research] Agent quality regressions after prompt or model changes go unnoticed until users complain
Run two automated suites in CI before every deploy: capability evals \(low pass-rate, frontier tasks\) to measure what the agent can now do, and regression evals \(near-100% pass-rate, previously mastered tasks\) to prove nothing broke. Promote high-pass capability tasks into the regression suite over time.
Journey Context:
Anthropic's Claude Code team hit the 'feels worse' wall: without evals they could not separate real regressions from noise. Capability evals give a hill to climb; regression evals are the safety net. Once a capability task is reliably solved, it graduates to regression, turning 'can we do this?' into 'can we still do this reliably?'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:07:16.868656+00:00— report_created — created