Mem0
Memory layer for agents: plugins for Claude Code, Codex, Cursor and OpenCode, plus a CLI and SDKs that carry context across sessions
Install
export MEM0_API_KEY='your-mem0-api-key'
claude plugin marketplace add mem0ai/mem0
claude plugin install mem0@mem0-plugins --scope user --config api_key="$MEM0_API_KEY"
unset MEM0_API_KEYRequires Python 3.10+, Git and a Mem0 Platform key. Restart Claude Code or run /reload-plugins afterwards.
This is third-party code. Review the repository files before installing.
What it does
Mem0 stores and retrieves memory for AI apps and coding agents. The Claude Code plugin uses hooks to capture messages, changed files and test results, a background worker turns them into Mem0 memories, and the next session starts with up to five relevant ones. Memory splits into shared project memory with conventions and working commands, and personal memory with your preferences. Similar plugins exist for Codex, Cursor, OpenCode, Kimi and Antigravity, and the mem0 and mem0-cli skills teach agents to add memory to apps via the Python and TypeScript SDKs.
Who it is for. For developers annoyed that agents forget the project between sessions, and for those adding memory to their own AI apps.
Good fit when
- The agent relearns build commands and project conventions every session
- A team needs shared agent memory per repository
- You need long-term memory in a chatbot or custom agent
Not a fit when
- Session content cannot go to an external service
- A hand-written CLAUDE.md or AGENTS.md is enough
Example request
Remember that tests in this project run with pnpm test:unit, not npm testLimitations
Agent plugins need a Mem0 Platform key, i.e. the api.mem0.ai cloud service. A fully local setup is only possible with the open-source library or a self-hosted Docker server. Secrets are redacted before sending, but full message text goes to the service.
How to disable. Run claude plugin uninstall mem0@mem0-plugins. Remove the CLI with npm uninstall -g @mem0/cli.
Security check
- Sends session text and changed file paths to an external service
- Stores the Mem0 API key in plugin config
README in short
The README opens with benchmark results for the new memory algorithm on LoCoMo and LongMemEval. Quick start shows the CLI with agent signup, then compares three options: library, self-hosted server and cloud platform. It covers pip and npm installs, running the server with docker compose and integrations with agent frameworks. Apache-2.0 licensed.
FAQ
Can it run without the cloud?
Agent plugins need a platform key. The mem0ai library and a docker compose server can be self-hosted.
How does an agent get a key without signup?
The README describes mem0 init --agent, which issues a working key to the agent that a person can later claim by email.
Related
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
A self-improving agent from Nous Research with a TUI, messaging gateway, cron jobs and skills it writes itself
Anthropic's coding agent for the terminal, IDE and GitHub: understands your codebase, runs tasks and handles git
OpenAI's coding agent that runs locally in your terminal, with IDE and desktop versions