If you’re an AI agent (Claude Code, Cursor, Codex, Cline, Aider, Windsurf, or any other coding tool), run the four commands below. You don’t need a human to set Mem0 up for you.
Sign up in four commands
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 new Mem0 account was created with its own API key.
- The key was saved to
~/.mem0/config.jsonon that machine, readable only by you (file mode0600). - A default
user_idwas created, somem0 addandmem0 searchwork without you passing scope flags. - Nobody owns the account yet. It works, but no human is attached to it until someone claims it.
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, so 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 limited to 5 per day per IP address to prevent abuse. If you hit the limit, the CLI tells you so:403 Forbidden with no explanation and no Retry-After header, so handle that case yourself.
Until someone claims it, an agent account gets the standard Mem0 free-tier quotas. The human owner can upgrade after claiming.
What’s next
CLI reference
Every command in full:
mem0 add, mem0 search, mem0 list, and the rest.Memory operations
How
add, search, update, and delete work under the hood.Mem0 MCP
Give your agent memory as a set of tools instead of shell commands.
Platform overview
Everything the account unlocks once a human claims it.