Report #36184
[architecture] Registering the same tool name across multiple agents causing the orchestrator to execute it in the wrong context
Namespace tools by agent or strictly bind tool execution to the agent that invoked it, ensuring the execution environment matches.
Journey Context:
If two agents expose 'run\_code', the orchestrator must know which agent's environment to run it in. If tools aren't namespaced or bound to the agent's context, you get environment leaks or missing dependencies. Execution context must travel with the tool call to maintain isolation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:13:05.619205+00:00— report_created — created