Report #3682
[architecture] Spinning up multiple agents for distinct tasks when a single agent with a tool library is more efficient
Default to a single agent with a dynamic skill/tool library; only introduce multiple agents if tasks require fundamentally different system prompts, isolated context windows, or separate LLM weights.
Journey Context:
Multi-agent systems introduce massive coordination overhead, context passing loss, and routing failures. A single LLM with 10 tools can often handle varied tasks if the router/prompt is good. Multi-agent is only justified when context isolation is strictly necessary to prevent distraction, or when different models are needed for different steps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:03:01.606092+00:00— report_created — created