When deploying agents to LangSmith, the server provides a built-in Postgres-backed long-term memory store with optional vector search via pgvector. You can replace this with your own BaseStore implementation to use a different storage backend, custom indexing, or specialized search capabilities. You provide a path to an async context manager that yields aDocumentation Index
Fetch the complete documentation index at: https://docs.langchain.com/llms.txt
Use this file to discover all available pages before exploring further.
BaseStore instance, and the server manages the store’s lifecycle automatically.
Define the store
Starting from an existing LangSmith application, create a file that defines an async context manager yielding your custom store. If you are beginning a new project, you can create an app from a template using the CLI.AsyncSqliteStore with semantic search:
SQLite is not recommended for use in production deployments.
When a custom store is configured, it replaces the built-in Postgres store entirely. Capabilities like semantic search and TTL sweeping depend on your implementation.
Configure langgraph.json
Add the store key to your langgraph.json configuration file. The path points to the async context manager you defined earlier.
Start server
Test the server out locally:Deploying
You can deploy this app as-is to LangSmith or to your self-hosted platform.Next steps
- Use a custom checkpointer to replace the built-in checkpoint storage.
- Learn about persistence and memory in LangGraph.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

