Harness Engineering: A Field Guide to Building Agents That Hold Up
Every agent demo works. Day two is where they fall over. The five layers of harness engineering, the system around the model, that decide whether an agent survives production.
Field notes
Harness engineering, agent evaluation, and what changes in an R&D org when agents write the first draft. Written for senior engineers.
14 notesRSS feed →
Every agent demo works. Day two is where they fall over. The five layers of harness engineering, the system around the model, that decide whether an agent survives production.
Most agents are bad at using tools because the tools were built for programmers, not for a model reading a one-line description under load. How to design tools, and MCP servers, that agents get right.
Teams reach for a vector DB and stop thinking. Real agents need layered memory: a working set, durable preferences, retrieval, and state that survives a restart. A practical breakdown.
Checking an agent's final answer tells you almost nothing. You have to score the whole trajectory: tool choice, arguments, step count, cost, policy. How to build evals that catch real failures.
Multi-agent is the current default answer, and it is usually the wrong one. When orchestration earns its overhead, when a single agent wins, and the patterns that hold up in production.
The technique behind viral AI agent loops: treat context like managed memory. State lives in files, not conversation. Progress persists. Failures evaporate.
Standard Ralph gates on tests passing. My version adds an adversarial intelligence that must explicitly sign off before progress is allowed.
I was losing 40k tokens on startup. So I built Flow, a plugin that uses command stubs, progressive disclosure, and adversarial review loops.
Most AI benchmarks tell you if a model can solve a LeetCode puzzle. They don't tell you if it can ship a product.
Practical tips from two weeks of shipping with the best agentic model yet.
Why modern AI delivery patterns finally unlock what agile promised - and how to structure teams to ship safely.
How AI agents and openEHR can lift healthcare out of its purgatory by structuring every input and embedding it into durable clinical knowledge.
Store everything, retrieve only what matters: long-context chat in ~100 lines with LangChain and Node.
Context quality sets the ceiling for AI outcomes; better retrieval and cleaner signals beat model hype.