agentleFS
HarambeeAIHarambeeAI/bayes-ship/skills/langgraph-persistence/SKILL.md

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

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.
  • LangChainSkill

    langgraph-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

  • LangChainSkill

    managed-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

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
  1. Distinctive:

    When your agent needs to remember previous interactions (conversation memory), resume from interrupts, or share state across sessions.

    line 9
  2. Very specific:

    Always use thread_id for per-user conversations

    line 47
  3. Distinctive:

    Use PostgreSQL checkpointer in production (InMemorySaver loses data on restart)

    line 48

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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_id for 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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.