Most "multi-agent orchestration" is just a single agent calling a function. Stop rebranding function calls as agents.
Summary
The article critiques the overuse of the term 'multi-agent orchestration,' arguing that many implementations are simply single agents using function calls rather than true distributed systems. It highlights practical, production-tested patterns like sequential pipelines and human-in-the-loop workflows as alternatives to complex but ineffective architectures.
Similar Articles
Multi agent vs Single Agent systems
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.
Sub-Agents Are Not the Only Way
The article challenges the default sub-agent orchestration pattern in multi-agent systems, advocating for decentralized coordination via a shared message board. It introduces Blueprint Bulletins, a feature that allows agents to post self-expiring notes on a shared board for ambient coordination without a central orchestrator.
Experimenting with a multi-agent system without leaders or messaging
The author details an experimental multi-agent orchestration framework using a directed acyclic graph (DAG), concentrating intelligence in planner and replanner components while keeping worker agents mechanical. They are seeking community feedback, benchmarks, and existing research to validate its practicality against conventional message-passing approaches.
Stop Building Multi-Agent Systems
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.
Are we calling too many workflows “agents”?
The author questions whether many so-called AI agents are better described as workflows, arguing that for repeatable browser tasks, defined workflows may be more reliable than agents that reinterpret steps each time.