local backend keeps long-term memory in the current process’s memory. Memory text is embedded by an embedding model and written to a llama-index in-memory vector index; retrieval recalls by semantic similarity.
Because the data lives only in process memory, it is cleared when the process exits and cannot be shared across processes. The backend is therefore intended for local development, debugging, and quickly validating the end-to-end long-term memory flow — not for production.
When to use
- Quickly try the full long-term memory flow locally, from write to cross-session retrieval;
- Develop and debug agent logic without introducing external storage;
- Write demos or unit tests where data does not need to persist.
Dependencies
Thelocal backend relies on vector search, which requires the extensions:
Usage
Parameters
Usually you only passindex or app_name to LongTermMemory. To customize embedding, pass embedding_config through backend_config.
Constructor parameters
backend_config supports the following settings:
Embedding config
embedding_config is an EmbeddingModelConfig with env prefix MODEL_EMBEDDING_:
Environment variables
If
MODEL_EMBEDDING_API_KEY is not set separately, VeADK reuses MODEL_AGENT_API_KEY and then falls back to an auto-fetched Ark token.