AI CompendiumA public chart of the language
Home / Evaluation / Agent Benchmark
Evaluation

Agent Benchmark

also called Agentic benchmark, Tool-use benchmark

A benchmark that scores an agent on real work in a terminal or codebase, not on answering questions.

Definition

A benchmark designed for agents rather than chat models: instead of asking questions with known answers, it gives the model a real environment, a terminal, a repository, a browser, and scores whether it completes tasks. Terminal-Bench, ProgramBench, and DeepSWE are the current examples: they measure multi-step work like running commands, editing programs, and finishing automation jobs. They are why recent model updates report their biggest gains on agent tasks rather than on question answering.

Agent benchmarks are harder to game and harder to run than Q&A benchmarks. A task can pass by accident, fail on environment quirks, or take minutes of tool calls, so results depend on the harness and the agent scaffold as much as on the model. Two models compared on different scaffolds are not really compared at all, which is why the harness name belongs next to every score you quote.

The October 2026 DeepSeek V4.1-Flash-1017 update is a good illustration of what these benchmarks reveal: vendor numbers showed Terminal-Bench 4.0 jumping from 31.2 to 42.3 and ProgramBench from 20.3 to 29.1 against the September checkpoint, while question-answering scores moved far less. That pattern, big agent-task gains and small Q&A gains, is the signature of post-training aimed at tool use.

How people use it
Deciding whether a model upgrade matters for an agent product.
"Ignore the headline Q&A scores. If the agent benchmarks moved on terminal and program tasks, that is the number that predicts our product."
Worked example

Quoting a vendor table honestly

A vendor announces a new checkpoint with big agent-benchmark gains.

Write the harness next to every number before you repeat it. DeepSeek ran Terminal-Bench with the Claude Code harness and DeepSWE with the mini-SWE-v2 harness, so a score from one table is not comparable to a score from a different harness. Then re-run your own eval set in the scaffold you actually ship, and let that number, not the vendor table, decide whether the upgrade matters.

Avoid

Comparing agent benchmark scores across different harnesses or scaffolds. The scaffold is part of the measurement, and a score without it is not comparable.

Sources
Related terms