Report #16644
[architecture] Router agent hallucinating the name of a target agent or skill, causing orchestration dispatch failures
Define agent routing as a strict function call with an enum of valid agent names, rather than allowing the LLM to output the agent name as a raw string.
Journey Context:
If you ask an LLM which agent should handle this, it might invent an agent name that does not exist. By mapping the routing decision to a tool call where the agent name parameter is constrained by an enum, the LLM is forced to select from the actual registry of available agents, eliminating typo-based dispatch failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T03:13:57.480535+00:00— report_created — created