Report #35962
[architecture] Overhead of multi-agent orchestration for tasks a single agent could handle
Default to a single-agent-plus-skill-library; only adopt multi-agent when distinct system prompts, isolated memory, or parallel execution are strictly required.
Journey Context:
Multi-agent systems introduce severe overhead in context passing, token duplication, and latency. Passing context between agents is lossy compared to keeping it in a single context window. Use multi-agent only when a single context window overflows, when system prompts fundamentally conflict \(e.g., planner vs. executor\), or for true parallelizable sub-tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:50:16.084590+00:00— report_created — created