Field noteAug 17, 20261 min read3 sources

Agent evaluation is moving from leaderboards to operating diagnostics

In one minute

Open tasks, stack benchmarks, delivery checks, and behavior catalogs expose why an agent succeeded or failed.

Agent evaluation is acquiring diagnostic surfaces around the score. Mercor publishes sample tasks for Terminal-Bench and related benchmarks, DORA's Quick Check connects delivery practices to concrete improvement areas, and AgentBehavior organizes observed behaviors that can appear during an agent trajectory.

The shared move is from “which model ranks first?” to “which system configuration produced this result?” A meaningful record includes the model version, harness, tools, context budget, cost, reviewer interventions, and any unsafe actions along the way. Without that data, a leaderboard cannot explain whether the gain will survive a different repository or policy.

For production selection, eval output should lead to an operating decision: allow, restrict, route, review, or reject a model-plus-harness combination. Open tasks and behavior traces make that decision auditable. They also make regressions easier to localize when a model, tool, or prompt changes independently.

Sources

Evidence / sources

  1. 1mercor.com/apex/oss-benchmarks/oss-terminal-bench-2-1-leaderboard/sample-task
  2. 2dora.dev/insights/quickcheck-updates
  3. 3agentbehavior.dev
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAgent EvalsExplore the agent-evals topic hub.
  2. 02topicObservabilityExplore the observability topic hub.
  3. 03topicHarnessesExplore the harnesses topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract