Report #46358
[architecture] Routing tasks to specialized agents prematurely based on keyword matching, causing unnecessary context fragmentation
Route to specialized agents only when the primary agent explicitly signals low confidence, encounters a missing tool error, or fails a validation step.
Journey Context:
Eagerly routing based on keywords \(e.g., seeing 'database' and routing to a DB Agent\) breaks the context of the primary agent, which might have been able to handle it using its general knowledge. Confidence-aware or error-aware routing ensures handoffs only happen when the current agent actually fails, preserving unified context as long as possible.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:17:08.935236+00:00— report_created — created