OpenClaw Memory
Automatically manages project configurations to ensure that the local chat history stored in the journal directory is excluded from version control via gitignore rules.
Records AI conversation turns, including user inputs, agent responses, and code modifications, into local Markdown journal files to create a searchable and persistent history.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenClaw Memory Search my history for the solution we found for the database timeout bug."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenClaw Memory
Your AI conversations disappear after every session. OpenClaw Memory fixes that.
Every time you chat with an AI coding assistant, valuable context — decisions, solutions, debugging steps — vanishes when the session ends. The next session starts from zero.
OpenClaw Memory automatically records every conversation turn to local Markdown files, making your entire AI chat history searchable and browsable. No cloud, no database — just plain text files in your project.
How It Works
You chat with AI → Every turn auto-saved to .openclaw_memory/journal/2026-02-24.md
→ Search past conversations via MCP tool or web viewerEach journal entry captures the complete conversation: timestamps, model used, your input, the AI's full response, and any code changes made.
Related MCP server: Amber
Quick Start
1. Install
pip install claw-memory2. Initialize in your project
cd your-project
claw-memory initThis creates:
.openclaw_memory/journal/— where chat history lives.cursor/mcp.json— connects the MCP server to Cursor.cursor/rules/memory.mdc— tells the AI agent to auto-record
3. Restart Cursor — that's it. Every conversation is now being recorded.
Searching Past Conversations
The AI agent can search your history automatically. Just ask naturally:
"We discussed this before, what was the solution?"
"Last time we fixed a similar bug, how did we do it?"
The agent will call memory_search() behind the scenes and find matching conversations.
Search via Web Viewer
# Single project (current directory)
claw-memory web
# Multiple projects — scan a parent directory
claw-memory web --scan-dir ~/projectsOpens a browser-based viewer where you can:
Browse journal files by date
Full-text search across all conversations
Dark/light mode
Multi-project view: use
--scan-dirto scan a parent directory and browse all projects in one place, with sidebar grouped by project
What Gets Recorded
Each conversation turn is saved as Markdown:
## 14:32 | claude-4-opus
### User
How do I fix the N+1 query problem in the user list endpoint?
### Agent
The issue is in `api/users.py` where each user triggers a separate query for their roles...
### Code Changes
- `api/users.py` (modified)
- `tests/test_users.py` (modified)MCP Tools
Tool | Purpose |
| Record a complete conversation turn |
| Append to the last turn (for long responses) |
| Search chat history by keyword |
Storage
All data is stored locally in .openclaw_memory/journal/ as plain Markdown files — one file per day. No database, no cloud sync. You own your data.
The .openclaw_memory/ directory is auto-gitignored to prevent accidental commits of chat history.
Project Isolation
Each project gets its own .openclaw_memory/ directory. MCP tools always operate on the current project only.
To view multiple projects together, use the web viewer with --scan-dir.
License
Apache 2.0
Available Tools
3 toolsmemory_log_conversationA
Record one full conversation turn to today's journal.
You MUST pass the complete user message and your entire reply — no truncation, no summary, no "..." or "see above". If your reply is very long, pass the first part here then use memory_log_conversation_append() for the rest.
Args:
user_message: The user's full message in this turn.
agent_response: Your full reply (complete text, every paragraph).
model: The model used for this response (e.g. "claude-4-opus").
code_changes: Optional. Files created/modified, e.g. "- src/foo.py (created)".
title: Optional. One-line summary for this turn; if empty, derived from first line of user_message.
Inputs: user_message (required), agent_response, model, code_changes, +1 more. Returns: result
memory_log_conversation_appendA
Append more text to the last Agent section in today's journal.
Use after memory_log_conversation() when your full reply did not fit in one call. Can be called multiple times; each chunk is appended to the same turn.
Args: agent_response_chunk: Next part of your reply to append (no truncation).
Inputs: agent_response_chunk (required). Returns: result
memory_searchB
Search chat history for a keyword, returning full conversation turns.
Args: query: Text to search for (case-insensitive). since: Only search from this date onward (YYYY-MM-DD format). max_results: Max turns to return (0 = no limit).
Inputs: query (required), since, max_results. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes with no overlap: memory_log_conversation records a complete conversation turn, memory_log_conversation_append extends that recording when needed, and memory_search retrieves past conversations. Each tool serves a unique function in the conversation logging workflow.
The naming follows a consistent memory_verb_noun pattern with minor deviations: memory_log_conversation and memory_search fit perfectly, while memory_log_conversation_append is slightly longer but maintains the same prefix structure. All use snake_case consistently.
Three tools is ideal for this server's purpose of conversation memory management. It covers the core workflow of logging, appending when responses are long, and searching history without being overly complex or insufficient for the domain.
The toolset provides solid coverage for basic conversation memory operations: logging, extending logs, and searching. A minor gap exists in lacking update/delete capabilities for recorded conversations, but agents can work effectively with the provided CRD (create, read, delete via omission) functionality.
Maintenance
Related MCP Connectors
Persistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients.
Persistent memory for AI agents to retain, retrieve, and recall conversation context through MCP.
Hosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing.
Persistent memory for AI agents across Claude, ChatGPT and any MCP client.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to automatically log and manage conversation history with developers in structured markdown format. Provides powerful search and context suggestions to help AI understand project history and maintain continuity across sessions.41MIT
- AlicenseAqualityBmaintenanceGives your AI persistent memory across conversations. Stores facts automatically, finds them by meaning using hybrid search with query expansion, and organizes everything into topics without manual tagging.291MIT
- AlicenseNot gradedqualityBmaintenanceProvides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.MIT
- AlicenseNot gradedqualityCmaintenanceEnables capturing and storing AI coding decisions as markdown, and provides MCP tools for assistants to query and record those decisions so they respect past architectural choices.MIT