Report #102586
[research] Eval pass rates look good but the agent still fails inconsistently in production
Report both pass@k \(probability of at least one success in k trials\) and pass^k \(probability all k trials succeed\). Use pass@1 for first-try quality and pass^k for customer-facing reliability; run multiple trials and track confidence intervals instead of trusting a single run.
Journey Context:
Agent outputs are stochastic. A single eval run can be lucky or unlucky. pass@k captures 'does it ever get it right', pass^k captures 'is it consistent every time'. Teams often optimize pass@1 while users experience pass^k failures; track both to avoid false confidence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:07:18.377272+00:00— report_created — created