From dad0f39fa47ed1e77ca461c39357511bb29d930f Mon Sep 17 00:00:00 2001 From: Eugene Yurtsev Date: Wed, 4 Dec 2024 18:49:17 -0500 Subject: [PATCH] concepts: reword network architecture (#2625) --- docs/docs/concepts/multi_agent.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/docs/concepts/multi_agent.md b/docs/docs/concepts/multi_agent.md index 46bf4eeda..d8ef0a73b 100644 --- a/docs/docs/concepts/multi_agent.md +++ b/docs/docs/concepts/multi_agent.md @@ -28,12 +28,7 @@ There are several ways to connect agents in a multi-agent system: ### Network -In this architecture, agents are defined as graph nodes. Each agent can communicate with every other agent (many-to-many connections) and can decide which agent to call next. While very flexible, this architecture doesn't scale well as the number of agents grows: - -- hard to enforce which agent should be called next -- hard to determine how much [information](#shared-message-list) should be passed between the agents - -We recommend avoiding this architecture in production and using one of the below architectures instead. +In this architecture, agents are defined as graph nodes. Each agent can communicate with every other agent (many-to-many connections) and can decide which agent to call next. This architecture is good for problems that do not have a clear hierarchy of agents or a specific sequence in which agents should be called. ### Supervisor