How the Same GPT‑5.6 Model Jumped from 7.8 to 93.3: The Rise of Agent Harnesses
The Twin paper shows that fixing the base GPT‑5.6 model while swapping different harnesses can boost performance from 7.8 to 93.3, proving that an Agent’s true capability now depends on the combined system of model and harness rather than the model alone.
01 – Separating Model Ability from Agent Ability
The Twin study evaluates a single GPT‑5.6 Sol model under four execution setups: Direct Play (score 7.8), Codex Harness (61.1), Prime Agent (78.3), and Twin Harness (93.3). All use the same base model, but the harnesses differ in how they let the model interact with the environment, validate actions, and plan.
Direct Play – 7.8
Codex Harness – 61.1
Prime Agent – 78.3
Twin Harness – 93.3
This stark ladder demonstrates that the “Agent ability” is largely defined by the surrounding system, not just the model’s raw intelligence.
02 – Why Harnesses Matter More Than an Extra Prompt Layer
Twin’s core innovation is letting the coding agent build a executable World Model in Python during testing. The harness enforces hard constraints: the agent cannot submit a scoring action unless its World Model can replay all observed transitions. Mismatches become counterexamples that feed back into the next repair cycle.
This validation loop gives the harness execution authority, turning it from a simple prompt tweak into a decisive control mechanism that blocks erroneous actions and guides exploration.
03 – DeepSeek Formalizes the Idea: Agent = Model + Harness
DeepSeek’s official page states the formula “Agent = Model + Harness” and describes a modular harness architecture with plug‑in tools, sessions, sandboxes, and scheduling. Different modes (Standard, Code, Minimal) expose varying toolsets, illustrating how the harness shapes the agent’s capabilities.
Both Twin (experimental evidence) and DeepSeek (product design) converge on the same insight: the model provides potential, while the harness determines how that potential is realized in real tasks.
04 – Benchmark Units Are Shifting to Whole Systems
Because harnesses dramatically affect scores, future Agent benchmarks must compare complete systems—model, tools, context handling, verification, and execution loops—rather than isolated model performance.
The Twin experiments also reveal a cost trade‑off: Twin consumes about 2.6 B tokens (≈2.4× the no‑harness baseline) and 91.4 hours of wall‑clock time, but achieves far higher task completion rates and action efficiency.
05 – Conclusion: The Next Gap Lies Outside the Model
As models become strong general‑purpose engines, the decisive factor for Agent success will be the design of the surrounding harness: how it structures tool use, maintains state, validates actions, and turns failures into learning signals. Competitive advantage will increasingly shift from model scaling to harness engineering.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
DataFunTalk
Dedicated to sharing and discussing big data and AI technology applications, aiming to empower a million data scientists. Regularly hosts live tech talks and curates articles on big data, recommendation/search algorithms, advertising algorithms, NLP, intelligent risk control, autonomous driving, and machine learning/deep learning.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
