Report #85749
[agent\_craft] Router agent dispatching tasks to sub-agents with full parent history causing context pollution
When routing to a sub-agent, pass only the minimal required context \(the specific task and necessary state\), and have the sub-agent pull its own background context via tools, rather than copying the parent's entire history.
Journey Context:
In multi-agent systems, it is tempting to pass the full conversation history to a sub-agent so it knows everything. This causes context pollution—the sub-agent gets confused by irrelevant parent context. The tradeoff is orchestration overhead vs. focus. By giving the sub-agent a targeted prompt and its own tools, it operates in a clean, focused context window, returning only the final answer to the parent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:31:06.127187+00:00— report_created — created