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.
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 benchmark environments misrepresent deployment readiness?
- Which separable capability axes reveal when single benchmarks misrepresent deployment readiness?
- Can a single leaderboard score capture multi-dimensional differences in agent performance?
- What realism standards should compliance benchmarks meet to avoid evaluation gaming?
- Can a single benchmark score capture both progress and readiness?
- Can a single agent benchmark score accurately represent deployment readiness?
- Why do single-axis benchmarks fail to measure deployment-ready agent capability?
- What role does online RL play in scaling GUI agents?
- How can agent data flywheels improve task quality iteratively?
- What makes an agent mechanism reusable versus benchmark-specific?
- Can context management be optimized for an agent without retraining or changing the model?
- How do parametric and non-parametric updates differ in agents?
- Which foundation model tiers most benefit from harness updates?
- How do evolved harness edits generalize across different benchmark domains?
- How much realized agent capability comes from the harness versus the model?
- How do prompt optimization and code harnesses compare for capability transfer?
- What should an external contract for model improvement actually contain?
- How do agentic systems hide harness failures from benchmarks?
- What makes a harness low-friction for model strategy?
- Can weaker models match stronger ones by reorganizing harness-side components?
- Which domains see models exceed human harness design quality?
- Why do useful harness updates often disappear during model evolution?
- How much does executor choice change a harness's actual performance?
- Do models co-adapt their harnesses to specific executor strengths?
- Can mid-tier models benefit more from harness improvements than frontier models?
- Does harness scaling represent a fundamentally different path than model scaling?
- How much does harness design contribute to reported model capability scores?
- How does harness structure affect planner token efficiency compared to model size?
- What role does effective feedback compute play in agent harness scaling?
- Does harness optimization generalize across different benchmarks and agent architectures?
- Can weaker models benefit equally from harness updates as stronger ones?
- How fast do new benchmarks get adopted across the AI research community?
- What distortions do automated benchmarks introduce compared to real tasks?
- How do fast skill injection and slow gradient updates work on different timescales?
- What makes frozen model reasoning different from weight-based parameter updates?
Related concepts in this collection 5
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Where does agent reliability actually come from?
Exploring whether LLM agent performance depends on larger models or on thoughtful system design choices like memory, skills, and protocols that shift cognitive work outside the model.
states the harness thesis; this paper adds benchmark accuracy gains and a state-and-runbook mechanism
-
Does raw token spending actually predict agent performance?
Standard measures of agent effort—tokens, tool calls, operations—may not capture what makes inference-time scaling work. This explores what actually drives performance gains when agents spend more compute.
locates harness gains in retained, informative feedback; StateM's lesson reactivation and durable state fit that account
-
What predicts success in ultra-long-horizon agent tasks?
Does an agent's initial solution quality matter more than its willingness to iterate? AUTOLAB's frontier-model benchmark suggests persistence through feedback loops may be the true differentiator.
premature stopping appears in both as a failure of long-horizon agents
-
Do stronger models always evolve harnesses better?
We explore whether base model capability predicts both the ability to write useful harness updates and the ability to benefit from them. The answer reshapes how we should allocate capability in self-evolving agent systems.
same fixed-weights harness setting; StateM's cross-model gains are not ordered by tier, so the tier question stays open
-
How should we measure agent system performance beyond task success?
Current evaluation metrics collapse agent behavior into a single success score, hiding critical information about how agents operate. What dimensions—trajectory quality, memory use, context efficiency, verification cost—should benchmarks actually measure?
StateM reports accuracy and cost only, the scalar view this note says hides harness behavior
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- StateM: Reaching 95.3% Raw Accuracy, or a \$15 Frontier Run, on Terminal-Bench 2.1 via Harness Scaling
- DarwinX: Evolving Agent Harnesses Through Natural Selection
- Harness Updating Is Not Harness Benefit: Disentangling Evolution Capabilities in Self-Evolving LLM Agents
- HarnessDev: Can LLMs Create and Evolve Their Own Agent Harness?
- Scaling Laws for Agent Harnesses via Effective Feedback Compute
- RRSI: Regularized Recursive Self-Improvement of Agent Harnesses
- From Model Scaling to System Scaling: Scaling the Harness in Agentic AI
- Rethinking the Evaluation of Harness Evolution for Agents
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