Back to Gap Map Model components / Benchmark / eval datasets

Terminal-Bench

Laude Institute
open / Overall score: 4.0(strong)

Benchmark of difficult, hand-vetted tasks that agents must complete in a real terminal, from compiling and debugging code to system administration. It runs as a continuous benchmark with tagged releases (2.0, 2.1, 3.0) mirrored on Hugging Face and executed through the Harbor framework, with an audited leaderboard at tbench.ai. Frontier agent builders use it to track progress on long-horizon terminal work.

The org renamed from laude-institute to harbor-framework and the original repo is now terminal-bench-1; the product's numbers are the official harborframework Hub mirrors, whose 2.0 card states it is a read-only mirror of the GitHub source. PyPI terminal-bench is the legacy harness, superseded by harbor, and is left undeclared.

Openness

5 high confidence
5.0
license
Apache-2.0(repository LICENSE body read (terminal-bench-1)
every version repo and all three Hub mirrors carry license
apache-2.0)
access
open(ungated Hub mirrors ("gated":false) and public GitHub task sources)
answers
released(tasks include oracle solutions and tests, run and graded locally by Harbor
datasheet
present(Hub dataset cards on each release mirror plus tbench.ai docs and repository CONTRIBUTING/task rubric)

Terminal-Bench's tasks and harness are Apache-2.0, the Hub release mirrors are ungated and carry dataset cards, and oracle solutions ship in the repository. The governing release is recorded as the newest published mirror, 3.0, though every tagged release carries the same license, so that choice does not change the reading.

Adoption

4 high confidence
4.0

Adoption is measured by Hugging Face downloads summed across the three official harborframework release mirrors: terminal-bench-2.0, 2.1 and 3.0. Third-party mirrors of the dataset are excluded from the count, and so is the legacy PyPI harness, which measures installs of the old evaluation tool rather than use of the dataset.

Capability

not assessed

A dataset is not 'capable', so capability is left unscored, mirroring the category pattern (gsm8k).

Verified 2026-10-07, except some scores, still awaiting re-confirmation