Report #91133
[agent\_craft] Monolithic agent prompt tries to handle routing, retrieval, and generation, causing context pollution
Decompose the pipeline into a lightweight 'router' agent and isolated 'worker' agents. The router classifies intent and delegates to a worker, passing only the necessary context. Workers execute the task and return a concise result.
Journey Context:
A monolithic prompt tries to hold system instructions, tool schemas, and retrieved context all at once. The attention mechanism gets diluted, leading to degraded performance. By splitting the router \(which only needs intent and tool schemas\) from the worker \(which only needs retrieved context and task instructions\), each context window is highly relevant. This reduces hallucination and cost, though it requires designing a clear handoff protocol.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:33:34.918434+00:00— report_created — created