Report #14263
[agent\_craft] Router latency and errors from over-prompting
Keep the router lightweight. Use embedding similarity or keyword heuristics for initial retrieval, and only use an LLM for routing if the decision requires deep semantic understanding between ambiguous options.
Journey Context:
A common anti-pattern is using a massive LLM call just to decide \*which\* RAG database to query. This adds seconds of latency and often hallucinates the routing logic. Semantic routing or simple keyword heuristics are faster and more reliable for 90% of routing decisions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:10:46.981742+00:00— report_created — created