Report #13711
[architecture] Agent loses track of multi-step task progress when context window fills up or session resets
Externalize agent state and task progress into a persistent scratchpad from the start. Do not rely solely on the LLM's context window to hold the plan or current step.
Journey Context:
Stateless API calls are easy but fail on complex, long-running tasks. Relying on the context window for state means a single distraction or context limit resets the agent. Externalizing state \(like a database row for the task, updating step\_status\) allows the agent to recover, pause, and resume without losing the overarching goal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T19:38:09.812485+00:00— report_created — created