langgraph-persistence
Skill1 starsChanged 7 months agoMITView on GitHub
Implement checkpointers, thread_id-based memory, and cross-thread persistence for LangGraph agents. Use when building agents that remember conversation history or need durable execution across sessions.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- langchain-ai/langchain-skillstheir own version, first seen Oct 13, 2026
- willlee1995/skillstheir own version, first seen Oct 13, 2026
- gerald-donkor/poli-inteltheir own version, first seen Oct 11, 2026
- workatustadarshajay/CareLoop-AItheir own version, first seen Oct 9, 2026
- zoujindouGithub/agent-skillstheir own version, first seen Sep 2, 2026
- buduan/soul-graphtheir own version, first seen Jun 7, 2026
Used with
Projects with it also use langgraph-cli, managed-deep-agents and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LangChainSkilllanggraph-cli
INVOKE THIS SKILL when using the langgraph CLI to scaffold, develop, build, or deploy LangGraph applications. Covers langgraph new, dev, build, up, deploy, and langgraph.json configuration.
Also in 4 projects that use this
LangChainSkillmanaged-deep-agents
INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can actually do, then scaffolding and deploying it. Covers the file-based project layout; define_deep_agent / defineDeepAgent; instructions, skills, memory, identity, tools, MCP servers, connections, middleware, sandboxes, schedules, channels, and evals; the mda CLI; GitHub deployments; and Context Hub.
Also in 4 projects that use this
- +4 more from langchain-ai
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- langchain-ai/langchain-skills★ 1.3ksame name
- langchain-ai/skills-benchmarks★ 116same name
- buduan/soul-graph★ 2same name
- gerald-donkor/poli-intel★ 1same name
- willlee1995/skills★ 1same name
- zoujindouGithub/agent-skills★ 1same name
- workatustadarshajay/CareLoop-AI★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-settingsSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
When your agent needs to remember previous interactions (conversation memory), resume from interrupts, or share state across sessions.
- Very specific: line 47
Always use thread_id for per-user conversations
- Distinctive: line 48
Use PostgreSQL checkpointer in production (InMemorySaver loses data on restart)
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LangGraph Persistence
When to use
When your agent needs to remember previous interactions (conversation memory), resume from interrupts, or share state across sessions.
In-memory checkpointer (development)
from langgraph.checkpoint.memory import InMemorySaver
checkpointer = InMemorySaver()
app = graph.compile(checkpointer=checkpointer)
# Thread-based memory
config = {"configurable": {"thread_id": "user-123"}}
result = app.invoke({"messages": [HumanMessage("Hello")]}, config)
# Next call with same thread_id continues the conversation
result = app.invoke({"messages": [HumanMessage("What did I say?")]}, config)PostgreSQL checkpointer (production)
from langgraph.checkpoint.postgres import PostgresSaver
checkpointer = PostgresSaver.from_conn_string("postgresql://...")
app = graph.compile(checkpointer=checkpointer)Cross-thread memory (shared knowledge)
from langgraph.store.memory import InMemoryStore
store = InMemoryStore()
# Store facts accessible across all threads
store.put(("user", "preferences"), "theme", {"value": "dark"})Rules
- Always use
thread_idfor per-user conversations - Use PostgreSQL checkpointer in production (InMemorySaver loses data on restart)
- Store user preferences in the Store, not the checkpointer (checkpointer is for conversation state)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

