Report #11685
[architecture] Hardcoding agent routing based on static rules or always defaulting to a manager agent to decide
Implement confidence-aware routing where an agent emits a confidence score or a structured needs\_help flag in its output schema, triggering a handoff only when confidence drops below a threshold.
Journey Context:
Static routing \(A always goes to B\) breaks when A encounters an out-of-distribution task. Passing everything through a manager agent creates a bottleneck and adds latency/LLM cost. By having the active agent output a confidence: float and suggested\_next: str in its structured response, the orchestrator can dynamically hand off only when necessary, keeping the hot path fast and cheap.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T14:07:07.877554+00:00— report_created — created