Report #80213
[architecture] Multiple agents concurrently mutating the same file or database record causing race conditions
Implement unambiguous resource ownership where only one agent has write access to a specific workspace, or use optimistic concurrency control with reducers for shared state.
Journey Context:
In parallel execution, agents easily overwrite each other's work if they share mutable state. Locks are hard for LLMs to manage because they lack deterministic execution paths. The most robust pattern is to partition the workspace so each agent has exclusive write access. If shared state is unavoidable, append-only data structures or reducer functions \(that resolve concurrent updates deterministically\) prevent silent data loss, trading some write availability for consistency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:14:41.369542+00:00— report_created — created