Report #99300
[architecture] Agent loses state between restarts or cannot remember users across sessions
Use two persistence layers: a checkpointer for short-term thread-scoped state \(messages, interrupted steps\) and a store for durable cross-thread facts. Pass the same thread\_id to resume a conversation; write user preferences and extracted facts to the store with namespace/key lookup from any node.
Journey Context:
Developers often store chat history in memory or dump it to a database manually, which breaks on interruption and mixes transient session state with long-term knowledge. LangGraph's persistence docs define checkpointers \(save graph state per super-step, scoped to a thread\_id\) and stores \(application-defined key-value data across threads\). Checkpointers give pause/resume, human-in-the-loop, and time travel; stores give user profiles and shared knowledge. Using both avoids conflating transient conversation state with durable memory and makes migration and backups easier.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T04:54:17.041286+00:00— report_created — created