SYNTHESIS NOTE
Topics›Evaluations›this note

Can execution harnesses lift model performance without retuning weights?

Explores whether improving an agent's runtime system—not the model itself—can boost benchmark accuracy and transfer across different model versions without modification.

Synthesis note · 2026-09-25 · sourced from Evaluations

The StateM paper reports that improving the execution system around an agent, "without changing its model weights," raises benchmark accuracy across several models. On Terminal-Bench 2.1, GPT-5.5 xhigh with StateM reaches 92.1% against an 83.1% reference, above GPT-5.6 Sol Ultra at 91.9%. The same runbook "transfers to GPT-5.6 without modification," where the system records 95.3% raw accuracy across 445 public-submission trials and succeeds at least once on each of the 89 tasks. The frozen profile lifts GPT-5.6 Luna from 76.7% to 85.4%, numerically above the 84.9% Sol xhigh reference. Starting from the same runtime, runbook structure, and golden rules, under $38 of adaptation cost moves DeepSeek-V4 Flash from 82.7% to 88.1% under standard timeouts.

The paper's diagnosis is that long-horizon agents "can fail even when their underlying models can solve the constituent steps." The failures it lists are losing track of mutable state, failing to reactivate lessons from earlier executions, skipping known procedures, and stopping prematurely. StateM answers with durable states, phase-local context, checked transitions, recoverable runbooks, and versioned procedural practices that agents and users can inspect together. The discussion adds a design requirement: the runtime must be "agent-native and enforceable" and also cheap to modify. Conventional state-machine and graph runtimes push reasoning into manually constructed nodes, edges, and handlers, so changing the control policy becomes "an engineering task of its own" and failure-driven iteration gets heavy.

The paper frames harness scaling as orthogonal to model scaling, asking whether "more of a model's existing capability" can be converted into completed, reliable work. That is the thesis of Where does agent reliability actually come from?, and StateM adds a benchmark-level result and a concrete mechanism: state, procedures, and lessons kept outside the model and enforced at transitions. Its named failure of reactivating earlier lessons echoes Does raw token spending actually predict agent performance?, where feedback counts only if it is retained for later decisions. Its premature-stopping failure is the same behavior What predicts success in ultra-long-horizon agent tasks? finds in most frontier models. On transfer, it complements Do stronger models always evolve harnesses better?: gains appear for Sol, Luna, and DeepSeek-V4 Flash, but the excerpt does not order these by capability tier, so it neither confirms nor contradicts a mid-tier peak.

The excerpt is silent on several points that matter for the claim. It shows no ablation, so it cannot say which of the five components produces the gains. It reports no variance, and the 92.1% versus 91.9% comparison is a 0.2-point difference. It does not say what the 83.1% and 84.9% references consist of. It lists only two of the three "progressively stronger empirical tests." The "$15 frontier run" in the title gets no detail, and transfer is shown only within the GPT-5.6 family plus a fresh adaptation for DeepSeek. It reports accuracy and cost, not trajectory quality, so it cannot speak to How should we measure agent system performance beyond task success?. At the strength the excerpt supports, the results are consistent with control-layer failures being a real share of what a capable model loses on long tasks, and the full paper is needed to say which parts of the harness do the work.

Inquiring lines that read this note 49

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

Why do standard benchmarks fail to predict agent deployment success? How do agent-learned skills transfer and improve across different tasks? What should agent evaluation prioritize to reveal reliable behavior? How does harness optimization generalize across different model architectures and domains? How do capability benchmark scores systematically misrepresent true model abilities? What capability trade-offs arise from domain specialization through fine-tuning? Do reasoning benchmarks predict model performance in long-horizon workflows? Can harness architecture and protocols provide agent reliability without model scaling? What trajectory-level metrics beyond task success best evaluate agent performance? What fundamental constraints limit how effectively agents can improve themselves? Can local safety checks guarantee system-level behavioral safety? How do surface patterns enable correct outputs but reduce robustness? How do standardized protocols improve multi-agent coordination and reliability? Should agents decouple planning from perception grounding for better performance? Why can recurrent transformers achieve reasoning capabilities that standard transformers cannot? Why can't prompting alone inject genuinely new knowledge into models? How do evaluation practices shape which failures stay visible? How should agents manage memory granularity to improve long-term performance?

Related concepts in this collection 5

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
13 direct connections · 81 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

harness scaling lifts fixed models on Terminal-Bench 2.1 without touching weights — the same runbook transfers to a newer model unchanged