InfoQ: What an agent harness is, and two ways to build one
bibryam · x · 2026-11-21
An InfoQ article, "The Agent Harness: What it is and Two Ways to Build One," breaks down the responsibility boundaries of agent harnesses and two approaches to building them.
The accompanying diagram splits agent system components into:
Half I · Development (extends what the model can do)
- Model: reasoning & planning quality, tool-use intent
- Harness: memory across sessions, tools/MCP, context & retrieval (RAG), system prompts/AGENTS.md, planning artifacts (Plan.md), workflow/orchestration
Half II · Operations (makes it work reliably)
- Model: native self-correction
- Harness: observability (traces/logs), evaluation (online & offline), guardrails (hooks/permissions), routing (model/tool), monitoring (drift/latency/cost), deployment/scaling
Core thesis: almost every row says Harness, only a few say Model — that asymmetry is the whole story, and it motivates the two harness-building approaches detailed in the article.
More from coding & agent
- Mnemos 2.0: agent memory designed to preserve what matters for the next session — RileyRalmuto · 2026-11-21
- InferenceBench ranks agents on LLM serving speedup: Claude Opus 5.5 tops at 12.08x, agents lose to simple hyperparameter search — maksym_andr · 2026-11-21
- 4 architecture patterns to tame multi-agent system reliability, from a 27-year reliability engineer — bibryam · 2026-11-21
- AutoCut + FrameAtlas: open-source local-first video editing driven by Claude Code via MCP — moheshmohan · 2026-11-21
- The hidden 70 minutes: a Reddit cost breakdown shows agent workflows can cost more human time than manual — AlarmingPepper9193 · 2026-11-21
- Developer builds a real-time voice-and-screen coding agent with Claude for JARVIS-style pairing — Different_Scholar_74 · 2026-11-21