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

SkillsGate: Open Source Marketplace for AI Coding Agent Skills
SkillsGate is an open source marketplace that indexes 45,000+ skills for AI coding agents like Claude Code, Cursor, and Windsurf. It provides semantic search with vector embeddings and one-command installation via npx.

Claude Code Prompt Architecture Reverse-Engineered for Local Models
A clean-room reimplementation of Claude Code's 26-prompt architecture is now available on GitHub, offering system prompts, tool prompts, safety rules, memory compression, and verification patterns for building coding agents on local models like Ollama, llama.cpp, or vLLM.

OpenClaw Skill Server for Indian Market Analysis and Trading
An open-source trading terminal for Indian markets has been integrated as an OpenClaw skill server, allowing agents to pull market data and run multi-agent analysis via HTTP. The system provides structured trade plans with entry prices, stop-losses, and targets across three risk profiles.

User-built PTC for Claude Code shows 40-65% token savings on analysis tasks, not code writing
A developer built a local PTC implementation called Thalamus for Claude Code and analyzed 79 real sessions, finding 40-65% token savings on analysis tasks but near-zero savings on code-writing tasks. The agent used execute() primarily for general Python computation rather than batching tool calls.