
How It Works
Once installed, Auto-Capture runs automatically with no extra configuration:- Auto-Capture (on by default): After conversations, messages are buffered and sent to Membase for extraction and long-term storage. Entities and relationships are automatically extracted into a knowledge graph.
- Auto-Recall (off by default): When enabled, the plugin searches your memories by semantic similarity before every AI turn and injects relevant context. Casual chat is skipped to keep things focused.
- Knowledge Graph: Unlike simple vector memory, Membase stores entities, relationships, and facts in a graph database. Search results include related nodes and edges for richer context.
Setup
Log in to Membase
Configuring Membase
The simplest way to change Membase settings is to just ask your AI in a conversation. No need to edit config files manually. Auto-Recall (inject past memories before each response):~/.openclaw/openclaw.json and ask you to restart the OpenClaw gateway for the change to take effect. Alternatively, you can edit the config directly — see the Configuration section below.
AI Tools
The AI uses these tools autonomously during conversations:| Tool | Description |
|---|---|
membase_search | Search memories by semantic similarity. Supports date filtering (date_from, date_to, timezone) and source filtering (sources, e.g. slack, gmail). Each result includes a relevance score (0–1). Returns episode bundles with related facts. |
membase_store | Save important information to long-term memory. Proactively stores preferences, goals, and context. |
membase_forget | Delete a memory. Shows matches first, then deletes after user confirmation (two-step). |
membase_profile | Retrieve user profile and related memories for session context. |
CLI Commands
Auto-Recall
Runs before every AI response (before_agent_start hook) when enabled.
Queries Membase for relevant memories and injects them as context. Casual chat (greetings, acknowledgments) is skipped. The injected context respects a maxRecallChars budget to avoid oversized prompts.
Auto-Recall is disabled by default. Enable it in your plugin config:
Auto-Capture
Runs after every AI response (agent_end hook).
Buffers conversation messages per channel and flushes them to Membase for knowledge extraction. Buffers flush after 5 minutes of silence or 20 messages, whichever comes first. At least 2 messages are required before flushing. The last 2 messages are kept as overlap for continuity across batches.
Configuration
All configuration is managed through OpenClaw’s plugin settings or~/.openclaw/openclaw.json:
| Key | Type | Default | Description |
|---|---|---|---|
apiUrl | string | https://api.membase.so | Membase API URL. Override for self-hosted. |
tokenFile | string | ~/.openclaw/credentials/openclaw-membase.json | OAuth token cache file path. Stored outside the plugin directory so it survives updates. |
autoRecall | boolean | false | Inject relevant memories before every AI turn. |
autoCapture | boolean | true | Automatically store conversations to memory. |
maxRecallChars | number | 4000 | Max characters of memory context per turn (500–16000). |
debug | boolean | false | Enable verbose debug logs. |
~/.openclaw/openclaw.json and stores rotating tokens in tokenFile.
Legacy keys (accessToken, refreshToken) are migrated automatically when present.
Enabling AI Tools
The plugin automatically adds itself totools.alsoAllow on first load. If it doesn’t take effect, restart the gateway once.
If you prefer to configure it manually, use tools.alsoAllow (not tools.allow) to avoid breaking your existing profile allowlist:
"openclaw-membase" in tools.alsoAllow expands to all tools registered by this plugin and is appended on top of the active profile. Using tools.allow instead can silently break your profile allowlist. Without this entry, the AI still receives memory context via auto-recall but cannot call the tools explicitly.
Managing Plugins
Useopenclaw plugins to manage installed plugins, check status, and update versions.

Updating the Plugin
To update Membase to the latest version:How Membase Differs
| Simple vector memory | Membase | |
|---|---|---|
| Storage | Flat embeddings | Hybrid: vector embeddings + Neo4j knowledge graph |
| Search | Vector similarity only | Vector + graph traversal (entities, relationships, facts) |
| Extraction | Store raw text | AI-powered entity/relationship extraction |
| Auth | API key | OAuth 2.0 with PKCE (no secrets to manage) |
| Ingest | Synchronous | Async pipeline with background graph sync |

