Report #51242
[counterintuitive] Model loses track of state in multi-step reasoning — running totals, board positions, variable assignments all drift
Use external state management \(code execution with actual variables, database lookups, scratchpads with real computation\) rather than relying on the model to maintain mutable state in its generated text. Have the model decide WHAT to do, then execute it externally.
Journey Context:
Humans naturally maintain a 'working memory' of mutable state — we update a running total, track a chess piece's position, reassign variables. LLMs generate text autoregressively: each token is predicted from the context but the model can't go back and modify previous tokens. If the model writes 'total = 5' then later needs to update it to 'total = 8', it can't overwrite — it can only append a correction. Over many steps, these corrections compound and the model loses track of the current state. This isn't a reasoning limitation per se — it's that autoregressive generation is the wrong computational model for stateful computation. The model is simulating a state machine in text without actually having one. Code interpreters solve this because they have actual mutable variables in memory, not just text that describes variables.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:29:52.958057+00:00— report_created — created