Why does the same model score differently in different agent harnesses?

Because the harness decides what the model actually sees at each step, and that alone can move a score with the weights never touched. A 2026 study compared two configurations of the same harness: the control kept the full conversation in time order, and the treatment bundled two changes together, mechanically shortening older tool results as context filled and responding to repeated or stalled work. On a 169-task SWE-bench Verified slice run under a tight 20,480-token window, the treatment raised the model’s mean per-task fail-to-pass fraction, a continuous partial-credit score, from 28% to 49%, and raised complete solutions, a separate binary count, from 43 to 72.

The study is a single-author preprint and measures the combined effect of that treatment package, not any one rule inside it; the paper itself leaves isolating the detector response’s own contribution to future work. Applying the same frozen package to three other models, with no retuning, raised their scores too, so the effect was not specific to one model’s quirks.

A benchmark score is reported for the model-and-harness pair run together, and this is why: change only the harness, and the pair produces a different number.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y