langgraph-checkpointing-and-persistence

A guide to LangGraph persistence, which saves a workflow's state between interactions. It covers conversation history, separate conversation threads, recovery after failures, and revisiting earlier states.

In plain words
What is it for?
Use it to keep chatbot conversations, store state during development or with PostgreSQL, inspect past states, update saved state, and support fault recovery.
Why use it?
It removes the need to rebuild context after every interaction and helps workflows continue after interruptions.

Skill for Claude CodeCodex

Part of the langgraph-dev plugin — 21 skills, 4 commands, 1 agent shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/postindustria-tech/agentic-toolkit/langgraph-dev-conversation-memory
Any agent
npx skills add postindustria-tech/agentic-toolkit --skill langgraph-dev-conversation-memory
Clone the repo
git clone --depth 1 https://github.com/postindustria-tech/agentic-toolkit

Made for: Claude Code, Codex.

Or install langgraph-dev, the plugin that ships this one along with the rest of its 21 skills, 4 commands, 1 agent.

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,676 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00110 $0.07676
Opus 5 $0.00055 $0.03838
Sonnet 5 $0.00022 $0.01535
Haiku 4.5 $0.00011 $0.00768

Measured 2d ago against content hash 29dcb68eda3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

langgraph-checkpointing-and-persistence scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (examples/basic-state-inspection.py, examples/fault-tolerance-recovery.py, examples/thread-management.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/langgraph-dev/skills/langgraph-dev-conversation-memory/SKILL.md · 940 lines

How it starts

The opening of the file, as written. The whole thing — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LangGraph Memory and Persistence

LangGraph provides built-in persistence through checkpointers, enabling workflows to maintain state across interactions, support multiple conversation threads, and recover from failures.

Checkpointer Types

InMemorySaver - Development/Testing

from langgraph.checkpoint.memory import InMemorySaver
from langgraph.graph import StateGraph, MessagesState, START, END
from langchain_anthropic import ChatAnthropic

# Create checkpointer for in-memory persistence
checkpointer = InMemorySaver()

# Define the graph
model = ChatAnthropic(model="claude-sonnet-4-5-20250929")

def chatbot(state: MessagesState):
    response = model.invoke(state["messages"])
    return {"messages": [response]}

# Build and compile with checkpointer
builder = StateGraph(MessagesState)
builder.add_node("chatbot", chatbot)
builder.add_edge(START, "chatbot")
builder.add_edge("chatbot", END)
graph = builder.compile(checkpointer=checkpointer)

# Use thread_id to maintain conversation context
config = {"configurable": {"thread_id": "user-123"}}

# Conversation turn 1
result = graph.invoke({"messages": [("user", "Hi, I'm Alice")]}, config)

# Conversation turn 2 - remembers context from turn 1
result = graph.invoke({"messages": [("user", "What's my name?")]}, config)
# Response: "Your name is Alice"

Pros: Zero setup, fast iteration Cons: Data lost on restart - use only for development

SqliteSaver - Local Persistence

# Requires: pip install langgraph-checkpoint-sqlite
from langgraph.checkpoint.sqlite import SqliteSaver
from langgraph.graph import StateGraph, MessagesState, START, END
from langchain_anthropic import ChatAnthropic

model = ChatAnthropic(model="claude-sonnet-4-5-20250929")

def chatbot(state: MessagesState):
    response = model.invoke(state["messages"])
    return {"messages": [response]}

builder = StateGraph(MessagesState)
builder.add_node("chatbot", chatbot)
builder.add_edge(START, "chatbot")
builder.add_edge("chatbot", END)

# Use context manager for proper connection handling
with SqliteSaver.from_conn_string("checkpoints.sqlite") as checkpointer:
    graph = builder.compile(checkpointer=checkpointer)

    config = {"configurable": {"thread_id": "session-456"}}
    result = graph.invoke({"messages": [("user", "Hello!")]}, config)

Read the full file on GitHub · 940 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 940 lines · 110 tokens per session scan A 29dcb68eda3b

Subscribe to this mod's changes

langgraph-checkpointing-and-persistence is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 7,676 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens