Report #38420
[frontier] LLM-based router agents introduce high latency and hallucinate routing paths in multi-agent systems
Use deterministic code-based routing \(intent classification via embeddings or small models\) for orchestration, reserving large LLMs only for cognitive execution tasks.
Journey Context:
It is tempting to use a powerful LLM as the 'orchestrator' or 'router' agent to decide which sub-agent to invoke. In practice, this adds 1-2 seconds of latency per step and is highly unreliable for structured routing decisions. The winning pattern is 'Code as Orchestrator, LLM as Brain': use fast, deterministic code \(like embedding similarity or a tiny classifier\) to route tasks, and only invoke the expensive LLM when actual reasoning or generation is required.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:58:03.366420+00:00— report_created — created