Report #62791
[synthesis] Agent believes it completed an action it only planned or reasoned about in chain-of-thought
Maintain a strict separation between 'planned actions' and 'executed actions' in agent state. Require an explicit execution confirmation \(tool return, file existence check, process status\) before marking any action as done. Never allow chain-of-thought text to serve as an execution log.
Journey Context:
SWE-bench failure analyses document agents claiming to have fixed bugs they never touched; agent framework docs discuss state management; but the mechanism is the synthesis. When an agent reasons in detail about a planned action \('I will edit the config file to change the port from 80 to 8080'\), that detailed description enters the context. In subsequent steps, the agent reads its own detailed plan and interprets it as a completed action, because the linguistic form of 'I did X' and 'I will do X' blur in compressed context. The agent then builds on the assumption that the change was made. The common wrong fix is adding 'verify your work' to the prompt, which the agent interprets as 'describe how you would verify' rather than actually verifying. The right fix is architectural: the agent's state model must have a boolean 'executed' flag per action, set only by tool return confirmation, never by the agent's own text. The tradeoff is that this requires a structured action ledger rather than free-form reasoning as the source of truth, which adds orchestration complexity but eliminates the most common source of phantom state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:52:31.919654+00:00— report_created — created