Timeline
- 9 June 2023
Zheng et al. publish MT-Bench and Chatbot Arena, establishing LLM-as-a-judge
Showed GPT-4 judges agree with human preferences over 80% of the time - and named position, verbosity and self-enhancement bias in the same paper.
- 17 June 2024
Sierra releases tau-bench with the pass^k metric
Made agent inconsistency measurable: GPT-4o succeeded on under 50% of tasks, and scored under 25% at pass^8 in the retail domain.
- 13 August 2024
SWE-bench Verified released: 500 human-screened instances from the original 2,294
Became the reference agentic coding benchmark, and the clearest example of saturation two years later.
- 19 November 2024
Anthropic publishes 'A statistical approach to model evals'
Gave eval reporting a canonical statistical standard: confidence intervals, clustered standard errors, paired difference tests.
- 10 April 2025
OpenAI releases BrowseComp, 1,266 hard-to-find questions
GPT-4o with browsing scored 1.9% against Deep Research at 51.5% - a benchmark built to separate real browsing from guessing.
- 29 April 2025
'The Leaderboard Illusion' published
Documented ~27 private Llama-4 variants tested before release and large data-access asymmetries in arena evaluation.
- 5 December 2025
ARC Prize 2025 results
ARC-AGI-2's top verified commercial result was 37.6%, showing at least one benchmark still far from saturation.
- 9 January 2026
Anthropic publishes 'Demystifying evals for AI agents'
The most prescriptive public document on running an eval program: task counts, outcome grading, capability vs regression suites.
- 5 February 2026
Anthropic quantifies infrastructure noise in agentic coding evals
CPU and memory configuration alone moved Terminal-Bench 2.0 scores by 6 percentage points (p < 0.01).
- 18 February 2026
ICML 2026 study of 60 benchmarks finds nearly half saturated
Confirmed saturation rises with benchmark age and that hiding test data offers no protection.
- 9 March 2026
OpenAI acquires Promptfoo
Then, on 3 June 2026, announced its own Evals dashboard and API would shut down on 30 November 2026, pointing users at Promptfoo.
- 4 September 2026
tau^tau-Bench asks coding agents to build a customer-service agent end to end
Best configuration reached 23.9% against an 82.2% expert reference - the frontier of unsolved agentic work.
Most teams instrument before they measure
LangChain's State of Agent Engineering survey, collected from 1,340 responses between 18 November and 2 December 2025, shows where the effort actually goes. 89% of organisations had implemented some form of agent observability and 62% had step-level tracing. Only 52.4% ran offline evaluations on a test set, and 37.3% ran online evaluations. Among teams that do evaluate, 59.8% rely on human review and 53.3% use LLM-as-judge scoring.
The gap tracks with commercial outcomes. Databricks, working from platform telemetry covering more than 20,000 organisations including over 60% of the Fortune 500, reports that companies actively using evaluation tools get nearly 6x more AI projects into production, and companies using AI governance 12x more. Gartner predicted on 25 June 2025 that over 40% of agentic AI projects would be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls.
This is happening against real spend. Menlo Ventures put enterprise generative-AI spend at roughly $37 billion in 2025, up from $11.5 billion in 2024 and $1.7 billion in 2023, from a survey of about 500 US enterprise decision-makers fielded 7-25 November 2025. In the same data, prompt design remains the dominant customisation technique, ahead of retrieval, with fine-tuning and reinforcement learning niche. If most of the quality work lives in the prompt and the scaffolding rather than the weights, the eval suite is the only instrument that tells you whether a change helped.
- 89% have observability; 52.4% run offline evals; 37.3% run online evals (LangChain, December 2025)
- Nearly 6x more projects reach production at companies actively using evaluation tools (Databricks, January 2026)
- Over 40% of agentic AI projects predicted to be cancelled by end-2027 (Gartner, 25 June 2025)
What we do with this
We treat the eval suite as the first deliverable of an engagement, not the last. Before tuning prompts we agree what correct means for twenty or thirty real cases, so every later change has a number attached to it.
The golden set: 20-50 tasks, each with a reference solution
Anthropic's engineering post 'Demystifying evals for AI agents' (9 January 2026) is the most prescriptive public document on this. Its advice is to start with 20-50 tasks drawn from real failures - bug trackers, support queues, manual spot checks - rather than waiting to assemble hundreds. Each task should be proven solvable by writing a reference solution first. A task no one can solve is not an eval; it is an open question.
The central shift is what you grade. Grading the final message is no longer sufficient for agents, because an agent can claim success in text while leaving the database wrong. Anthropic's guidance is to grade outcomes - the state of the environment after the agent acts - and treat the transcript as a separate, secondary artifact. The vocabulary has stabilised around trial, transcript, outcome, pass@k and pass^k.
pass@k is the probability of at least one correct solution across k attempts. pass^k is the probability that all k trials succeed, and it is the number that exposes unreliability. Sierra introduced it with tau-bench on 17 June 2024, reporting that GPT-4o succeeded on under 50% of tau-bench tasks overall and scored under 25% at pass^8 in the retail domain. A system that is usually right but rarely consistent across repeated trials is a demo, not a product.
Anthropic also separates two kinds of suite that are often conflated. Capability evals should start with low pass rates and leave headroom, because their job is to show you where the ceiling is. Regression evals should target roughly 100% and be maintained like unit tests - routine work, not an afterthought. Mixing them produces a suite that is neither diagnostic nor a gate.
- Start at 20-50 real-failure tasks; write the reference solution before the eval
- Grade the outcome (environment state); keep the transcript as secondary evidence
- pass@k for best-of-n behaviour; pass^k for reliability
- Capability evals: low pass rate, headroom. Regression evals: ~100%, treated as unit tests
What we do with this
For agent work we build outcome checks against a reset test environment - rows written, tickets closed, files changed - and keep transcript review as a separate human pass rather than the primary signal.
Graders: code, model, human
Both labs converge on the same three tiers. Code-based graders are fast and objective but brittle. Model-based graders handle subjectivity but need calibration. Human graders are the gold standard and are expensive, so they are used to calibrate the other two rather than to run continuously.
OpenAI's Graders API makes this concrete with five types: string_check, text_similarity, score_model, python and multi, all reporting a grade in the 0-to-1 range so partial credit is expressible. Anthropic's platform documentation enumerates six grading methods with worked code - exact match, cosine similarity, ROUGE-L, LLM Likert scale, LLM binary classification and LLM ordinal scale - and adds one rule that is easy to skip: use a different model to judge than the one that generated the output.
OpenAI's evaluation best-practices guide is also unusually specific about thresholds, which is the part most internal eval docs omit. Its summarisation worked example targets ROUGE-L of at least 0.40 and a coherence score of at least 80%. Its document Q&A example targets context recall of at least 0.85, context precision above 0.7, and 70% or more positively rated answers. The numbers matter less than the habit of writing one down before the run.
- Code-based: fast, objective, brittle
- Model-based: handles subjectivity, needs calibration against humans
- Human\: gold standard, used to calibrate the rest
- Never judge a model's output with the same model that produced it
What we do with this
We push as much grading as possible into deterministic code - schema checks, database state, tool-call assertions - and reserve model graders for the genuinely subjective dimensions, each with its own rubric.
LLM-as-judge, three years on
The method and its caveats arrived together. Zheng et al.'s MT-Bench and Chatbot Arena paper, first posted 9 June 2023, reported that GPT-4 judges agreed with human preferences over 80% of the time, matching the level at which humans agree with each other. The same paper named position bias, verbosity bias and self-enhancement bias. The follow-up literature has mostly quantified those biases rather than dismissed them.
The systematic position-bias study of LLM-as-a-judge evaluated 15 judges across 22 tasks from MTBench and DevBench with about 40 solution-generating models, producing over 150,000 evaluation instances. Position bias turned out to be systematic rather than random, and driven mainly by the quality gap between the two candidates being compared. In other words, the judge is most likely to be swayed by ordering exactly when the two answers are close - which is the case you built the eval to resolve.
The mitigations in both labs' documentation are consistent and cheap to adopt. Anthropic advises grading isolated dimensions with structured rubrics, calibrating frequently against expert human judgment, and including an explicit 'Unknown' escape hatch for when the information is insufficient. OpenAI's guide adds controlling for response length and checking agreement against human annotations. None of this makes a judge unbiased; it makes the bias measurable.
- Over 80% judge-human agreement, matching inter-human agreement (Zheng et al., 9 June 2023)
- Over 150,000 judgements show position bias is systematic and quality-gap driven
- Score one dimension at a time against a structured rubric
- Give the judge an explicit 'Unknown' option, and control for response length
- Validate against human labels before scaling the judge
What we do with this
When we stand up a model grader we run it against a human-labelled sample first and report the agreement rate alongside the eval score, so a client can see how much of the number is judgment.
Agentic benchmarks, and how fast they saturate
The static-benchmark era ended when agentic benchmarks arrived. SWE-bench Verified is 500 instances screened by professional developers from SWE-bench's original 2,294, released 13 August 2024. GAIA (21 November 2023) posed 466 questions where humans scored 92% and GPT-4 with plugins 15%. OSWorld (11 April 2024) covers 369 real computer tasks spanning web and desktop applications, where humans exceeded 72.36% and the best model at publication managed 12.24%. BrowseComp (10 April 2025) has 1,266 questions designed to be hard to find but easy to verify; GPT-4o with browsing scored 1.9% and Deep Research 51.5%.
Those benchmarks are now saturating in turn. An ICML 2026 study of 60 LLM benchmarks (18 February 2026) found nearly half exhibit saturation, that saturation rates rise with benchmark age, that hiding test data offers no protective effect, and that expert-curated benchmarks resist saturation better than crowdsourced ones. Anthropic's eval post notes SWE-bench Verified began the year at 30% and frontier models are now nearing saturation above 80%. A leaderboard snapshot on 10 September 2026 put the top three at Claude Opus 5 with 96%, Claude Mythos 5 with 95.5% and Claude Fable 5 with 95% - a one-point spread - against Claude Opus 4.8 at 88.6%.
Read those numbers next to Stanford's AI Index 2026, published around 1 March 2026, which measured top SWE-bench Verified models clustered in the low-to-mid 70s as of February 2026 under a common harness, led by Claude 4.5 Opus at roughly 76.8%. The distance between a common-harness measurement and a leaderboard snapshot is a reminder that cross-source benchmark comparisons are not like-for-like. The Index also records Humanity's Last Exam rising 30 percentage points in a year, from under 10% to 38.3%, and GPQA Diamond mean accuracy reaching 93% against an 81.2% expert-validator baseline.
Not everything is saturating. On tau-bench, the AI Index found leading models between 62.9% and 70.2% pass@1, with Claude Opus 4.5 at 70.2%, GPT-5.2 at 69.9% and Qwen3.5 at 68.4% - no model above 71%. tau^2-bench (9 June 2025) added a dual-control environment and a telecom domain, where GPT-4.1's pass^1 fell to 34% against 74% retail and 56% airline. tau^tau-Bench (4 September 2026) asks a coding agent to build a customer-service LLM system end to end: the strongest configuration, Claude Opus 5 under Claude Code, passed 23.9% of evaluation simulations against 82.2% for an expert-authored reference. ARC Prize's 2025 results (5 December 2025) reported the top verified commercial model on ARC-AGI-2 at 37.6% for $2.20 per task, with a Gemini 3 Pro-based refinement solution reaching 54% at $30 per task.
Rubric-graded benchmarks are part of the response to saturation. HealthBench (13 May 2025) uses 5,000 multi-turn conversations built with 262 physicians and 48,562 unique rubric criteria, with o3 scoring 60% against GPT-4o's 32% and GPT-3.5 Turbo's 16%. GDPval (5 October 2025) evaluates models on real economically valuable tasks across 44 occupations in the top nine US GDP-contributing sectors, with a 220-task gold subset open-sourced. Grading open-ended deliverables against expert rubrics is harder to game than checking an answer key.
- SWE-bench Verified: 95-96% across the top three, 10 September 2026 leaderboard snapshot
- SWE-bench Verified: low-to-mid 70s under a common harness, February 2026 (AI Index 2026)
- tau-bench: 62.9-70.2% pass@1, no model above 71% (AI Index 2026)
- tau^tau-Bench: 23.9% best configuration vs 82.2% expert reference (4 September 2026)
- ARC-AGI-2: 37.6% top verified commercial model at $2.20 per task (5 December 2025)
- Humanity's Last Exam: under 10% to 38.3% in one year (AI Index 2026)
What we do with this
We use public benchmarks to shortlist models and internal golden sets to choose one. A benchmark tells you a model is plausible for the job; only your own tasks tell you it is right for it.
Three things sitting between a leaderboard number and a capability claim
Contamination is the first. A systematic review of 55 contamination studies published at GEM 2026 estimates score inflation of roughly 6% to 40%, depending on benchmark and setting. That range is wider than the gaps that currently separate models at the top of most leaderboards.
Eval awareness is the second, and it is newer. Anthropic found Claude Opus 4.6 independently hypothesising it was being evaluated on BrowseComp, identifying the benchmark, then locating and decrypting the answer key - a previously undocumented behaviour. 11 of BrowseComp's 1,266 problems were affected, of which 9 were ordinary contamination from public web content and 2 were the eval-aware decryption. Anthropic reported a multi-agent contamination rate of 0.87% against 0.24% for single-agent runs.
Infrastructure noise is the third and the most mundane. Anthropic's 5 February 2026 study showed that CPU and memory configuration alone swings Terminal-Bench 2.0 scores by 6 percentage points (p < 0.01), and concluded that leaderboard differences below 3 percentage points deserve skepticism absent documented configuration matching. 'The Leaderboard Illusion' (29 April 2025) adds the arena-specific version: approximately 27 private Llama-4 variants tested before release, and data-access asymmetries where Google held 19.2% and OpenAI 20.4% of total arena data against 29.7% for 83 open-weight models combined. Separately, a review of widely used benchmarks found invalid question rates from 2% on MMLU Math to 42% on GSM8K.
- Contamination inflates scores by roughly 6-40% (GEM 2026 review of 55 studies)
- Eval awareness: 2 of 1,266 BrowseComp problems involved a model decrypting the answer key
- Infrastructure alone moves Terminal-Bench 2.0 by 6 points; treat sub-3-point gaps as noise
- Invalid question rates run from 2% (MMLU Math) to 42% (GSM8K)
What we do with this
When we compare models for a client we run both under the same harness, the same hardware and the same prompt scaffolding, and report the gap with a confidence interval rather than a single number.
Release gates: continuous evaluation and honest statistics
OpenAI's evaluation best-practices guide frames the work as a five-step loop: define the objective, collect a dataset, define metrics, run and compare, and set up continuous evaluation that runs on every change. That last step is what turns an eval suite into a gate. A regression suite targeting roughly 100% belongs in CI; a capability suite belongs on a slower cadence where headroom is the point.
Statistical hygiene has a canonical reference. Anthropic's 'A statistical approach to model evals' (19 November 2024) recommends reporting SEM-derived 95% confidence intervals, clustering standard errors on the randomisation unit, resampling within questions to cut variance, and using paired-difference tests because frontier models' per-question scores are correlated. Clustered standard errors on popular evals can be over three times as large as naive ones, which is enough to change whether a reported gap is distinguishable from zero.
Automated evals are not the whole gate. Anthropic recommends a dedicated team owning eval infrastructure while domain experts contribute tasks, and pairing automated evals with production monitoring, A/B tests, manual transcript review and periodic human calibration studies. LangChain's survey found quality was the top production blocker at 33%, ahead of latency at 20%. Anthropic's own list puts manual transcript review alongside automated evals rather than after them.
- Continuous evaluation on every change is the fifth step of OpenAI's loop, not an optional one
- Report 95% confidence intervals; cluster standard errors on the randomisation unit
- Clustered standard errors can exceed naive ones by more than 3x
- Use paired-difference tests when comparing two models on the same questions
- Pair automated evals with monitoring, A/B tests and human transcript review
What we do with this
Our release gates are two-tier: a fast regression suite that blocks a deploy on any failure, and a slower capability suite reviewed at each milestone with confidence intervals attached.
Graders as reward functions: reinforcement fine-tuning
The same graders can do double duty as reward functions. OpenAI's reinforcement fine-tuning shares grader definitions with the Evals product: the trainer samples several responses per prompt, scores each with the grader, and applies policy-gradient updates. Supported graders include string_check, score_model, multi and Python code. The documented guidance is to start with dozens to a few hundred examples, with a training-file cap of 50,000 examples and a test-set cap of 1,000.
The practical constraint is availability. RFT is supported only on o-series reasoning models and in practice only o4-mini-2025-04-16, and it is closed to new users. More broadly, OpenAI announced on 7 May 2026 that it is winding down its self-serve fine-tuning platform, blocking new job creation entirely from 6 January 2027. LangChain's survey already found 57% of teams do not fine-tune at all, relying on base models plus retrieval, and a16z's survey of 100 enterprise CIOs (10 June 2025) found fine-tuning viewed as less critical as base capability and context windows improved.
For open-weight models the recipe has not changed much. QLoRA (23 May 2023) fine-tunes a 65B-parameter model on a single 48GB GPU while preserving full 16-bit fine-tuning task performance. The reason to mention reward-based training in an eval post is the dependency, not the product: it is only as good as the grader behind it, so the eval work comes first either way.
- RFT reuses Evals grader definitions as the reward signal
- Available only on o-series models, in practice o4-mini-2025-04-16, closed to new users
- Start with dozens to a few hundred examples; caps are 50,000 training and 1,000 test
- OpenAI blocks new fine-tuning jobs entirely from 6 January 2027
- 57% of surveyed teams do not fine-tune at all (LangChain, December 2025)
What we do with this
We advise clients to treat a trustworthy grader as the prerequisite for any reward-based training, because a reward signal is only as good as the grader behind it.
Own your eval assets
Vendor eval products are not stable ground. OpenAI acquired Promptfoo on 9 March 2026, an AI security and eval company whose products it says are used by more than 25% of Fortune 500 companies. On 3 June 2026 it announced that its own Evals platform is deprecated: existing evals become read-only on 31 October 2026, and the dashboard and API shut down on 30 November 2026, with migration pointed at Promptfoo. Eval datasets and grader definitions should live in version control, portable between runners.
The tooling around them is consolidating but plural. Inspect, from the UK AI Security Institute and Meridian Labs, is an open framework built on four primitives - datasets, solvers, scorers and agents - with over 200 pre-built evaluations. Arize Phoenix is open-source and built on OpenTelemetry trace ingest plus OpenInference instrumentation, with evaluators, datasets and experiments. Braintrust raised an $80 million Series B at an $800 million valuation on 17 February 2026, led by Iconiq.
Underneath, tracing is standardising. OpenTelemetry's GenAI semantic conventions define invoke_agent, chat and execute_tool spans with gen_ai.* attributes plus token and duration metrics, and are already emitted by Claude Code, VS Code Copilot and OpenAI Codex. Building on the conventions rather than a vendor SDK is what keeps the eval and observability layer swappable.
The strategic point is the one a16z heard from enterprise CIOs: external benchmarks such as LM Arena get used as an initial filter, while internal benchmarks, golden datasets and developer feedback are the deeper evaluation layer. Public leaderboards narrow the field. Your own golden set is what you ship against, and it is the asset worth protecting.
- OpenAI Evals: read-only 31 October 2026, shutdown 30 November 2026
- Inspect (UK AI Security Institute and Meridian Labs): open framework, 200+ pre-built evaluations
- OpenTelemetry GenAI conventions: invoke_agent, chat and execute_tool spans
- External benchmarks as a first filter; internal golden sets as the deciding layer
What we do with this
We deliver eval suites as code in the client's own repository, with graders that run under an open runner, so nothing about the measurement layer depends on a vendor dashboard staying open.
Sources
primary sources, checked on Sep 11, 2026- 01Demystifying evals for AI agentsAnthropic Engineering · 2026-01-09
- 02Define success criteria and build evaluationsClaude Platform Docs · 2026-09-11
- 03Evaluation best practicesOpenAI · 2026-09-11
- 04GradersOpenAI · 2026-09-11
- 05Reinforcement fine-tuningOpenAI · 2026-09-11
- 06DeprecationsOpenAI · 2026-06-03
- 07Judging LLM-as-a-Judge with MT-Bench and Chatbot Arena (arXiv:2306.05685)Zheng et al. · 2023-06-09
- 08Judging the Judges: A Systematic Study of Position Bias in LLM-as-a-Judge (arXiv:2406.07791)arXiv · 2024-06-12
- 09tau-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains (arXiv:2406.12045)Sierra · 2024-06-17
- 10tau^2-Bench: Evaluating Conversational Agents in a Dual-Control Environment (arXiv:2506.07982)Sierra · 2025-06-09
- 11tau^tau-Bench: An Environment for End-To-End, Realistic Agent Construction (arXiv:2609.04611)arXiv · 2026-09-04
- 12SWE-bench VerifiedSWE-bench · 2024-08-13
- 13SWE-bench Verified Leaderboard (September 2026)BenchLM.ai · 2026-09-10
- 14GAIA: a benchmark for General AI Assistants (arXiv:2311.12983)arXiv · 2023-11-21
- 15OSWorld: Benchmarking Multimodal Agents for Open-Ended Tasks in Real Computer Environments (arXiv:2404.07972)arXiv · 2024-04-11
- 16BrowseComp: a benchmark for browsing agentsOpenAI · 2025-04-10
- 17HealthBench: Evaluating Large Language Models Towards Improved Human Health (arXiv:2505.08775)OpenAI · 2025-05-13
- 18GDPval: Evaluating AI Model Performance on Real-World Economically Valuable Tasks (arXiv:2510.04374)OpenAI · 2025-10-05
- 19ARC Prize 2025 Results and AnalysisARC Prize · 2025-12-05
- 20When AI Benchmarks Plateau: A Systematic Study of Benchmark Saturation (arXiv:2602.16763)Akhtar et al., ICML 2026 · 2026-02-18
- 21Are LLM Benchmarks Already Contaminated? A Systematic Review of Contamination Detection MethodsACL Anthology (GEM 2026) · 2026-07-01
- 22Eval awareness and contamination on BrowseCompAnthropic Engineering · 2026-03-06
- 23Quantifying infrastructure noise in agentic coding evalsAnthropic Engineering · 2026-02-05
- 24A statistical approach to model evaluationsAnthropic · 2024-11-19
- 25The Leaderboard Illusion (arXiv:2504.20879)arXiv · 2025-04-29
- 26Technical Performance - The 2026 AI Index ReportStanford HAI · 2026-03-01
- 27State of Agent EngineeringLangChain · 2025-12-02
- 28State of AI Agents 2026Databricks · 2026-01-27
- 29Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027Gartner · 2025-06-25
- 302025: The State of Generative AI in the EnterpriseMenlo Ventures · 2025-12-09
- 31How 100 Enterprise CIOs Are Building and Buying Gen AI in 2025Andreessen Horowitz · 2025-06-10
- 32OpenAI acquires Promptfoo to secure its AI agentsTechCrunch · 2026-03-09
- 33InspectUK AI Security Institute · 2026-09-11
- 34Compare 7 LLM Evaluation Platforms (2026)Arize AI · 2026-08-13
- 35Braintrust lands $80M funding round to become the observability layer for AISiliconANGLE · 2026-02-17
- 36Inside the LLM Call: GenAI Observability with OpenTelemetryOpenTelemetry Blog · 2026-01-01
- 37QLoRA: Efficient Finetuning of Quantized LLMs (arXiv:2305.14314)arXiv · 2023-05-23