Report #63765
[synthesis] Agent acts on stale state due to context window caching
Force explicit state rehydration. Before taking a mutating action, the agent must explicitly call a read current state tool and cannot rely on the state description present in its earlier context.
Journey Context:
In long-running agent tasks, the agent reads a file or database record in step 1. By step 10, after multiple intermediate reasoning steps, the external state may have changed \(either by the agent's own intermediate tools or external factors\). However, the agent acts on the step 1 state because it is cached in the context window. This is the LLM equivalent of a race condition. The tradeoff is increased tool calls \(reading before writing\), but this is essential to prevent the agent from overwriting new data with decisions based on stale data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:30:54.765809+00:00— report_created — created