Production agent work showed why one-job-per-agent beats complex swarms
Deepfeet-09 · reddit · 2026-07-22
After months of breaking autonomous agents in production, the author concludes that simple architectures beat clever ones.
What failed
- A complex multi-agent assistant that planned, executed, and self-corrected end to end turned into an unmaintainable token sink.
- It got lost several steps into reasoning loops and could fail silently without errors.
What worked better
- Replace open-ended planners with a strict one-job-per-agent design.
- Give each agent narrow responsibilities and explicit state boundaries.
- Use micro-agents with clear input/output contracts so failures are easy to debug.
- Add human-in-the-loop approval for irreversible external writes, while low-risk internal tasks can run autonomously.
The main lesson is that the hard part of production agents is not making the model smarter; it is building guardrails, state management, and recovery paths that keep the system deterministic when the model goes off course.
More from coding & agent
- Antirez says DwarfStar could become quasi-automated as frontier models improve — antirez · 2026-07-22
- Antirez proposes a DwarfStar workflow with human main branches and AI-built experiments — antirez · 2026-07-22
- browser-search v2.0 turns agents into deterministic web browsers — Ill-Tradition1362 · 2026-07-22
- LangChain says graph engineering has powered its agents for years — hwchase17 · 2026-07-22
- Agent memory needs ontology, write paths, and graph-based retrieval — Al_Grigor · 2026-07-22
- AI-assisted tool generates an FPGA dev board in 52 minutes — debreuil · 2026-07-22