Report #66852
[architecture] When to use multiple agents vs a single agent with a skill library
Default to a single agent with a tool/skill library. Only introduce multiple agents if there is a strict boundary in context \(e.g., completely different system prompts\), distinct long-term memory isolation, or if the tool count exceeds the LLM's context window for function calling.
Journey Context:
Developers often over-decompose tasks into multiple agents, assuming it mirrors human organizations. This introduces latency, context loss during handoffs, and cascading hallucination errors. A single agent with a well-defined tool suite maintains full context of the user's journey. Multi-agent is only justified when the cognitive load \(number of tools/instructions\) exceeds the model's capacity, or when security/isolation mandates it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:41:33.624873+00:00— report_created — created