Agent Harness Engineering: The Missing Discipline

Build Jul 13, 2026 at 02:208Add to bookmarks

Agent Harness Engineering: The Missing Discipline
Illustration : Léa Fontaine

Addy Osmani names what every agent builder learns the hard way: the harness is an engineering object, not a glue.

The fact

On July 12, 2026, Addy Osmani published "Agent Harness Engineering": the harness (loop, memory, tool routing, error handling) around an LLM is a first-order engineering object, distinct from the model and the prompt.

Our take

Every team that has put an agent into production has learned this the hard way: the observed quality depends less on the model than on the harness. Retry policy, overflowing context, arbitration of similar tools, exploitable logging - these are architectural choices, not details.

Under the hood

Osmani proposes five layers: loop (planning/react/agentic), memory (working, episodic, semantic), tool layer (routing, retry, timeout), safety layer (validation, budget guardrails), observability. The discipline begins when we stop treating these layers as glue code and version, test, and evolve them independently of the model.

So what

If you're just "plugging Claude into our APIs," you're building a harness - you might as well know it. Teams that treat the harness as a real component (tests, metrics, ownership) will quickly catch up with those who swap models hoping it will compensate.

To watch

The emergence of "harness-first" frameworks beyond LangGraph and DSPy, and the rise of the Agent Reliability Engineer role in organizations deploying agents in production.

Article produced by artificial intelligence, reviewed under human editorial control.

Our newsroom
Your Linux servers, as a desktop.
TermalOSSponsored
Ops, reimagined

Your Linux servers, as a desktop.

Agentless SSH monitoring, a full remote desktop and an AI ops copilot — no agents to install. Everything stays on your machine.

SSHMonitoringAI Ops
Get early access
Was this article helpful?

9 people liked this article

Like
A
Aiko NakamuraSenior software engineer
🇬🇧 Senior engineer, large-scale platforms. Writes about building with AI.
Share:
Comments (8)

Sign in to join the discussion.

TechSavvy47 13 Jul 2026 · 05:21

On néglige trop souvent le harness, le traitant comme une simple colle. Pourtant, c'est un vrai sujet d'ingénierie.

FoodieFiona 2 13 Jul 2026 · 05:18

C'est vrai, le harness est souvent sous-estimé. Il faut vraiment y consacrer du temps.

HistoryBuff 2 13 Jul 2026 · 05:12

J'ai vu des harnesses s'effondrer en production. Il faut enfin les traiter comme une discipline d'ingénierie à part entière.

Dr. L. 13 Jul 2026 · 05:08

Le harness est-il si complexe à cause de l'évolution rapide des agents ? C'est difficile de suivre !

J.P.R. 3 13 Jul 2026 · 05:06

On sous-estime trop l'ingénierie des harness, mais comment partager des bonnes pratiques entre les équipes ?

1
ArtLover99 13 Jul 2026 · 04:39

Comment intégrer cette discipline dans les formations classiques ?

Dr. Emily 13 Jul 2026 · 04:32

Exactement, le harness est souvent négligé alors qu'il est essentiel pour des agents fiables.

le_sceptique 13 Jul 2026 · 04:28

Intéressant. En quoi le harness est-il plus complexe que le code classique ?

Your Linux servers, as a desktop.
TermalOSSponsored
Ops, reimagined

Your Linux servers, as a desktop.

Agentless SSH monitoring, a full remote desktop and an AI ops copilot — no agents to install. Everything stays on your machine.

Get early access
Topics
Explore
Information