AssistantBench: 214 Realistic Web Tasks for Assistant Agents
The benchmark designed around what users actually ask assistants to do: multi-step web research with a verifiable answer.
Construction
The Tel Aviv University team built AssistantBench by sourcing tasks from three streams: (1) MTurk worker submissions of recent tasks they actually wanted help with, (2) university administrator workflows (course catalogue lookups, scholarship eligibility checks), and (3) author-curated tasks designed to stress specific failure modes. Each task ships with a gold answer extracted by humans and a verification protocol.
The benchmark targets tasks that require live web research rather than recall. Closed-book GPT-4 with browsing disabled still reaches 16.5% with an instruction prompt and 22.2% with a one-shot example, higher than any pure web agent, but the paper shows the figure is misleading: 85% of those closed-book errors are hallucinated answers, so the model scores on a high answer rate rather than genuine knowledge of the web.
Reading the scores
The launch paper's anchors are clear. The best result, 25.2%, comes from an ensemble that runs the SeePlanAct (SPA) web agent and falls back to a closed-book model when the agent abstains. SPA alone scores 11.1%, the earlier SeeAct web agent only 4.1%, and browsing-disabled closed-book GPT-4 reaches 16.5 to 22.2% (higher than the pure web agents, but mostly by hallucinating). No system passes 26%. We do not reprint a per-model table of current scores, because a responsibly-sourced one cannot be published here: there is no continuously-maintained board we re-verify, current numbers come from vendor reports under different browser harnesses, and the live-web design means a task's gold answer can change between runs, so 2024 and 2026 numbers are not strictly comparable.
For current results, read the official AssistantBench project page and each submission's harness together. To choose the right benchmark for your use case rather than chase a single figure, start from the homepage task picker.
Limitations
Live-web evaluation has a reproducibility cost. A 2024 task that asked for the rent of a specific listing has a different gold answer in 2026 because the listing changed. The AssistantBench team partly addresses this by snapshotting page contents at task creation time, but agents in the live browser see the current page, not the snapshot. This means scores from 2024 papers and 2026 papers are not strictly comparable for time-sensitive tasks.
Q.01What does AssistantBench test?+
Q.02What is the headline score?+
Q.03How does AssistantBench score answers?+
Q.04Why is GPT-4 stuck below 30%?+
Q.05How is this different from WebArena and Mind2Web?+
Sources
- [1] Yoran et al. (2024): arxiv.org/abs/2407.15711
- [2] AssistantBench project: assistantbench.github.io