Report #101109
[architecture] How should I persist agent state so it survives crashes and remembers across sessions?
Use a checkpointer for thread-scoped short-term state and a separate store for long-term cross-thread memory. Compile the graph with both: the checkpointer resumes conversation/human-in-the-loop workflows, while the store keeps user preferences, facts, and shared knowledge across threads.
Journey Context:
Many agents conflate conversation history with durable memory and lose everything on restart. Checkpointers save graph-state snapshots tied to a thread\_id, enabling resume, time-travel, and fault tolerance. Stores persist key-value data independently and can be searched from any node. Separating the two avoids bloating the conversation window with long-term facts and prevents accidental cross-talk between users or sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T04:59:54.087894+00:00— report_created — created