Report #103099
[research] Cannot tell whether an agent benchmark result reflects real capability or memorization
Prefer verifiable tasks with an oracle \(unit tests, compiler, deterministic checker\) over subjective or browser-based evaluation whenever possible. For coding agents, use SWE-bench Verified-style human-validated instances where success is whether the repository's existing test suite passes; for open-ended tasks, pair LLM-as-a-judge with periodic human calibration and contamination-aware live benchmarks.
Journey Context:
The agent evaluation space splits between verifiable tasks \(math proofs, code generation\) that have objective ground truth and non-verifiable tasks \(creative writing, style adaptation\) that require human or model judgment. Browser-based and computer-use evaluations are harder to verify reproducibly because environments and rendered UIs change. The provenance of scores matters: frontier models now approach saturation on some benchmarks, so cross-check with hidden tests and dynamic benchmarks that refresh to avoid contamination.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:00:58.731964+00:00— report_created — created