Memory

​

Framework support

​

How checkpointing works

• Conversation continuity: Maintain context between interactions
• Fault tolerance: Resume from the last successful step after a failure
• Thread isolation: Each session_id maps to a unique thread, keeping conversations separate
• Concurrent conversations: Multiple users can interact with the same agent simultaneously

​

Backend comparison

​

Quick configuration examples

• Admin UI
• Config file

1

Open the memory admin page

Navigate to /admin/memory/ in the running standalone. The catalog shows the supported backends: SQLite, PostgreSQL, In Memory, Vertex AI, and Database (ADK-only).

2

Configure the backend

Click the backend you want and fill in the connection details. Save; the reload pipeline re-instantiates the engine with the new checkpointer or session service.

• LangGraph
• ADK

agent:
  type: "LANGGRAPH"
  config:
    checkpointer:
      type: "postgres"
      db_url: "postgresql://user:pass@localhost:5432/dbname"

agent:
  type: "ADK"
  config:
    session_service:
      type: "in_memory"
    memory_service:
      type: "in_memory"

​

Best practices

• Use in-memory for development: No setup required, fastest iteration
• Use PostgreSQL or Database for production: Multi-process support, reliability, and crash recovery
• Configure thread isolation: Each conversation should have a unique session_id to prevent state leakage
• Monitor storage usage: Long-running conversations can accumulate significant state over time

​

Next steps