JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: navigation (#5900)

Browse Source
This commit is contained in:
Kartik
2026-07-01 22:48:23 +05:30
committed by GitHub
parent f2532f072f
commit 207f65deda
107 changed files with 951 additions and 1296 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/platform/agent-signup.mdx
+7 -7
View File
@@ -5,7 +5,7 @@ icon: "robot"
iconType: "solid"
---
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.
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.
## The 4-command demo
@@ -39,14 +39,14 @@ mem0 search "am I using mem0"
```
</CodeGroup>
That's it: under 30 seconds from a fresh shell to a working memory store.
That's it. Under 30 seconds from a fresh shell to a working memory store.
## 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.
<Tip>
**Forgot `--agent-caller` on init?** Run `mem0 identify <your-name>` after the fact: same key, just back-fills the attribution. Idempotent.
**Forgot `--agent-caller` on init?** Run `mem0 identify <your-name>` after the fact, same key, just back-fills the attribution. Idempotent.
</Tip>
## What happened when you ran `mem0 init --agent`?
@@ -54,13 +54,13 @@ Replace `claude-code` in the `init` command with your actual agent name (`cursor
- 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_id` was provisioned so `mem0 add` / `mem0 search` work without explicit scope flags.
- The account is **unclaimed**: no human owns it yet.
- The account is **unclaimed**; no human owns it yet.
Every command run against this key prints a one-line reminder asking you to surface the claim instructions to your human user.
## 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:
When the human is ready to take ownership of the agent's account (and all the memories it has accumulated), they run:
```bash
mem0 init --email you@yourcompany.com
@@ -68,7 +68,7 @@ mem0 init --email you@yourcompany.com
The CLI detects the existing Agent Mode config, sends a verification code, and upgrades the shadow account in-place:
- **The API key never changes**: the agent isn't disrupted.
- **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.
@@ -97,7 +97,7 @@ How `add`, `search`, `update`, and `delete` work under the hood.
</Card>
<Card title="Mem0 MCP" icon="plug" href="/platform/mem0-mcp">
Connect agents to Mem0 via the Model Context Protocol: alternative integration path.
Connect agents to Mem0 via the Model Context Protocol, as an alternative integration path.
</Card>
<Card title="Platform Overview" icon="star" href="/platform/overview">