Report #14461
[architecture] When to use multiple agents vs a single agent with tools
Use a single agent with a tool/skill library for sequential tasks sharing tight context. Switch to multi-agent only when tasks require isolated context windows, distinct system prompts, or parallel execution to prevent context poisoning.
Journey Context:
Developers often default to multi-agent architectures for complex tasks, assuming it mirrors human organizations. However, inter-agent communication is lossy and introduces latency. A single agent retains the full conversational state without needing serialization or summarization. Multi-agent is the right call only when the 'cognitive load' of different personas causes the single agent to hallucinate or drop instructions, or when tasks can run in parallel.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:40:39.047885+00:00— report_created — created