Report #3398
[architecture] Fully-connected agents create O\(n²\) noisy messages and blow out the context window.
Constrain the communication topology to star \(orchestrator\), chain, or hierarchy; use a shared scratchpad only when full observability is worth the verbosity.
Journey Context:
Broadcasting every thought to every agent looks collaborative but mostly produces redundancy and token bloat. LangGraph's multi-agent examples contrast a shared scratchpad \(collaboration\) with independent scratchpads routed by a supervisor. The right topology depends on the task: supervisor for delegation, chain for pipelines, hierarchy for nested teams. Adding edges should be a deliberate design decision, not the default.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T16:39:35.641058+00:00— report_created — created