Report #20863
[architecture] Agent loses track of complex multi-step task progress because state is implicitly held only in the conversational context
Implement a scratchpad or working memory state object that is explicitly updated \(read/write\) at every agent step, persisted outside the LLM context window, and injected fresh on every turn.
Journey Context:
Relying on the LLM context window to track state in a long agentic workflow is fragile. Once the conversation exceeds the window, older steps are truncated, and the agent forgets what it already did. The fix is to externalize the state machine. The tradeoff is that injecting the full state every turn consumes context tokens, but it guarantees the agent always has the current ground truth of its progress, preventing infinite loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:25:37.203579+00:00— report_created — created