Lite (the default): storage and search run on your machine with a SQLite graph and local usearch vectors. No Docker, database service or account is needed for local use. Optional LLM extraction through a hosted provider such as Groq calls that provider's service.
Service: connect to the managed SmartMemory backend instead of running storage locally. Run smartmemory setup --mode remote and paste an API key from the SmartMemory dashboard (Dashboard, then Settings, then API Keys). See pricing for current plans and access options.
You choose Lite or Service at smartmemory setup time, not at install time, and you can switch later by re-running setup.
# or a dedicated conda envconda create -n smartmemory python=3.11conda activate smartmemorypip install -U smartmemory
Check your active conda environment. Run conda info --envs. The * marks the active environment. If base is active, create and activate a dedicated environment using the commands above. If your dedicated environment is already active, continue with setup.
One store per environment. Every environment uses the same local store, ~/.smartmemory, and the same daemon port, 9014, unless you point it elsewhere. If more than one environment has SmartMemory installed (for example two conda envs on different versions), give each its own store and daemon port so two versions never write to one store. In conda, set them on the environment and reactivate it:
conda env config vars set SMARTMEMORY_DATA_DIR="$HOME/.smartmemory-myenv" SMARTMEMORY_DAEMON_PORT=9020conda activate myenv
In a venv, export the same two variables in its activate script. The first smartmemory command in a project may ask whether to use these inherited settings: choose use. When smartmemory opens a store that a different version used last, it prints a warning that names both versions.
Lite is the default local mode. It uses local SQLite storage and embedded vectors with zero infrastructure.
smartmemory setup
Choose local storage. Groq is the recommended hosted LLM provider and the default at the LLM provider prompt. For local use without an LLM key, choose none at that prompt and keep the local embedding provider.
Saving needs two local models: the spaCy model en_core_web_sm for entity extraction and the local embedding model (MiniLM). A fresh pip install has neither, and nothing is downloaded when you import the package. smartmemory setup fetches them for you. If you use the library or the smartmemory-core command without running setup, the first save stops with a message that names this command and writes nothing:
smartmemory-core install-models
Downloading spaCy model 'en_core_web_sm' (first run only)...spaCy model 'en_core_web_sm' ready.Local models ready. Saving works now.
It needs network access the first time (roughly 100 MB in total). Later runs find the models and do nothing. No API key is needed.
Service mode connects the SDK and tools to the managed SmartMemory backend.
smartmemory setup --mode remote
Paste an API key from the SmartMemory dashboard when prompted. Keys live under Dashboard, then Settings, then API Keys. See pricing for current plans and API access options. There is no database or server to run locally.
After local setup has downloaded the spaCy and embedding models, verify Lite storage and search with this no-key Python example. It reads setup's configured data directory and spaCy model, while keeping embeddings local and LLM extraction disabled. The Lite context selects SQLite and closes it when the example finishes.
SmartMemory can store and search explicit memories without an LLM key. Choose a provider when you want LLM-backed extraction. Groq is the recommended hosted LLM provider. Re-run sm setup, choose local storage, and select groq. Setup prompts for GROQ_API_KEY and lets you skip the key.
The local setup menu offers these LLM providers:
Setup choice
Authentication or runtime
groq
Groq API key (GROQ_API_KEY), recommended
claude-agent
Claude Agent SDK with OAuth, no API key
anthropic
Anthropic API key (ANTHROPIC_API_KEY)
openai
OpenAI API key (OPENAI_API_KEY)
gemini
Google Gemini API key (GEMINI_API_KEY)
ollama
Local Ollama runtime
lmstudio
Local LM Studio endpoint compatible with the OpenAI API
none
No LLM, local ruler extraction only
Embedding selection is separate. Keep local for embeddings without a provider key. Setup also offers openai and ollama embeddings.
Re-run sm setup and check the selected provider and its key prompt. For the recommended Groq provider, use GROQ_API_KEY. To continue without an LLM key, choose none and keep local embeddings. Explicit memory storage and search work without LLM extraction.