Report #67703
[architecture] When to use multiple agents versus one agent with a large skill library
Default to a single agent with multiple tools. Only introduce multiple agents if you hit context window limits, need strict permission isolation, or require highly divergent system prompts.
Journey Context:
Engineers often map human org charts to agent architectures, creating a 'sales agent' and 'support agent'. This introduces coordination overhead, state synchronization errors, and routing failures. A single LLM with a unified context and tool suite is far more reliable for tightly coupled tasks because it eliminates handoff latency and context loss.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:07:19.500458+00:00— report_created — created