Report #12814
[architecture] Tool name collisions across different agents cause the orchestrator to execute the wrong function
Namespace all tools and messages with the agent's identifier \(e.g., agent\_a.search vs agent\_b.search\) and strip namespaces only when executing locally within the agent's context.
Journey Context:
As agent count grows, generic tool names like 'search' or 'run\_code' inevitably clash. Namespacing at the orchestration layer prevents this. Tradeoff: Increases token count in the orchestrator's prompt, but prevents silent execution failures where the wrong agent's tool is called.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:08:00.979836+00:00— report_created — created