agent-readings / Evaluation and Benchmarks
Live-site agent evaluation with intercepted effects and trace-grounded verdicts
The one sentence
It treats browser-agent evaluation as an infrastructure problem spanning isolation, effect control, recording, reference collection, and outcome verification rather than as action prediction over static pages.
Before this paper
Static-trace web benchmarks evaluate action prediction over recorded pages rather than end-to-end task execution.
Self-hosted web environments improve reproducibility but omit production-site drift, authentication flows, anti-automation systems, and platform-specific validation.
Earlier live-web benchmarks primarily emphasize read-only information retrieval instead of purchases, reservations, applications, and detailed form submissions.
The missing capability is a safe, auditable way to measure whether an agent can complete heterogeneous, state-changing daily web workflows on production websites.
Core idea
Collect broad everyday write-heavy tasks, have a human complete each task to identify the terminal committing request, run every model-task pair in a fresh instrumented browser container, block the matching terminal request at runtime, and score the retained...
Gather realistic write-heavy tasks from everyday website use and filter out read-only, unavailable, geographically restricted, paid,...
Formalize each retained task as a task card with required personal data, expected final state, and a terminal submission target.
Record a human reference run and annotate the terminal request's URL pattern, method, and required payload fields.
Launch each model-task pair in a fresh isolated container with a clean Chromium profile, fixed resources, shared task data, and common browser...
Action grammar
task card: instruction, starting URL, user data, expected final state, and terminal request schema.
observation: accessibility tree, DOM snapshot, or screenshot exposed through the browser harness.
action: navigate, click, type, scroll, observe, take_screenshot, or wait.
terminal request: URL pattern, HTTP method, and required payload fields that would commit the task.
Executable shape
Evidence
The paper reports 153 tasks across 144 live production websites, organized into 8 high-level groups and 15 fine-grained categories.
Tasks involve purchases, reservations, applications, account updates, and detailed form submissions on production websites, carrying user-specific data through platform...
The interceptor blocked every annotated terminal request reached in the 153 human reference runs and produced zero false-positive blocks on recorded navigation traffic.
The five-layer trace is session video, action screenshots, HTTP traffic, agent messages, and browser actions; Agent-as-Judge compares it with the human reference and intercepted...
Claim map
The paper's benchmark contains 153 everyday tasks spanning 144 live production websites and 15 fine-grained life and work categories.
ClawBench evaluates write-heavy, state-changing workflows on live production websites rather than action prediction on static traces or interaction only in...
The final-request interceptor captured and blocked every annotated terminal request reached in the 153 human reference runs, with zero false-positive blocks...
Every run is recorded as five synchronized evidence layers and judged against a human reference trajectory with an outcome-oriented binary protocol.
Agent infrastructure
A browser-agent benchmark measures a model-plus-harness system; the harness, prompt, browser configuration, and action interface must be held constant...
Effect control is strongest at a narrow, machine-checkable boundary: the terminal network request is easier to audit and block than an agent's stated...
The safety envelope is task-scoped. Workflows with multiple irreversible intermediate effects should be excluded rather than treated as covered.
Auditability requires synchronized evidence from the UI, network, agent transcript, low-level actions, and full-session replay.
Caveats
Live production websites trade rerun determinism for ecological validity; layouts, A/B tests, region, account state, and anti-automation systems can...
Final-request interception is not a general browser sandbox and only covers the audited terminal endpoint for each task.
Live sessions, model calls, network instrumentation, and trace-based judging make repeated trials and ablations more expensive than static benchmarks.
Reported model scores are conditioned on the shared OpenClaw harness and should not be read as model-only capability measurements.
Run it
No separate PoC is added here. The public ClawBench repository contains the runnable benchmark infrastructure, task definitions, harnesses, and evaluation tooling.