Hacker News AI · 10/19/2026, 20:07:41

Harness Engineering 101: LLM is the Brain, Harness is the Body

68AI Score
Executive Summary

The 'Harness Engineering 101' series introduces the metaphor that an LLM is the brain and the harness is the body, defining agents as state-management programs wrapping a stateless LLM API. Across 16 chapters, it builds a ~300-line toy agent in Python from first principles, analyzing specific failure modes and trade-offs for each functional patch.

SOURCE COVERAGEFull Original Report

Contents10 sections

The LLM is the brain. The harness is the body.

Version 1.0 — September 2026.

A blog series about building AI agents from first principles, published as a book.

📖 Read it online: https://isuruwijesiri.com/harness-engineering-101/

An LLM API is stateless. Every turn, you send the entire conversation as a JSON array and get text back. A harness is the program that builds, maintains, and protects that array. Everything the field calls "agents" is a set of patches to that one loop, and each patch exists because something concrete broke. This series develops that one idea across 16 chapters, growing a ~300-line toy agent in plain Python as it goes.

The patterns here are developed in full in One Code, an open-source coding agent built on pi.

The rendered book reads best online at the link above. If you'd rather read the source here on GitHub, follow the chapters in order below. The full introduction is on the book's landing page.

Reading order

Every chapter has the same shape: the failure, the minimal patch, what the patch costs.

Part I — The Wire (nothing is magic)

#ChapterThe failure it patches
1It's Just a JSON Array"How do I even talk to this thing?"
2The Brain: A Next-Token Black Box"Why does it behave like that?"
3Tools: JSON Mapped to FunctionsThe brain can't touch the world
4The Agent LoopOne tool call isn't enough
5Caching: Why Order Is Load-BearingResending the array gets expensive

Part II — Running Long (the array under pressure)

#ChapterThe failure it patches
6Context Is a Budget, Not a BagThe window fills up
7Subagents: Fork the ContextOne array can't hold all the work
8Steering the Running LoopThe brain drifts mid-task
9Background Work and TimeThe loop is synchronous; the world isn't

Part III — The Ecosystem (naming what you already understand)

#ChapterThe failure it patches
10Every Framework Is a Wrapper Around Chapter 1Abstraction anxiety
11Extending the Body: MCP, Skills, Deferred Loading, HooksCapabilities don't fit in the array
12Debugging the ArrayYou can't fix the prompt you can't see

Part IV — Trust, Domains, and Data

#ChapterThe failure it patches
13Reflexes and GuardrailsThe loop will do something dumb
14Case Study: Coding AgentsHow specialized does the body need to be?
15RAG Was a Harness Pattern All AlongA thousand names for one idea

Epilogue

Appendix — Advanced Topics

Standalone pieces. Read them when you need them.

Repository layout

PathWhat it holds
src/*.mdThe chapters and appendices (the book source)
src/SUMMARY.mdThe book's table of contents
src/harness/The runnable toy harness — one file per stage
src/diagrams/Diagram generators and their generated PNGs
book.tomlmdBook configuration
scripts/sync-to-blog.shBuilds the book and mounts it into the blog for serving

Building the book locally

BASH
cargo install mdbook mdbook-mermaid   # or: brew install mdbook (+ mdbook-mermaid binary)
mdbook serve --open                    # live-reloading preview at http://localhost:3000
mdbook build                           # static site into ./book

mdbook-mermaid renders the inline mermaid diagrams; without it those blocks show as raw code.

Regenerating the quantitative diagrams

BASH
cd src/diagrams && python3 gen_all.py   # Python 3.10+, matplotlib