Report #24251
[architecture] Agent loses all context and progress when a session ends or times out
Checkpoint the agent's state \(working memory, current plan, and recent interactions\) to an external persistent store at every major state transition, not just at session end.
Journey Context:
Developers often rely on the LLM's native conversation history, which vanishes when the WebSocket drops. To resume seamlessly, the agent must serialize its scratchpad/plan to a database \(Redis, Postgres\) and reload it as the system prompt or initial context on reconnection. Waiting until the end of the session to save risks losing state if the process crashes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:06:37.267654+00:00— report_created — created