The thinking router currently makes routing decisions without any fallback for low-confidence cases. It should be able to express uncertainty and escalate to a richer signal — a summary of the conversation session (at minimum, user messages only) — before committing to a route.
- Current behavior: the router makes a binary/forced routing decision regardless of confidence
- Gap: ambiguous or context-dependent requests can be misrouted with no recovery path; the router has no way to signal "I don't have enough context" and pull in session history to resolve it
- Suggested approach: add an uncertainty state to the router output; when triggered, summarize recent user messages (or the full session) and re-evaluate before finalizing the route
The thinking router currently makes routing decisions without any fallback for low-confidence cases. It should be able to express uncertainty and escalate to a richer signal — a summary of the conversation session (at minimum, user messages only) — before committing to a route.