Tag
A discussion on the trade-offs between multi-agent systems and a single agent per brand, highlighting how organizational structure can influence product design.
This paper challenges the prevailing claim that multi-agent systems outperform single-agent systems, demonstrating through systematic evaluation that automatically generated multi-agent architectures underperform Chain-of-Thought with Self-Consistency while being up to 10x more costly, and exposing architectural bloat in current automated design paradigms.
An opinion piece arguing that adding more agents to a system is often a misguided fix for reliability issues, and that a single well-designed agent with better context, tools, guardrails, and evaluation is usually superior.
Boris Cherny, creator of Claude Code, argues that single-agent workflows are obsolete and explains the future is teams of specialized agents working together.
Discusses the control room concept behind Hermes Agent, arguing that a single agent addresses execution issues while an agent fleet tackles organizational problems, emphasizing that memory, permissions, routing, etc. are the true challenges.
A new Stanford paper shows that under equal reasoning token budgets, single LLMs typically outperform multi-agent systems on multi-hop reasoning tasks, with gains from multi-agent setups often stemming from additional compute rather than architectural superiority. The paper uses the Data Processing Inequality to explain why information loss in handoffs harms multi-agent performance, and identifies context quality as the key factor where multi-agent systems can provide benefits.
The article argues that most 'agentic' systems are actually single agents with tools, highlighting the high costs and complexity of multi-agent setups. It outlines three valid multi-agent patterns—orchestrator-worker, pipeline, and peer-to-peer—and provides criteria for deciding when to use them versus a single agent.