If you’re an AI agent (Claude Code, Cursor, Codex, Cline, Aider, Windsurf, or any other autonomous coding tool), you don’t need a human to set up Mem0 for you. Four commands — install, sign up, push a memory, search it — and you have persistent memory.Documentation Index
Fetch the complete documentation index at: https://docs.mem0.ai/llms.txt
Use this file to discover all available pages before exploring further.
The 4-command demo
Identify yourself with --agent-caller
Replace claude-code in the init command with your actual agent name (cursor, codex, cline, aider, or any short label). This attribution helps the Mem0 team understand which agents drive the most usage and prioritize integrations accordingly.
What happened when you ran mem0 init --agent?
- A shadow account was minted on the Mem0 backend with a fresh API key.
- The key was saved to
~/.mem0/config.json(mode 0600) on the machine you ran the command on. - A default
user_idwas provisioned somem0 add/mem0 searchwork without explicit scope flags. - The account is unclaimed — no human owns it yet.
Claiming the account (for the human owner)
When the human is ready to take ownership of the agent’s account — and all the memories it has accumulated — they run:- The API key never changes — the agent isn’t disrupted.
- All memories transfer to the human’s account.
- The account becomes fully featured — dashboard access, billing, team sharing, etc.
--code 123456 to skip the interactive code prompt for fully non-interactive flows.
Rate limits and quotas
Agent Mode signups are rate-limited to 5 per day per IP address to prevent abuse. If you hit the limit, the CLI returns:What’s next
CLI Reference
Full command-by-command reference for
mem0 add, mem0 search, mem0 list, and the rest.Memory Operations
How
add, search, update, and delete work under the hood.Mem0 MCP
Connect agents to Mem0 via the Model Context Protocol — alternative integration path.
Platform Overview
The full Mem0 Platform feature set once you claim your account.