12 KiB
@mem0/openclaw-mem0
Long-term memory for OpenClaw agents, powered by Mem0.
Your agent forgets everything between sessions. This plugin fixes that — it stores conversations, extracts what matters, and brings it back when relevant. Enable autoRecall and autoCapture in config to run this automatically, or use agent tools for explicit control.
Requirements
Check your OpenClaw version:
openclaw --version
# OpenClaw 2026.4.15 (041266a)
| OpenClaw Version | Plugin Support |
|---|---|
>= 2026.4.15 |
Fully supported |
Quick Start
The fastest way is to install directly from your OpenClaw chat — no CLI or config editing needed.
Copy and paste this into your OpenClaw chat (Telegram, WhatsApp, default chat, or any channel where your agent lives):
Setup Mem0 from mem0.ai/claw-setup
OpenClaw installs the plugin, prompts you for your email, and connects your Mem0 account with OTP verification. See Chat Setup below for the full walkthrough.
If you prefer the OpenClaw CLI, or are setting up self-hosted / open-source mode, see Manual Config and Open-Source (Self-hosted) below.
Platform (Mem0 Cloud)
There are two ways to set up @mem0/openclaw-mem0 on the Mem0 platform:
- Chat setup (recommended) — run the setup inside any OpenClaw chat. No config editing, no API key handling.
- Manual config — edit
openclaw.jsondirectly.
Chat Setup (Recommended)
You no longer need manual config editing to get started. Everything happens inside the OpenClaw chat itself.
-
Send the setup command to your OpenClaw agent. Open any OpenClaw channel and paste:
Setup Mem0 from mem0.ai/claw-setupOpenClaw responds with a Mem0 setup card and asks: "What's your email address? I'll send you a verification code to connect your Mem0 account."
-
Enter your email. Type your email address and send it. Mem0 replies: "Check your email for a 6-digit code and paste it here."
-
Paste the OTP. Copy the 6-digit code from your email inbox and paste it into the chat. You'll see: "Connected to Mem0."
That's it. No API key, no config file editing, no environment variables. The plugin is now active and auto-capture and auto-recall are running on every turn.
The chat flow uses the same underlying config as manual setup — it writes
apiKeyanduserIdintoopenclaw.jsonfor you. You can still open the file to inspect or override values afterward.
Manual Config
-
Install the plugin via the OpenClaw CLI:
openclaw plugins install @mem0/openclaw-mem0 -
Get your API key from app.mem0.ai.
-
Select the plugin as your memory backend in
openclaw.json. Either initialize via the CLI:openclaw mem0 init --api-key <your-key> --user-id <your-user-id>Or add the full config to your
openclaw.json:{ "plugins": { "slots": { "memory": "openclaw-mem0" }, "entries": { "openclaw-mem0": { "enabled": true, "config": { "apiKey": "${MEM0_API_KEY}", "userId": "alice" } } } } }
Note: OpenClaw memory plugins load through an exclusive slot, so install alone does not activate the plugin. You must set
plugins.slots.memoryas shown above.
Open-Source (Self-hosted)
No Mem0 key needed. Vectors are stored locally in SQLite at ~/.mem0/vector_store.db — no external database required.
Defaults: text-embedding-3-small (OpenAI) for embeddings, gpt-5-mini (OpenAI) for fact extraction — requires OPENAI_API_KEY. For a fully local setup, use Ollama for both LLM and embeddings.
Interactive Setup (Recommended)
Run the guided 4-step wizard:
openclaw mem0 init --mode open-source
The wizard walks you through:
- LLM provider — OpenAI (
gpt-5-mini), Ollama (llama3.1:8b, local), or Anthropic (claude-sonnet-4-5-20250514) - Embedding provider — OpenAI (
text-embedding-3-small) or Ollama (nomic-embed-text, local) - Vector store — Qdrant (
http://localhost:6333) or PGVector (PostgreSQL) - User ID — your memory namespace identifier
Each step tests connectivity (Ollama, Qdrant, PGVector) before proceeding.
Non-Interactive Setup
For CI/CD, scripts, or agent-driven setup — pass all options as flags:
# Fully local with Ollama + Qdrant
openclaw mem0 init --mode open-source \
--oss-llm ollama --oss-embedder ollama --oss-vector qdrant
# OpenAI + Qdrant
openclaw mem0 init --mode open-source \
--oss-llm openai --oss-llm-key <key> \
--oss-embedder openai --oss-embedder-key <key> \
--oss-vector qdrant
# Anthropic LLM + OpenAI embeddings + PGVector
openclaw mem0 init --mode open-source \
--oss-llm anthropic --oss-llm-key <key> \
--oss-embedder openai --oss-embedder-key <key> \
--oss-vector pgvector --oss-vector-user postgres --oss-vector-password secret
# JSON output (for LLM agents)
openclaw mem0 init --mode open-source --oss-llm ollama --oss-embedder ollama --oss-vector qdrant --json
All --oss-* flags
| Flag | Description |
|---|---|
--oss-llm <provider> |
openai, ollama, or anthropic |
--oss-llm-key <key> |
API key for LLM provider |
--oss-llm-model <model> |
Override default LLM model |
--oss-llm-url <url> |
Base URL (Ollama only) |
--oss-embedder <provider> |
openai or ollama |
--oss-embedder-key <key> |
API key for embedder |
--oss-embedder-model <model> |
Override default embedder model |
--oss-embedder-url <url> |
Base URL (Ollama only) |
--oss-vector <provider> |
qdrant or pgvector |
--oss-vector-url <url> |
Qdrant server URL (default: http://localhost:6333) |
--oss-vector-host <host> |
PGVector host |
--oss-vector-port <port> |
PGVector port |
--oss-vector-user <user> |
PGVector user |
--oss-vector-password <pw> |
PGVector password |
--oss-vector-dbname <db> |
PGVector database name |
--oss-vector-dims <n> |
Override embedding dimensions |
Manual Config
Minimal config — uses OpenAI defaults:
{
"plugins": {
"slots": {
"memory": "openclaw-mem0"
},
"entries": {
"openclaw-mem0": {
"enabled": true,
"config": {
"mode": "open-source",
"userId": "alice"
}
}
}
}
}
Customize the embedder, vector store, or LLM via the oss block:
"config": {
"mode": "open-source",
"userId": "alice",
"oss": {
"embedder": { "provider": "openai", "config": { "model": "text-embedding-3-small" } },
"vectorStore": { "provider": "qdrant", "config": { "url": "http://localhost:6333" } },
"llm": { "provider": "openai", "config": { "model": "gpt-5-mini" } }
}
}
All oss fields are optional. See the Mem0 OSS docs for supported providers.
How It Works
Auto-Recall (autoRecall: true) — Before the agent responds, the plugin searches Mem0 for relevant memories and injects them into context.
Auto-Capture (autoCapture: true) — After the agent responds, the conversation is filtered through a noise-removal pipeline and sent to Mem0. New facts get stored, stale ones updated, duplicates merged.
Both are opt-in. Once enabled, they run silently — no prompting, no manual calls required. Without them, the agent can still use memory tools (memory_add, memory_search, etc.) explicitly.
Memory Scopes
- Session (short-term) — Scoped to the current conversation via
run_id. Recalled alongside long-term memories. - User (long-term) — Persistent across all sessions. Default for
memory_add.
Multi-Agent Isolation
Each agent gets its own memory namespace automatically via session key routing (agent:<name>:<uuid> maps to userId:agent:<name>). Single-agent setups are unaffected.
Agent Tools
Eight tools are registered for agent use:
| Tool | Description |
|---|---|
memory_search |
Search by natural language query. Supports scope (session, long-term, all), categories, filters, and agentId. |
memory_add |
Store facts. Accepts text or facts array, category, importance, longTerm, metadata. |
memory_get |
Retrieve a single memory by ID. |
memory_list |
List all memories. Filter by userId, agentId, scope. |
memory_update |
Update a memory's text in place. Preserves history. |
memory_delete |
Delete by memoryId, query (search-and-delete), or all: true (requires confirm: true). |
memory_event_list |
List recent background processing events. Platform mode only. |
memory_event_status |
Get status of a specific event by ID. Platform mode only. |
CLI
All commands: openclaw mem0 <command>. All commands support --json for machine-readable output (for LLM agents).
# Memory operations
openclaw mem0 add "User prefers TypeScript over JavaScript"
openclaw mem0 search "what languages does the user know"
openclaw mem0 search "preferences" --scope long-term
openclaw mem0 get <memory_id>
openclaw mem0 list --user-id alice --top-k 20
openclaw mem0 update <memory_id> "Updated preference text"
openclaw mem0 delete <memory_id>
openclaw mem0 delete --all --user-id alice --confirm
openclaw mem0 import memories.json
# Management
openclaw mem0 init # interactive setup
openclaw mem0 init --mode open-source --oss-llm ollama # non-interactive OSS
openclaw mem0 init --api-key <key> --user-id alice # non-interactive platform
openclaw mem0 status
openclaw mem0 config show
openclaw mem0 config get api_key
openclaw mem0 config set user_id alice
# Events (platform only)
openclaw mem0 event list
openclaw mem0 event status <event_id>
# Memory consolidation
openclaw mem0 dream
openclaw mem0 dream --dry-run
# JSON output (any command)
openclaw mem0 search "preferences" --json
openclaw mem0 list --json
openclaw mem0 status --json
openclaw mem0 help --json # discover all commands + flags
Configuration Reference
General
| Key | Type | Default | Description |
|---|---|---|---|
mode |
"platform" | "open-source" |
"platform" |
Backend mode |
userId |
string |
OS username | User identifier. All memories scoped to this value. |
autoRecall |
boolean |
false |
Inject relevant memories before each turn |
autoCapture |
boolean |
false |
Extract and store facts after each turn |
topK |
number |
5 |
Max memories returned per recall |
searchThreshold |
number |
0.5 |
Minimum similarity score (0-1) |
Platform Mode
| Key | Type | Default | Description |
|---|---|---|---|
apiKey |
string |
— | Required. Mem0 API key (supports ${MEM0_API_KEY}) |
customInstructions |
string |
(built-in) | Custom extraction rules |
customCategories |
object |
(12 defaults) | Category name to description map |
Open-Source Mode
All fields optional. Defaults: text-embedding-3-small embeddings, local SQLite vector store (~/.mem0/vector_store.db), gpt-5-mini LLM.
| Key | Type | Default | Description |
|---|---|---|---|
customPrompt |
string |
(built-in) | Extraction prompt |
oss.embedder.provider |
string |
"openai" |
Embedding provider |
oss.embedder.config |
object |
— | Provider config (apiKey, model, baseURL) |
oss.vectorStore.provider |
string |
"memory" |
Vector store provider (see list above) |
oss.vectorStore.config |
object |
— | Provider config (host, port, collectionName, dbPath) |
oss.llm.provider |
string |
"openai" |
LLM provider |
oss.llm.config |
object |
— | Provider config (apiKey, model, baseURL) |
oss.historyDbPath |
string |
— | SQLite path for edit history |
