Report #55768
[architecture] LLM orchestrator hallucinating the name or existence of a sub-agent, leading to routing failures
Define the list of available target agents as a strict enum in the orchestrator's tool schema, and programmatically validate the routing target before executing the handoff.
Journey Context:
When an orchestrator agent is prompted with a list of available agents in natural language, it may hallucinate a non-existent agent name when faced with a request it cannot fulfill. The fix is to represent the handoff as a structured tool call with an enum constraint. The LLM is forced to select from the schema, and the orchestrator code can catch invalid enum values deterministically.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:06:07.977460+00:00— report_created — created