Harness Leaderboard
Which coding-agent harness should you run your open model in?
Same model, same provider, same reasoning effort, three attempts with confidence intervals, every trajectory public.
Accuracy vs. cost
Each dot is a harness running the same model. Up and to the left is better. The highlighted staircase is the Pareto frontier: harnesses no other harness beats on both accuracy and cost. Hover a dot for its numbers, confidence interval included.
Leaderboard
Click a column to sort. Highlighted cells are the best value in each column. Per-trial values average over scored trials. Tokens, calls and model time are measured outside the harness by the same metering proxy; agent time is Harbor's timer around the harness process.
Harness vs. noise
A task flips when one attempt passes and the other fails. If swapping the harness flips no more tasks than re-running the same harness, the harness choice changes little beyond chance.
Runs
Each run executes on HF Jobs. Trials reused from earlier runs are copied, not re-run. Click a run for per-benchmark progress and its cost & time files.
Trajectory scan
atif-scan over the trials this view scores, per harness: how many trajectories it read, and the flagged trials (critical, high or medium severity), split by how the board counts them. Below, the review queue.
Method
Everything that could favour one harness is pinned or equalised.