Multi-Agent Systems: Engineering Workflows vs. Emergent Intelligence

After building and experimenting with several multi-agent systems, a developer on r/LocalLLaMA argues that most current implementations are solving engineering problems rather than intelligence problems. The post examines what multi-agent systems actually do well and why they don't yet produce emergent intelligence.

What Multi-Agent Systems Actually Do Well

From the developer's experience, multi-agent systems mainly help with three practical engineering benefits:

• Task decomposition: Instead of one giant prompt, workflows are split into multiple steps. Example: Planner Agent → decides the plan, Research Agent → gathers information, Writer Agent → generates content, Critic Agent → reviews. This works well but is fundamentally just a pipeline.
• Parallelization: Multi-agent setups make it easier to run tasks in parallel. Example: Research Agent 1 → search papers, Research Agent 2 → search news, Research Agent 3 → search databases, with an aggregator agent combining results. This is basically distributed workers with LLM reasoning.
• Engineering modularity: In real systems with dozens of tools, splitting agents by responsibility helps development and maintenance. Example: Search Agent → handles search tools, Database Agent → handles DB queries, Code Agent → handles coding tasks, Planner Agent → handles reasoning. This is mostly software architecture, not emergent intelligence.

Why "Agent Swarms" Don't Produce Emergent Intelligence (Yet)

The post identifies three structural limitations:

• Communication is extremely expensive: Neurons communicate in microseconds. Agents communicate through LLM calls that take seconds, limiting complex interactions.
• Agents cannot update each other: Neural networks learn through backpropagation. If Agent A makes a mistake, Agent B can criticize it, but it doesn't actually change Agent A's internal model.
• No shared representation space: Neurons communicate through vectors. Agents communicate through natural language, which is ambiguous, lossy, and token-expensive, causing information to degrade quickly across multiple agents.

What Multi-Agent Systems Actually Resemble

The developer concludes that after working with them, these systems look much closer to microservices architecture. Each agent is essentially: a role, a toolset, and a prompt, and the system is just an orchestrated workflow.

Practical Value and Future Directions

Multi-agent systems are not useless—they're extremely useful for complex workflows, tool-heavy systems, large engineering teams, and parallelizable tasks. However, the value is mostly engineering scalability, not collective intelligence.

The real question is: if we actually want true emergent multi-agent intelligence, we probably need something very different. Possibly things like: shared latent memory spaces, agents that learn policies (multi-agent RL), or graph-based reasoning architectures instead of pipelines.

Right now, most "multi-agent systems" are just well-structured workflows with LLMs.