Terminal-Bench 4.0
Terminal-Bench 4.0 is the latest Harbor Framework terminal agent benchmark. Keep separate from Terminal-Bench 2.1 and 3.0; DeepSeek reports scores with DeepSeek Harness Minimal mode and a 1M-token context window.
Models ranked
8
tracked on this benchmark
Score band
65.7 – 28.8
best → lowest tracked
Snapshot trend
+20.90
Oct 17 → Oct 23 · 1 models
Leaderboard
Tracked models ranked by Pass@1 (higher is better).
Notes: Moonshot self-reported launch table, row 'Terminal-Bench 4.0', column 'Kimi K3.1 Pro (max)'. Settings: reasoning effort max, temperature 1.0, top-p 0.95 (blog footnote). Footnote: 'Kimi K3.1 Pro is evaluated with the Claude-Code harness.'
Configuration: Claude Mythos 5.1 (max thinking effort)
Notes: System card §8.6 (p.171): Claude Code --bare mode, max thinking effort, averaged over 10 trials per task (660 trials), SE ~±1.6-2 pts. Launch-page chart data (https://www.anthropic.com/claude-fable-and-mythos-5-1) lists Mythos 5.1 max = 60.9 at $18.0/task. Table 8.1.A shows shared Fable 5.1/Mythos 5.1 column 56% (61%); the 60.9 figure is the Mythos-specific value. Retrieved 2026-10-17.
Configuration: MiniMax M3.1 Flash
Notes: MiniMax M3.1 Flash launch blog (2026-10-19) main benchmark table image m31-flash-en-2 (webp converted to png; values transcribed by eye from table) incl. footnotes. Footnote: 'using the Codex 0.149.1 harness.' Retrieved 2026-10-19.
Notes: Harness conflict: the September V4.1 Flash card names DeepSeek Harness Minimal mode for Terminal-Bench 4.0, while the 1017 card and the 2026-10-17 changelog name Claude Code for the comparison table. Version kept per the base card.
How to read this benchmark
This benchmark scores models where higher is better. Use scores for directional filtering and shortlisting, not universal quality ranking; then validate pricing, context window, provider availability, and fit for your workload.
Trust this score when
- There is a fresh timestamped snapshot (or multiple snapshots) for this benchmark.
- The model list covers the same version family you can actually deploy today.
- Top candidates overlap with your required routing and feature requirements.
Be cautious when
- There is only one benchmark snapshot or the dataset appears stale.
- The benchmark metric direction is opposite of your decision objective.
- The score difference between options is narrow and likely within implementation variance.
Related benchmarks
Last reviewed: Sep 10, 2026