Agent harnesses should match action and context complexity, not copy Claude Code
hugobowne · x · 2026-07-22
A long post argues that most agent systems fail because builders add too much harness complexity too early.
- The author says the common default list — memory, compaction, sub-agents, orchestration, planning, hooks, guardrails, evals — is often the wrong starting point.
- Instead, an agent should first be mapped on two axes:
- Action complexity — how many tools, decisions, dependencies, and iterations it must coordinate.
- Context complexity — how much information must stay coherent across model calls.
- Coding agents and deep-research agents tend to be high on both axes.
- Support/sales agents usually have lower context complexity; their main issues are routing, tool exposure, and human handoff.
- The post also separates action complexity from action risk: a one-turn agent can still need strict permissions if its actions have high consequences.
- The takeaway is to design around the actual failures your system can encounter, not around a one-size-fits-all Claude Code-style harness.
Related event: Production Agent Insights: Simple Architecture Beats Over-Engineering(4 posts)→
More from coding & agent
- qwen-code v0.26.1 nightly adds session permission rules, auto approval and shared agent loop — qwen-code-review-bot · 2026-10-27
- Mitsuhiko Cleans Up the AI-Made Game He Built With His Kids — mitsuhiko · 2026-10-27
- 'Taste skills' are AI's biggest lie — code is commoditized, your eye is the moat — aryanXmahajan · 2026-10-27
- Agent Buddy: A Desk Gadget That Shows What Your Background AI Coding Agents Are Doing — DanWahlin · 2026-10-27
- kimo: open-source GUI-less video editor lets AI agents cut video via typed MCP tools and render frames to self-verify — LieTop7965 · 2026-10-27
- Weekend RAG turns into a full-time job; Stack Overflow's Stack Internal absorbs the cost — pchandrasekar · 2026-10-27