The multi-agent system trap
By Lenny's Podcast
Key Concepts
- Agent-based Systems: Systems built from multiple autonomous "agents" designed to handle specific tasks.
- Functional Decomposition: Breaking down a complex problem into smaller, functionally-defined components (agents).
- Gossip Protocol: A communication method where agents share information with nearby agents, hoping it spreads throughout the system.
- Agent Utopia (as a fallacy): The incorrect belief that simply connecting independent agents will result in a harmonious and effective system.
- Control & Predictability in Agent Systems: The difficulty in managing and anticipating the behavior of agents, particularly in customer-facing applications.
The Fallacy of Functional Decomposition in Agent Systems
The speaker challenges the common approach to building complex systems using multiple agents, each responsible for a specific function. The prevailing idea, as described, is to decompose a large problem into smaller, manageable pieces and assign these to individual agents. The expectation is that by connecting these agents, a functional and efficient system will emerge – an “agent utopia.” However, the speaker argues this is fundamentally flawed.
The core argument is that this approach, relying on a “gossip protocol” or similar decentralized communication, is “extremely misunderstood.” The assumption that agents will seamlessly collaborate simply because they are connected is unrealistic. The speaker explicitly states, “This notion of I’m going to divide the responsibilities based on functionality and somehow expect all of that to work together in some sort of gossip protocol. That is extremely misunderstood.”
Challenges in Customer Support Applications
The speaker highlights the particular difficulties of applying this agent-based approach to customer support. A key issue is the lack of control over which agent responds to a customer. The speaker emphasizes, “doing this in say a customer support kind of use case is incredibly hard to control what kind of agent is replying to your customer.” This lack of control introduces unpredictability and potential for inconsistent or inappropriate responses, directly impacting customer experience.
Current Model Limitations
The speaker expresses skepticism about the current methodologies and models used for building these types of agent-based applications. They state definitively, “I don't think current ways of building and current model are right there in terms of building those kind of applications.” This suggests a need for a re-evaluation of the fundamental principles guiding the development of multi-agent systems, particularly those intended for direct interaction with users.
Logical Connections & Synthesis
The argument progresses logically from a general critique of functional decomposition in agent systems to a specific example – customer support – to illustrate the practical challenges. The speaker doesn’t offer an alternative solution within this short excerpt, but clearly positions the current approach as inadequate. The core takeaway is a cautionary one: simply dividing a problem into functional components and connecting agents does not guarantee a well-functioning system, especially when predictability and control are crucial, as in customer-facing applications. The speaker implies that a more robust and controlled architecture is required.
Chat with this Video
AI-PoweredLoad the transcript when you're ready to chat so the initial page stays lighter.
Related Videos

Build a multi-agent system using ADK & MCP
Google Cloud Tech

Build a multi-agent system: A2A & Agent Registry
Google Cloud Tech

Build Systems, Not Code - Angie Jones, Agentic AI Foundation
AI Engineer

The most trusted code on Earth is being rewritten in Rust
Fireship

This Is The First Real Shape Of AGI: Fusion Agents
AI Revolution

3 patterns to build long-running AI agents
Google Cloud Tech

Intro to multi-agent systems with ADK
Google Cloud Tech