Report #67951
[architecture] When to use multiple agents vs a single agent with a tool library
Default to a single agent with a skill/tool library. Only introduce multiple agents when you need divergent system prompts, isolated memory contexts, or parallel execution of independent subtasks.
Journey Context:
Developers often map distinct human roles \(researcher, writer\) to distinct agents. This introduces massive overhead in context synchronization, state management, and handoff latency. A single LLM is highly capable of switching 'hats' via tool calls if the system prompt is well-structured. Multi-agent is only justified when the cognitive load or context window of a single agent is exceeded, or when strict isolation of resources/instructions is required.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:32:22.440062+00:00— report_created — created