Uh oh!
There was an error while loading. Please reload this page.
docs(eval): record the four-arm Terminal-Bench 2.1 comparison - #2208
Merged
Conversation
Astro-Hanforce-pushed
the
docs/eval-4arm-tbench-2.1-deepseek-v4-flash
branch
from
August 5, 2026 06:44
b576e95 to
0fe3d48CompareFour harnesses around one DeepSeek V4 Flash model over all 89 tasks, every arm inside the task container under the same budget and package mirror. Codex leads on pass@1 at 70/89 against Maka's 65/89, but the exact McNemar test puts that five-task gap at p = 0.359 -- only the Codex advantages over Claude Code and Reasonix reach significance. Maka records the lowest cost per pass. On the 60 tasks where no arm ran out of budget the top three invert and sit within 3.33 points of each other, so the headline spread tracks whether an arm finishes rather than whether it can solve the task.
Astro-Hanforce-pushed
the
docs/eval-4arm-tbench-2.1-deepseek-v4-flash
branch
from
August 5, 2026 07:00
0fe3d48 to
7b28ae3Compare…ext steps The Experiment table stated a flat 900 s per-cell budget. The run used the task-native agent timeout at x1, which is 900 s on 48 of the 89 tasks and ranges from 600 s to 12000 s elsewhere. Every statement resting on that number is corrected. Adds the frozen setup, outcome accounting, integrity hashes, and artifact pointers the earlier Maka vs OpenCode report carries, plus exclusive outcomes and two analysis sections. The failure decomposition behind them is new: of the 12 tasks Codex won alone, 8 are Maka verification failures and only 4 are deadline losses, so the larger half of the gap is answer correctness rather than unfinished work.
Astro-Han
marked this pull request as ready for review
August 5, 2026 08:52
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Records the four-arm Terminal-Bench 2.1 comparison of Maka, Codex, Claude Code, and Reasonix around one DeepSeek V4 Flash model, over all 89 tasks. Every arm ran inside the task container under the same executor, the same task-native deadline policy, and the same package mirror, so the harness is the only variable that moves.
Codex leads on pass@1 at 70/89 (78.65%) against Maka's 65/89 (73.03%), but the exact two-sided McNemar test puts that five-task gap at p = 0.359, and an independent earlier run over the same suite flips 19% of Codex's own tasks while moving its net score by 3. Maka records the lowest cost per pass at $0.03215, on 61% of Codex's input tokens, and the fastest median cell at 332.8 s.
The diagnostic decomposition is the part worth reading: on the 60 tasks where no arm exhausted its budget, the top three invert and land within 3.33 percentage points of each other (Claude Code 90.00%, Codex 88.33%, Maka 86.67%). Claude Code has the highest conditional pass rate and the lowest headline score because it ran out of budget on 26.97% of the suite.
The report follows the structure of the earlier Maka vs OpenCode report: frozen setup, outcome accounting, integrity hashes, and artifact pointers. It adds exclusive outcomes, a positioning section stating what the run does and does not establish about Maka, and a next-steps section.
Refs #1970
Verification
task.toml: 900 s on 48 tasks, 1800 s on 17, 3600 s on 13, 1200 s on 5, 2400 s on 2, and one each at 600, 750, 7200, and 12000 s. Every dependent statement is updated.passed/budget_exhausted/infra_failedfields rather than from a duration threshold, and cross-checked against the report body: 89 rows, per-arm totals match every number in the prose.task_completedevents), and deadline-share ratios computed against each task's own[agent] timeout_sec.shasum -a 256over the archived evidence and the committed CSV.Review focus
Three things are stated in the report rather than resolved:
default-headless) and the only arm running a tool-result prune policy. This is disclosed as a live harness asymmetry; the run has no prompt-off or prune-off control.