Version 2

The systems-centric view of AI agent performance — that the surrounding infrastructure ('harness') shapes agent behavior more than model or prompt choices alone — is crystallizing into new vocabulary and tooling. A significant linguistic shift is underway: multiple independent sources now prefer 'context engineering' over 'prompt engineering' as the frame for what AI teams should be optimizing.[6][7] The AI agent memory conversation has broadened from a single Meta finding into a recognized field-wide concern, with multiple 2026 state-of-the-field surveys appearing.[3][5] Warp's 75.8% score on SWE-bench Verified[10] illustrates real-world competitive stakes, while SWE-bench's own documentation formalizes a 'harness' concept at the evaluation layer itself.[9]

The shift from 'prompt engineering' to 'context engineering' is significant not just as terminology but as a reframing of where engineering effort should go — from crafting text inputs to designing information architecture. If standardized evaluations now treat the harness as a first-class architectural component,[9] that creates the infrastructure for controlled ablations that would let teams rigorously measure harness versus model contributions to performance — the measurement gap that has made the systems-centric argument hard to prove empirically.

The central argument gaining traction in May 2026 is that AI agent performance should be understood as a systems problem — not a model problem and not a prompts problem. The 'harness' — the orchestration logic, tool wiring, memory management, and context construction surrounding the model — is where most emergent capability lives, according to researcher Rohan Paul, who synthesized research arguing that 'many AI agents look like 1 model, but their real behavior comes from surrounding code' and that 'agent intelligence is becoming partly a systems problem.'[1] This claim directly challenges the dominant industry practice of selecting models on benchmarks and tuning prompts, suggesting that both activities optimize the wrong variable.

A parallel and complementary finding from Meta reinforces the memory dimension of this argument: coding agents perform substantially better when given short summaries of prior solution attempts rather than raw execution logs.[2] The implication is that the bottleneck is not compute — running more attempts — but information architecture: how past experience is encoded, compressed, and made accessible to the model on subsequent attempts. This finding is supported by a broader body of 2026 work on AI agent memory, now mature enough to generate multiple state-of-the-field surveys and benchmark efforts tracking how different memory architectures affect agent behavior.[3][4][5]

The vocabulary for this systems-centric view is now coalescing around a new term: 'context engineering.' Multiple sources have identified a shift away from 'prompt engineering' as the dominant frame, with AI teams and practitioners increasingly preferring 'context engineering' to describe the challenge of curating what information a model receives and when.[6][7] A Reddit thread in the MachineLearning community has similarly surfaced the AI infrastructure versus prompt engineering debate.[8] This framing is broader than harness engineering per se — it encompasses retrieval strategy, memory design, and context window management — but it points in the same direction: the real engineering challenge is building the information environment around the model, not crafting the text inputs to it.

The institutional infrastructure around these ideas is catching up. SWE-bench, the widely used coding agent benchmark, maintains formal documentation of its own 'harness' concept, treating evaluation infrastructure as a named architectural component.[9] Warp's 75.8% score on SWE-bench Verified[10] illustrates the competitive stakes: companies are now racing to push agent performance on standardized benchmarks, and harness design is a key variable in that race. Meta's ARE (Agent Runtime Environments) research[11] extends the infrastructure argument to the evaluation layer itself — applying systems-level thinking not just to how agents operate, but to how they are measured. Practitioners formalizing this sub-discipline include Martin Fowler, who has published a practitioner-oriented guide on harness engineering for coding agent users,[12] and LangChain, which has published anatomy-of-a-harness documentation to establish shared vocabulary.[13]