Graphzustand speichern (Checkpoints)

Warum den Zustand persistieren?

In-Memory-Checkpointer

from langgraph.checkpoint.memory import MemorySaver

checkpointer = MemorySaver()
app = graph.compile(checkpointer=checkpointer)

Postgres-Checkpointer

from langgraph.checkpoint.postgres import PostgresSaver

checkpointer = PostgresSaver.from_conn_string('postgresql://...')
await checkpointer.setup()   # create tables
app = graph.compile(checkpointer=checkpointer)

Sqlite-Checkpointer

from langgraph.checkpoint.sqlite import SqliteSaver
import sqlite3

conn = sqlite3.connect('agents.db', check_same_thread=False)
checkpointer = SqliteSaver(conn)

Thread-IDs

config = {'configurable': {'thread_id': 'user-42-conversation-1'}}
result = app.invoke({'messages': [...]}, config)

Einen Lauf fortsetzen

# Some hours later:
app.invoke(None, config)

Den Zustand untersuchen

snapshot = app.get_state(config)
print(snapshot.values)         # current state dict
print(snapshot.next)           # which node is next
print(snapshot.created_at)

Zustandsverlauf

for snapshot in app.get_state_history(config):
    print(snapshot.created_at, snapshot.values)

Einen Lauf abzweigen

app.update_state(config, {'plan': 'a different plan'})
app.invoke(None, config)   # continue with the new plan

Human-in-the-Loop mit interrupt_before

app = graph.compile(
    checkpointer=checkpointer,
    interrupt_before=['send_email']
)

result = app.invoke({'messages': [...]}, config)
# Agent paused. Human inspects state.
# When approved:
app.invoke(None, config)

Nach der Bearbeitung fortsetzen

app.update_state(config, {'email_draft': 'final version'})
app.invoke(None, config)

Kostenverfolgung über Checkpoints hinweg

class State(TypedDict):
    cost_usd: Annotated[float, lambda a, b: a + b]

# Every LLM-calling node adds to it.

Bereinigung

await checkpointer.delete(thread_id='old-thread')

Threads fortsetzen

Zusammenfassung