Report #23001
[synthesis] Parallel tool execution causes race conditions where the agent's context diverges from actual file system state
Serialize tool calls that mutate shared state like file writes or database updates even if the LLM requests them in parallel.
Journey Context:
To speed up agents, frameworks sometimes execute multiple independent tool calls simultaneously. If the agent requests \`write\_file\(A\)\` and \`write\_file\(B\)\` in parallel, and B depends on A's output \(which the agent might have inferred but the framework didn't check\), B fails or reads stale state. The agent gets confused because it assumes A finished. The fix is strictly serializing mutations, only parallelizing read-only operations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T17:01:06.427032+00:00— report_created — created