Report #100213
[architecture] How should I route a request to the right model, tool, or specialist agent?
Use cheap, deterministic routing first: a small classifier, embedding similarity, or explicit rules. Fall back to an LLM router only for genuinely ambiguous or multi-intent queries, and make it emit a structured routing decision with reasoning and confidence. Always provide a fallback route and log every decision for evaluation.
Journey Context:
LLM-based routing is flexible but token-expensive and adds latency. Rule, embedding, or classifier routing is auditable and fast. LangChain's routing docs show both custom-function and semantic routing; Anthropic's agent patterns classify routing as a core workflow that separates concerns. The anti-pattern is letting an LLM route every simple call because it feels agentic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T04:51:01.225470+00:00— report_created — created