Harness Engineering 101

What It Covers

Harness engineering — the systems, tools, and configurations surrounding AI models — has emerged as the defining discipline of 2025, following prompt and context engineering. The episode traces its origins, maps its components across three layers, and explains why every major AI product is converging on the same architectural pattern.

Key Questions Answered

• •The Evolution of Engineering Disciplines: AI practitioners have moved through three distinct eras: prompt engineering (2023–2024), context engineering (2024–2025), and now harness engineering. Each layer builds on the last. Understanding this progression helps practitioners stop optimizing the wrong layer — most current agent failures are configuration problems, not model capability problems.
• •Three-Layer Harness Framework: Aetna Labs maps harnesses into three actionable layers: an information layer (what the agent can see and invoke), an execution layer (how work decomposes, agents collaborate, and failures recover), and a feedback layer (evaluation, verification, tracing, and observability). Structuring agent systems around all three layers produces more reliable, improvable pipelines.
• •Outer Harness vs. Inner Harness: Practitioners using Claude Code, Cursor, or Codex build two harness types simultaneously. The inner harness is built by Anthropic or OpenAI. The outer harness — agents.md files, repo structure, MCP servers, memory configuration — is built by the user and directly determines output quality for specific codebases and goals.
• •Harness Performance Outpacing Raw Models: Blitzy achieved 66.5% on SWE-bench Pro versus GPT-4.5's 57.7% by wrapping foundation models in a knowledge graph that provides deep codebase context. GPT-4.5 failed not catastrophically but on intricate corner cases. This data point supports the thesis that harness infrastructure can unlock larger performance gains than model upgrades alone.
• •Anthropic's Meta-Harness Architecture: Anthropic's Managed Agents product separates the agent loop (brain), execution environment (hands), and event log (session) so each component can fail or be replaced independently. The design principle: any specific harness is temporary as models improve, so building stable interfaces around disposable harness implementations future-proofs agent infrastructure.