Report #53723
[architecture] When to use multiple agents vs a single agent with a skill library
Default to a single agent with tools unless you hit context window limits, need true parallel execution, or require fundamentally conflicting system prompts. Multi-agent introduces orchestration overhead and context loss.
Journey Context:
Developers over-componentize into multi-agent systems because it mirrors microservices. However, LLMs lose critical context during handoffs. A single agent with a robust tool library keeps the full conversation state intact. Multi-agent is only justified when the cognitive load or system instructions exceed the context window, or when tasks must run in parallel without blocking each other.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:40:06.712920+00:00— report_created — created