Introducing Terminal-Bench 2.0 and Harbor
tbench.ai · 355 words · saved by 1 readers
A benchmark for terminal agents
Today we are releasing Terminal-Bench 2.0 and Harbor: a harder, better verified version of Terminal-Bench and a new package for evaluating and optimizing agents. Harbor While building Terminal-Bench we kept hearing about the same set of problems from agent developers. Namely: Evaluating in containers is slow, how can we scale horizontally to thousands of containers in the cloud? How can we not only evaluate but also improve agents via SFT, RL, and prompt optimization? With so many frameworks for building agents and benchmarks for measuring them, how do we build tools that generalize across dep
related reading
- GitHub - harbor-framework/terminal-bench-science: Terminal-Bench-Science: Evaluating AI agents on research workflows across scientific domainsgithub.com
- Quantifying infrastructure noise in agentic coding evals \ Anthropicanthropic.com
- Composer2.pdfcursor.com
- TERMINAL-BENCHtbench.ai
- Senior SWE-Benchsenior-swe-bench.snorkel.ai
- Continual Learning Bench 1.0 — Newscontinual-learning-bench.com
- Every Benchmark is Brokenjonathanpgabor.substack.com
- BenchmarkList: Track the Frontier of AI Capabilitiesbenchmarklist.com
- FrontierSWEfrontierswe.com
- Adithya S K on X: "RL Coding Environments 101: Why Harbor Exists" / Xx.com
- VeRO: A Harness for Agents to Optimize Agentsarxiv.org
- [2602.12316] GT-HarmBench: Benchmarking AI Safety Risks Through the Lens of Game Theoryarxiv.org