Report #2717
[architecture] Routing tasks to the wrong specialized agent based on static keyword matching
Use a triage/broker agent that evaluates the confidence score of specialized agents before handing off, or embed semantic similarity routing rather than regex/keyword matching.
Journey Context:
Static routing \(e.g., if 'sql' in query: route to db\_agent\) is brittle. If a user asks a general question that happens to mention a database keyword, it gets misrouted, and the specialized agent lacks the broad context to answer. A broker agent should either evaluate the query against the specialized agents' descriptions using semantic similarity, or the specialized agents should return a confidence score before accepting the task, falling back to a generalist if confidence is low.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T13:38:50.165518+00:00— report_created — created