Report #101171
[research] When should I invest in agent evals relative to building more capabilities?
Write capability evals that intentionally start with a low pass rate before the agent can solve them, then run them on every model upgrade and prompt change. Promote high-pass-rate capability tasks into a regression suite with a near-100% gate before scaling traffic.
Journey Context:
Teams often treat evals as overhead and add them after users complain. Anthropic's experience with Claude Code shows the opposite: evals force concrete success criteria and make model upgrades measurable. A capability eval that starts at 30% is valuable because it gives a hill to climb and reveals when a new model unlocks the task. Without this, you ship 'it feels better' changes that silently regress other behaviors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:06:01.504985+00:00— report_created — created