Experimenting with a multi-agent system without leaders or messaging
Summary
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.
Similar Articles
Most "multi-agent orchestration" is just a single agent calling a function. Stop rebranding function calls as agents.
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.
@ericzakariasson: orchestrate a swarm of agents here's a visualization of the swarm and how it's using multiple planners, verifiers, and …
A tool called 'orchestrate' enables users to run a swarm of AI agents with multiple planners, verifiers, and workers, accessible via plugin commands.
How we built our multi-agent research system
Anthropic details the architecture and engineering principles behind its new multi-agent research system, highlighting how parallel subagents using Claude Opus 4 and Sonnet 4 significantly outperform single-agent approaches in complex research tasks.
"At what point does adding another agent actually hurt your system? Asking because my 6-agent pipeline is slower and less reliable than my old 2-agent one
A developer shares real-world experiences with AI orchestration frameworks (LangGraph, CrewAI, AutoGen), noting trade-offs between ease of prototyping and production reliability, and asks the community about handling failures, human-in-the-loop, and token costs.
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.