terminus2.
How it works
- Load tasks. On its first run, AgentCompass shallow-clones the Terminal-Bench 2.0 repository from GitHub into the data directory. Each task supplies its instruction, container definition, and verifier.
- Run the agent. The task’s container image and resource requirements are applied by the environment recipe. The task instruction is passed to the harness, which operates in the prepared terminal workspace.
- Verify the result. The benchmark runs the task’s
tests/test.shthrough the Harbor verifier. A verifier reward of1is recorded ascorrect.
Parameters
Configure Terminal-Bench-specific options with--benchmark-params '{...}'.
Run examples
agentcompass run takes the benchmark id, harness id, and model id in that order. The default configuration uses the local docker environment; the recipe applies each task’s image automatically.
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.
Recommended harness
The recommended terminal agent isterminus2.
- Smoke test (single task end-to-end)
- Custom parameters
- AgentCompass recommended config
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_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.
- Run with the official image
- AgentCompass recommended config
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 viewssummary.md and metrics.json under the run directory.
Aggregate metrics (summary.md)
The primary metric is binarycorrect: 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 atattempts.<N>.metrics.correct, together with execution status, the agent trajectory, Harness diagnostics, and raw verifier evidence. See Results.