langgraph-persistence

You can persist LangGraph state by configuring a checkpointer backend such as InMemorySaver, SqliteSaver, or PostgresSaver, and providing a unique thread_id during graph invocation to maintain multi-turn memory.

Checkpointing in LangGraph saves graph state at each execution step, enabling durable execution and time travel. You need it for applications requiring multi-turn memory, session recovery, or replaying graph states from specific points.

You separate conversation histories by assigning a unique thread_id to each graph invocation. This thread-based scoping isolates checkpointed states, ensuring each user or session maintains an independent contextual memory.

Yes, LangGraph persistence supports subgraph scoping controls for interrupts and multi-turn memory. Checkpointing applies across subgraphs, allowing durable execution and state recovery within complex graph architectures.

Yes, PostgresSaver is a supported checkpointer backend for LangGraph persistence in production deployments. It provides durable state management and checkpointing alongside SqliteSaver and InMemorySaver for different environmental needs.

You share long-term memory across different LangGraph threads by configuring a runtime store alongside your checkpointer. The store enables cross-thread memory access, allowing subgraphs and separate conversations to retrieve shared persistent data.