Harness engineering: why the value of AI has left the model

The whole industry stares at the same scoreboard: which model is in the lead, by how much, on which benchmark. The reflex is understandable, and today it largely misses the point. The best models are now neck and neck at the top, within a few decimals of each other. While we compared those decimals, the engineering that actually decides things moved to new ground. It left the model and settled into what we build around it: the harness.

I sum this up with an equation that has become my compass: Agent = Model + Harness. The model brings the raw intelligence. The harness is the entire environment that turns that intelligence into a genuinely useful agent: its tools, its memory, the business procedures it has to follow, its guardrails, its verification loops, its access to the information system. The quality of an agent barely depends on the first term of the equation anymore. It plays out in the second.

Three ages of AI engineering

To understand this shift, you have to place it inside a short history in three acts.

2022-2023, prompt engineering. The art of whispering into a model's ear. You phrase the right request, with the right role and the right examples. It was new, spectacular, and already a little fleeting.

2024-2025, context engineering. A good question is no longer enough, you also need the right context. Not "write an email", but "here is the client, here is our tone, here is the history, write an email". You no longer tune the phrasing, you curate the information that enters the model's window.

2025-2026, harness engineering. You no longer just tune a prompt or a context, you build the whole environment around the AI. This is what takes you from a raw model to a production agent. My rule of thumb, empirical but stubborn: a good prompt counts for 10% of the result, the right context adds 30%, and the harness wrapping the whole thing counts for the remaining 60%.

The proof in the numbers

You might think this is a pose. The measurements say otherwise. In March 2026, the LangChain team moved its coding agent from 30th to 5th place on the Terminal Bench 2.0 benchmark without touching the underlying model. Twenty-five places gained, purely by optimizing the harness. On SWE-bench, the finding is of the same order: swapping the harness shifts the score by about 22 points, swapping the model shifts it by 1 point.

Read those figures a second time. With the model held constant, the harness makes twenty times more difference than the model itself does with the harness held constant. That is the whole thesis: the model is becoming a commodity, and the variable that decides production performance is the harness.

What is really inside a harness

A good harness is not a configuration file, it is an architecture. You always find the same layers: tool orchestration (how the agent selects, chains and executes its actions, with error recovery); memory and context (indexing a codebase, persisting history); the business procedures the agent has to respect; the guardrails (strict bounds, security sandbox, budget caps, human validation checkpoints); the verification loops (tests, self-critique, in-run quality control); and observability (telemetry, tracing, audit logs).

The right image is organizational before it is technical. Building a harness is like setting up a company: once you have recruited the right talent, you still have to build the organization, the tools and the processes so they move in the same direction and create value. The model is a superhuman worker. The harness engineer is the architect who decides which materials that worker is allowed to use, and the order in which the stones must be laid.

Value migrates

This shift has very concrete consequences for who makes money, and how. Stripe merges more than 1,300 code changes per week generated by its agents. There is no miracle model in there: its engineers spent months building a harness that produces code consistent with the company's specification and workflow.

Conversely, platforms like Lovable have watched their advantage evaporate. Their real value was precisely the harness they built around the models. The moment an ecosystem like Claude Code ships with its harness built in, file read and write tools, permission controls, correction loops, that moat melts before your eyes. Value then simply migrates from the model to the way you wire it into your processes.

A durable engineering discipline

One last difference, and it is decisive. Prompt engineering had something of a trick to it: a good phrasing, quickly copied, quickly outdated. Harness engineering is of a different nature. It is a real craft, a real engineering discipline, one that compounds and refines over time. And the more capable the models become, the more this shift intensifies: their intelligence becomes abundant, and what stays rare is the way to wire it into a real context.

That is also what makes the harness so strategic. Done well, it lets you make AI the operating system of your organization. I am building one right now for my own activities, and it has transformed close to 90% of the way I work. The term itself is young, it emerged in early 2026, but the skill will last.

The conclusion fits in one sentence. In the era now opening, the reigning skill is shifting: knowing how to build the harness around the model. Stop looking for the right whisper. Become the architect.