Report #45467
[architecture] Two agents attempting to call the same stateful external tool simultaneously, leading to corrupted external state
Assign tool ownership to a single agent. If another agent needs the tool, it must request the action via a message to the owning agent, enforcing a single writer principle.
Journey Context:
Concurrent writes to a file or database from two LLMs will overwrite each other's changes. By making one agent the exclusive writer \(e.g., a CodeEditorAgent\), you serialize access to that resource. The tradeoff is creating a bottleneck at the owning agent, but it guarantees consistency and prevents the 'too many cooks' problem where agents undo each other's work.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:47:32.177138+00:00— report_created — created