Report #12258
[architecture] When to use single-agent-plus-tools vs. multiple agents
Default to a single agent with a tool library. Only introduce multiple agents when you need isolated system prompts, parallel execution, or distinct security boundaries.
Journey Context:
Developers often over-decompose tasks into multi-agent systems, which introduces routing overhead, context loss during handoffs, and duplicated token costs \(each agent needs its own system prompt and context\). A single agent maintains a unified context window and avoids handoff failures. Multi-agent is only justified when instructions fundamentally conflict \(e.g., writer vs. critic\) or tasks can run in parallel.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T15:36:54.636113+00:00— report_created — created