Skip to main content
Terminal-Bench 2 Verified is the verified Terminal-Bench 2 subset hosted on Hugging Face. It follows the same task execution and verifier flow as Terminal-Bench 2, normally with terminus2.

How it works

  1. Load tasks. AgentCompass clones the Hugging Face dataset and retrieves its Git LFS objects before loading the task directories.
  2. Run the agent. The recipe prepares each task’s container image and workspace, then the terminal harness solves the instruction.
  3. Verify the result. The Harbor verifier executes tests/test.sh; a reward of 1 marks the task correct.
git-lfs must be installed in the process that loads the dataset. Without it, the verified task assets cannot be retrieved.

Parameters

Configure Terminal-Bench-specific options with --benchmark-params '{...}'.

Run examples

Use --benchmark-params for dataset and judge settings, --harness-params for agent and tool settings, and --execution-params for phase timeouts and multipliers. YAML uses benchmark.params, harness.params, and execution; explicit CLI values override YAML values. The recommended terminal agent is terminus2.
Verify the end-to-end flow works — sample_ids selects which case to run, with all other parameters using their defaults.

Other optional harnesses

codex and claude_code are two other harness options. Pass --recipe terminalbench2_verified_docker_ac to use the AgentCompass prebuilt image. It includes download dependencies such as Node.js, npm, curl, and wget for Codex, Claude Code, and similar harnesses.
Omit --recipe to use the official task image. Because it does not include the Node bootstrap dependencies, provide the matching installation command explicitly.

Output

A run writes per-task details and the aggregate views summary.md and metrics.json under the run directory.

Aggregate metrics (summary.md)

The primary metric is binary correct: the Harbor verifier’s full reward (1) maps to true. At k=1, correct.native@1 is Terminal-Bench’s pass rate over evaluated observations. At k>1, the generic reducers can emit correct.avg@k and correct.pass@k, each with independent counts.

Per-task details (details/)

Each task JSON stores the binary observation at attempts.<N>.metrics.correct, together with execution status, the agent trajectory, Harness diagnostics, and raw verifier evidence. See Results.