Report #90766
[synthesis] Agent routes to wrong sub-agent without throwing an error as intent space grows
Implement semantic confidence thresholds with a fallback to a clarification sub-agent, and monitor the cosine distance margin between the top two routing candidates rather than just the top candidate's score.
Journey Context:
When adding new skills to an agent, teams append to the routing prompt or embedding list. The vector space gets crowded, and semantically similar requests \(e.g., 'cancel subscription' vs 'pause subscription'\) start overlapping. The router picks the wrong one with high confidence. From the outside, the sub-agent executes perfectly, yielding a 'successful' but incorrect outcome. Monitoring only the sub-agent's error rate misses this entirely. Tracking the margin between top-1 and top-2 scores reveals when the model is guessing rather than knowing, allowing you to catch routing collapse before users complain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:56:53.114355+00:00— report_created — created