What is harness engineering?

Harness engineering is the discipline of designing and evolving the harness around a model, the loop, tools, context management, safety controls, orchestration, and extension surfaces, so an agent’s mistakes get fixed at the system level instead of waited out. A source-code study of eleven production coding harnesses, which named the discipline in early 2026, maps it to seven canonical subsystems and catalogs 29 recurring design patterns across them.

In practice it’s narrower than architecture: Addy Osmani describes the job as noticing when an agent makes a mistake and engineering a fix so it never makes that exact mistake again, a prompt line added, a tool description tightened, a hook inserted, rather than waiting on a better model. The scope stretches past the loop itself into how an agent’s actions get observed, since a harness engineer can’t fix what a trace doesn’t show.

It never finishes: a fix that’s correct today still needs the next one once the model, the tools, or the traffic underneath it changes.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y