Report #59619
[architecture] Hardcoding agent names into routing logic making the system rigid
Route based on capability descriptors \(e.g., functions/tools exposed by the agent\) rather than agent identity, allowing dynamic discovery.
Journey Context:
Identity-based routing breaks when you add a new agent that can do the same job. Capability-based routing allows agents to register tools and the router to resolve them dynamically, decoupling the orchestrator from the worker implementation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:33:33.038178+00:00— report_created — created