What Is an Agent Harness

LangChain is not a harness. LangGraph is not a harness.

Defines the modern agent harness as an out-of-the-box architecture that emerged from coding agents: an iteration loop over tools, context management, skill/tool discovery, permissions, hooks, session persistence, sub-agents, and project-context injection.

A strongly procedural counterweight to thin-harness framings. The post argues that harnesses are not generic frameworks for humans to assemble agents, but working closed-loop environments that let models act, observe, repair, persist, and extend themselves.

• Read the original →

Dhinakaran draws a bright line between frameworks and harnesses. Frameworks such as LangChain and LangGraph give human developers abstractions to wire together. A harness, in her account, ships as a working agent architecture: outer loop, context manager, tool and skill registry, permission system, lifecycle hooks, session persistence, sub-agent management, and dynamic project-context injection. The post is useful because it treats harnesses as an empirical convergence, not a vendor category. Coding agents such as Cursor, Claude Code, Windsurf, and Codex started from the practical problem of changing real repositories, then converged on similar structures: tool loops, compressed context, approval layers, and built-in file/shell/code-navigation primitives. Arize's Alyx is positioned as the same pattern appearing outside pure coding. For the Extended Frontier argument, this is direct evidence that capability is produced by the situated assembly. The model alone is a one-shot text generator; the model inside a harness becomes a feedback-seeking system that can act, observe consequences, and adjust. That closed loop is not incidental plumbing. It is what changes the unit of capability from model output to model-in-environment performance. This entry should sit beside: • Tan, "Thin Harness, Fat Skills" — disagrees on where durable leverage should live. • Miessler, "Good and Bad Harness Engineering" — adjacent harness-engineering vocabulary. • Anthropic, "Agent Skills" — one of the built-in skill-layer mechanisms this post treats as part of harness architecture. Components To Reuse Dhinakaran's harness 1.0 component list is a useful checklist for classifying future entries: • Outer iteration loop. • Context management and compression. • Skills and tools management. • Sub-agent management. • Built-in pre-packaged skills. • Session persistence and recovery. • System prompt assembly and project-context injection. • Lifecycle hooks. • Permission and safety layer. Tension The strongest claim is also the pressure point: if a harness is defined as an out-of-the-box working agent architecture, then LangGraph-style frameworks are excluded even when they can be used to build similar loops. That exclusion is analytically useful for the library because it keeps the focus on deployed capability environments, not just orchestration abstractions.

Date confirmed by Daniel. Title, author, URL, and content came from user capture; confirm directly in X before formal citation.