langgraph-checkpoint-persql 0.1.0

LangGraph checkpointer backed by PerSQL — durable agent state in an isolated SQLite database per agent.

langgraph-checkpoint-persql

LangGraph checkpointer backed by PerSQL — durable agent state in an isolated SQLite database per agent, provisioned instantly.

pip install langgraph-checkpoint-persql

Usage

import os
from persql import PerSQL
from langgraph.checkpoint.persql import PerSQLSaver

client = PerSQL(token=os.environ["PERSQL_TOKEN"])
checkpointer = PerSQLSaver(client.database("acme/agent-state"))

graph = builder.compile(checkpointer=checkpointer)
config = {"configurable": {"thread_id": "session-42"}}
graph.invoke({"messages": [("user", "hi")]}, config)
graph.invoke({"messages": [("user", "remember me?")]}, config)  # state persists

Async:

from persql import AsyncPerSQL
from langgraph.checkpoint.persql.aio import AsyncPerSQLSaver

async with AsyncPerSQL(token=os.environ["PERSQL_TOKEN"]) as client:
    checkpointer = AsyncPerSQLSaver(client.database("acme/agent-state"))
    graph = builder.compile(checkpointer=checkpointer)
    await graph.ainvoke(inputs, {"configurable": {"thread_id": "session-42"}})

Or let the saver own the client:

with PerSQLSaver.from_token(os.environ["PERSQL_TOKEN"], "acme/agent-state") as cp:
    graph = builder.compile(checkpointer=cp)

Tests run against the SDK's local mode — in-process SQLite, no network, no token:

checkpointer = PerSQLSaver(PerSQL(local=":memory:").database("test/db"))

Per-agent isolation

The saver keys state by thread_id inside one database, like every LangGraph checkpointer. PerSQL's shape lets you go one step further and give each agent (or each run) its own database: provision with client.databases.create(...) or lease a schema-only branch with a scoped token via db.branches. See the PerSQL docs for the per-agent patterns.

Storage and limits

• Two tables, created lazily on first use: checkpoints and checkpoint_writes, the same layout as the official SQLite saver (serialized values are base64 text rather than blobs).
• Every saver call is one HTTP round-trip to the database. LangGraph checkpoints once per super-step, so a remote checkpointer adds wire latency per step — the same trade-off as the official Postgres saver.
• Checkpoint rows land on PerSQL's usage meters like any other write. A typical graph step writes one checkpoint row plus a few pending writes; see persql.com/pricing for rates.
• delete_for_runs, copy_thread, and prune are not implemented (the official SQLite saver doesn't implement them either) and raise NotImplementedError.

License

MIT © PerSQL