Report #88401
[architecture] Using an LLM to decide which agent to route to when a simple deterministic rule suffices
Use deterministic routing \(if/else, keyword matching, fast classifiers\) for agent handoffs; reserve LLM-mediated routing only for highly ambiguous intent resolution.
Journey Context:
Using an LLM as a router introduces latency, cost, and non-determinism. If the user asks for a database query, a regex or intent classifier can route to the DBAgent instantly. Using an LLM to route adds 500ms\+ and might hallucinate the destination. Keep the control flow deterministic where possible; let LLMs handle the semantic reasoning within the agent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:57:51.414465+00:00— report_created — created