OpenClaw-Mem0 Plugin Adds Persistent Memory Outside Context Window

The openclaw-mem0 plugin addresses OpenClaw's default memory limitations by storing memories outside the context window, making them immune to context compaction, token limits, and session restarts.
The Memory Problem in OpenClaw
OpenClaw agents are stateless between sessions, with default memory stored in files that must be explicitly loaded. Context compaction summarizes older context to save tokens, causing injected memory to become lossy - large memory files and learned facts get compressed, rewritten, or dropped without warning.
Community workarounds like comprehensive MEMORY.md files, local BM25 + vector search engines, and SQLite-backed session logs all share the same limitation: they store memory inside the context window, making them vulnerable to compaction or session restarts.
How the Plugin Works
The plugin runs two processes on every conversation turn:
- Auto-Recall: Searches Mem0 for relevant memories before the agent responds, injecting matching context (preferences, past decisions, project details) into the working context every turn
- Auto-Capture: Sends each exchange to Mem0 after the agent responds, with Mem0's extraction layer determining what's worth persisting - new facts get stored, outdated ones updated, duplicates merged
Both processes are enabled by default on install.
Memory Structure
The plugin separates memory into two scopes:
- Long-term memories: User-scoped, persist across all sessions (name, tech stack, project structure, decisions)
- Short-term memories: Session-scoped, track active work without polluting long-term store
Both scopes are searched during every recall, with long-term memories surfaced first.
The agent gets five tools for explicit memory management:
memory_search- semantic queries across all memoriesmemory_store- explicitly save a specific factmemory_list- view all stored memoriesmemory_get- retrieve a specific memory by IDmemory_forget- delete memories (GDPR-compliant)
Setup Options
Cloud setup (easiest):
openclaw plugins install @mem0/openclaw-mem0Get an API key from app.mem0.ai, then add to openclaw.json:
{
"openclaw-mem0": {
"enabled": true,
"config": {
"apiKey": "${MEM0_API_KEY}",
"userId": "your-user-id"
}
}
}Fully local, fully private (self-hosted):
Set "mode": "open-source" and bring your own stack:
{
"openclaw-mem0": {
"enabled": true,
"config": {
"mode": "open-source",
"userId": "your-user-id",
"oss": {
"embedder": {
"provider": "ollama",
"config": {
"model": "nomic-embed-text"
}
},
"vectorStore": {
"provider": "qdrant",
"config": {
"host": "localhost",
"port": 6333
}
}
}
}
}
}📖 Read the full source: r/openclaw
👀 See Also

Token Enhancer reduces webpage token usage for AI agents
A developer found that raw HTML from web fetches consumes excessive tokens in AI agent context, with Yahoo Finance pages using 704K tokens. Using Token Enhancer as an MCP server reduced this to 2.6K tokens.

OpenClaw vs Hermes: Choose the Right Self-Hosted AI Agent After 100+ Deployments
After deploying 100+ AI agents for clients, a Reddit user shares hard-won lessons: OpenClaw (149K stars) is the reliable workhorse for single/small fleets; Hermes excels at multi-agent orchestration but has a smaller community.

monk: A skill that silences agent narration to save context and tokens
A Reddit user published 'monk', a skill that strips narration, preambles, and postambles from Claude agent responses, claiming ~54% output token reduction per turn and 29-39% context capacity gain at 100 rounds.

Codesight CLI reduces AI coding agent token usage by scanning codebases
Codesight is a zero-dependency CLI tool that scans TypeScript, Python, and Go projects to generate compact context files, reducing Claude Code exploration tokens by 12.3× on average according to benchmarks from real production codebases.