terminus2 harness.
How it works
- Load tasks. With the default dataset address, AgentCompass downloads Terminal-Bench 2.1 through the Harbor CLI. An explicitly configured regular Git source is shallow-cloned instead.
- Run the agent. The environment recipe selects the image declared by each task and starts the agent in its prepared terminal workspace.
- Verify the result. The task’s
tests/test.shis run through the Harbor verifier. A reward of1marks the taskcorrect.
Parameters
You can run all tasks in the default dataset without--benchmark-params. For task selection and aggregation options, see the shared Benchmark parameter reference. Configure phase deadlines and timeout multipliers through --execution-params; see run controls.
Run examples
agentcompass run takes three positional arguments in order: Benchmark, Harness, and Model. The examples use terminal_bench_2_1; harness choices are described below.
Before running, make sure local Docker is available and set MODEL_NAME, MODEL_BASE_URL, and MODEL_API_KEY to the model under test, API endpoint, and API key.
Recommended harness
The recommended terminal agent isterminus2.
- Smoke test (single task end-to-end)
- Custom parameters
- AgentCompass recommended config
Run the
filter-js-from-html task to verify container preparation, inference, and scoring, leaving other parameters at their defaults.Other optional harnesses
The commands below evaluate the full dataset. Configure the model variables for an OpenAI Responses API endpoint when using Codex, or an Anthropic Messages API endpoint when using Claude Code.codex and claude_code are two other harness options. Pass --recipe terminalbench2_1_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
- Use AgentCompass images
Omit
--recipe to use the official task image. Because it does not include the Node bootstrap dependencies, provide the matching installation command explicitly.Evaluation Results
For shared result conventions, see Run Directory, Aggregate Scores, and Task Files and Shared Fields.Scoring Metrics
Terminal-Bench 2.1’s primary metric is binarycorrect, recording the verdict from the verification flow above. A verifier reward of exactly 1 maps to true; other valid reward values map to false. There is no partial credit.
With the default configuration, each task has one attempt and the overall score is the pass rate over tasks with valid scores, ranging from 0 to 1; higher is better.
See Metrics and Aggregation for repeated attempts, category aggregation, and scoring failure rules.
Task Results and Scoring Evidence
eval_raw_data under meta.benchmark preserves the Harbor verifier’s scoring evidence:
