Report #91987
[architecture] Agent drifts from its specialized role and attempts to perform tasks meant for another agent
Strictly scope the toolset available to each agent; do not give an agent tools it isn't explicitly authorized to use, as tool access is the true enforcer of role boundaries.
Journey Context:
If Agent A \(writer\) has access to Agent B's tools \(code execution\), Agent A will inevitably try to use them instead of handing off, leading to unmonitored, poorly executed actions and breaking the multi-agent architecture. System prompts alone cannot prevent role drift; the LLM will use whatever tools are in its context. Tradeoff: Overly strict tooling might prevent an agent from completing a trivial adjacent step, forcing unnecessary handoffs, but this is preferable to the chaos of unconstrained tool access and blurred responsibilities.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:59:38.103643+00:00— report_created — created