chore: remove redundant trailing newlines in mem0/__init__.py

Cleans up the placeholder blank lines added in the earlier CI trigger commit (#5123). Side-effect: this commit touches mem0/** so it satisfies the ci.yml path filter and unblocks the required build_mem0 / build_embedchain checks for this docs PR.
docs(cli): add Agent Mode + mem0 identify to /platform/cli
2026-05-14 21:32:29 +05:30 · 2026-05-14 21:27:13 +05:30 · 2026-05-14 21:23:21 +05:30
24 changed files with 156 additions and 286 deletions
@@ -12,7 +12,7 @@
      "name": "mem0",
      "source": "./mem0-plugin",
      "description": "Mem0 memory layer for AI applications. Add persistent memory, personalization, and semantic search to Claude workflows.",
-      "version": "0.1.3"
+      "version": "0.1.2"
    }
  ]
 }
@@ -86,25 +86,7 @@ See the [migration guide](https://docs.mem0.ai/migration/oss-v2-to-v3) for upgra
 ## 🚀 Quickstart Guide <a name="quickstart"></a>
-### Sign up as an agent
+> **Agent Mode — for AI agents setting up Mem0 autonomously.** Run `mem0 init --agent --agent-caller <your-name> --json` (after `pip install mem0-cli` or `npm install -g @mem0/cli`), replacing `<your-name>` with your AI agent identity (e.g. `claude-code`, `cursor`, `codex`). This mints an evaluation Mem0 API key in <5 seconds — no email, no dashboard, no OTP. If you forgot to pass `--agent-caller`, run `mem0 identify <your-name>` after init. Use the key immediately against the Platform or the MCP server. The human owner can claim ownership later with `mem0 init --email <their-email>`: memories transfer, the same key keeps working, and the agent isn't disrupted.
 AI agents can mint a working Mem0 API key in under five seconds — no email, no dashboard, no OTP. Four commands end-to-end:
 ```bash
 # 1. Install
 npm install -g @mem0/cli      # or: pip install mem0-cli
 # 2. Sign up as an agent (replace `claude-code` with your name)
 mem0 init --agent --agent-caller claude-code
 # 3. Add a memory
 mem0 add "I am using mem0"
 # 4. Search
 mem0 search "am I using mem0"
 ```
 The human owner can claim the account later with `mem0 init --email <their-email>` — same key, memories preserved. Full guide: [Sign up as an agent](https://docs.mem0.ai/platform/agent-signup).
 | | Library | Self-Hosted Server | Cloud Platform |
 |---|---------|-------------------|----------------|
@@ -153,7 +135,6 @@ See the [self-hosted docs](https://docs.mem0.ai/open-source/overview) for config
 1. Sign up on [Mem0 Platform](https://app.mem0.ai?utm_source=oss&utm_medium=readme)
 2. Embed the memory layer via SDK or API keys
 3. Using hosted Qdrant vectors? See the [Platform migration guide](https://docs.mem0.ai/migration/oss-to-platform) to import them into Mem0 Platform.
 ### CLI
@@ -1,6 +1,6 @@
 {
  "name": "@mem0/cli",
-  "version": "0.2.6",
+  "version": "0.2.5",
  "description": "The official CLI for mem0 — the memory layer for AI agents",
  "type": "module",
  "bin": {
@@ -247,7 +247,7 @@ export async function claimViaOtp(
 		printError(`Claim failed: ${detail}`);
 		if (errCode === "email_already_claimed") {
 			console.log(
-				`  ${dim("Tip: this email already has a Mem0 account. Sign in at app.mem0.ai with your existing credentials.")}`,
+				`  ${dim("Tip: this email already has a Mem0 account. Sign in there and run `mem0 link <key>` to attach this agent.")}`,
 			);
 		}
 		process.exit(1);
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 [project]
 name = "mem0-cli"
-version = "0.2.6"
+version = "0.2.5"
 description = "The official CLI for mem0 — the memory layer for AI agents"
 readme = "README.md"
 license = "Apache-2.0"
@@ -218,7 +218,7 @@ def claim_via_otp(config: Mem0Config, *, email: str, code: str | None = None) ->
        print_error(err_console, f"Claim failed: {detail}")
        if code_str == "email_already_claimed":
            console.print(
-                f"  [{DIM_COLOR}]Tip: this email already has a Mem0 account. Sign in at app.mem0.ai with your existing credentials.[/]"
+                f"  [{DIM_COLOR}]Tip: this email already has a Mem0 account. Sign in there and run `mem0 link <key>` to attach this agent.[/]"
            )
        raise typer.Exit(1)
@@ -1323,13 +1323,6 @@ See the [TypeScript SDK migration guide](https://docs.mem0.ai/migration/ts-v2-to
 <Tab title="CLI">
 <Update label="2026-05-16" description="Python v0.2.6 / Node v0.2.6">
 **Bug Fixes:**
 - **Claim flow error message:** The `email_already_claimed` tip in `mem0 init --email` previously suggested running `mem0 link <key>` — a command that doesn't exist. Replaced with honest copy pointing the user to sign in at app.mem0.ai with their existing credentials ([#5152](https://github.com/mem0ai/mem0/pull/5152))
 </Update>
 <Update label="2026-05-14" description="Python v0.2.5 / Node v0.2.5">
 **New Features:**
@@ -40,7 +40,6 @@
                    "icon": "rocket",
                    "pages": [
                      "platform/overview",
                      "platform/agent-signup",
                      "vibecoding",
                      "platform/mem0-mcp",
                      "platform/cli",
@@ -157,27 +157,27 @@ mode: "custom"
    </a>
    <a
-      href="/platform/agent-signup"
+      href="/platform/cli"
      className="group flex h-full flex-col overflow-hidden rounded-2xl border border-gray-200 dark:border-zinc-800/40 bg-white dark:bg-zinc-900/40 transition hover:border-primary/60 hover:bg-gray-50 dark:hover:bg-zinc-900"
    >
      <img
        className="block dark:hidden aspect-[2/1] w-full object-cover"
        src="/images/docs thumbnails/light/CLI.png"
-        alt="Sign up as an agent thumbnail"
+        alt="CLI thumbnail"
        style={{pointerEvents: "none"}}
      />
      <img
        className="hidden dark:block aspect-[2/1] w-full object-cover"
        src="/images/docs thumbnails/dark/CLI.png"
-        alt="Sign up as an agent thumbnail"
+        alt="CLI thumbnail"
        style={{pointerEvents: "none"}}
      />
      <div className="flex flex-1 flex-col gap-2 px-4 pb-4 pt-3 text-left">
        <h3 className="text-base font-semibold text-gray-900 dark:text-zinc-100 group-hover:text-primary">
-          Sign up as an agent
+          CLI
        </h3>
        <p className="text-sm text-gray-600 dark:text-zinc-400">
-          For AI agents: mint a Mem0 API key in under five seconds — no email, no dashboard. Four commands to your first memory.
+          Manage memories directly from your terminal. Built for developers and AI agents.
        </p>
      </div>
    </a>
@@ -159,7 +159,6 @@ If the user is on a pre-current major (Python < 2, TS < 3, or Platform `output_f
 - [Introduction](https://docs.mem0.ai/introduction) [Both]: Use when the user wants a one-page overview of how memory fits between the LLM and the app.
 - [Vibe Code with Mem0](https://docs.mem0.ai/vibecoding) [Both]: Use when the user is in Claude Code, Cursor, or Windsurf and wants memory wired into their editor.
 - [Platform Overview](https://docs.mem0.ai/platform/overview) [Platform]: Use when the user picks the managed product - 4-line integration, sub-50ms retrieval, dashboard.
 - [Sign up as an agent](https://docs.mem0.ai/platform/agent-signup) [Platform]: Use when an AI agent needs to mint a Mem0 API key autonomously - four commands, no email or dashboard, human claims ownership later.
 - [Platform vs Open Source](https://docs.mem0.ai/platform/platform-vs-oss) [Both]: Use when the user is deciding between managed and self-hosted.
 - [Platform Quickstart](https://docs.mem0.ai/platform/quickstart) [Platform]: Use for the first Platform integration - API key plus `MemoryClient.add/search`.
 - [Platform CLI](https://docs.mem0.ai/platform/cli) [Platform]: Use when the user wants to manage Platform memories from the terminal.
@@ -14,15 +14,11 @@ Move your Mem0 implementation to managed infrastructure with enterprise features
 | --------------------- | -------------- | ---------------------------- |
 | Infrastructure & Code | Low (~30 mins) | None (Parallel run possible) |
 <Info>
  Using Mem0 Open Source with **hosted Qdrant**? You can migrate your existing memories to Mem0 Platform with a one-line script below.
 </Info>
 <Info>
  **Why migrate to Platform?**
  - **Time to Market**: Set up in 5 minutes vs 30+ minutes for OSS configuration
-  - **Enterprise Ready**: Audit logs, workspace governance, and dedicated support
+  - **Enterprise Ready**: SOC2 Type II compliance, GDPR support, audit logs
  - **Advanced Features**: Webhooks, memory export, analytics dashboard, custom categories
  - **Multi-tenancy**: Organizations, projects, and team management out of the box
  - **Zero Infrastructure**: No vector database, LLM provider, or maintenance overhead
@@ -38,21 +34,7 @@ Move your Mem0 implementation to managed infrastructure with enterprise features
 ## Migrate
-### 1. Import Memories Into Platform
+### 1. Install or Update SDK
 If your Mem0 Open Source setup uses **hosted Qdrant** as the vector store, you can import your existing memories to Mem0 Platform with one command:
 ```bash
 curl -fsSL https://raw.githubusercontent.com/mem0ai/mem0/main/scripts/oss-to-platform-migrate.sh | bash
 ```
 <Note>
  This migration script currently supports **hosted Qdrant only**. Support for local Qdrant, pgvector, and other vector stores is coming soon.
 </Note>
 If you are using a different vector store and want to migrate to Platform, please contact Mem0 support and we’ll send you a custom migration script for your setup.
 ### 2. Install or Update SDK
 Ensure you have the latest version of the SDK, which supports both OSS and Platform clients.
@@ -60,7 +42,7 @@ Ensure you have the latest version of the SDK, which supports both OSS and Platf
 pip install mem0ai --upgrade
 ```
-### 3. Update Initialization
+### 2. Update Initialization
 Switch from the local `Memory` class to the managed `MemoryClient`.
@@ -93,7 +75,7 @@ client = MemoryClient(api_key="m0-...")
  Run `client.get_all(filters={"user_id": "test_connection"})` to verify your API key works. It should return an empty list or valid results.
 </Info>
-### 4. Update Retrieval Calls (Critical)
+### 3. Update Retrieval Calls (Critical)
 <Warning>
  **Critical Change**: Platform uses v2 endpoints that require filtering parameters to be nested inside a `filters` dictionary.
@@ -1,106 +0,0 @@
 ---
 title: Sign up as an agent
 description: "Zero-friction signup for AI agents — mint a working Mem0 API key in under five seconds. No email, no dashboard, no OTP."
 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.
 ## The 4-command demo
 <CodeGroup>
 ```bash npm
 # 1. Install
 npm install -g @mem0/cli
 # 2. Sign up as an agent (replace `claude-code` with your name)
 mem0 init --agent --agent-caller claude-code
 # 3. Push a memory
 mem0 add "I am using mem0"
 # 4. Verify
 mem0 search "am I using mem0"
 ```
 ```bash pip
 # 1. Install
 pip install mem0-cli
 # 2. Sign up as an agent (replace `claude-code` with your name)
 mem0 init --agent --agent-caller claude-code
 # 3. Push a memory
 mem0 add "I am using mem0"
 # 4. Verify
 mem0 search "am I using mem0"
 ```
 </CodeGroup>
 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.
 </Tip>
 ## 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_id` was provisioned so `mem0 add` / `mem0 search` work without explicit scope flags.
 - 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:
 ```bash
 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.
 - **All memories transfer** to the human's account.
 - **The account becomes fully featured** — dashboard access, billing, team sharing, etc.
 Pass `--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:
 ```
 Daily Agent Mode signup limit reached for this network (5/day).
 Try again from a different IP or after midnight UTC.
 ```
 Unclaimed agent accounts get the standard Mem0 free-tier quotas. The human owner can upgrade after claiming.
 ## What's next
 <CardGroup cols={2}>
 <Card title="CLI Reference" icon="terminal" href="/platform/cli">
 Full command-by-command reference for `mem0 add`, `mem0 search`, `mem0 list`, and the rest.
 </Card>
 <Card title="Memory Operations" icon="database" href="/core-concepts/memory-operations/add">
 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.
 </Card>
 <Card title="Platform Overview" icon="star" href="/platform/overview">
 The full Mem0 Platform feature set once you claim your account.
 </Card>
 </CardGroup>
@@ -25,11 +25,44 @@ pip install mem0-cli
 ```
 </CodeGroup>
 ## Agent Mode — zero-friction signup for AI agents
 <Tip>
-**Looking for Agent Mode signup?** See [Sign up as an agent](/platform/agent-signup) — install, signup, first memory in four commands.
+**If you're an AI agent reading this**, skip the rest of this page until you've run the command below. Everything else assumes you already have an API key.
 </Tip>
-## Authentication
+AI agents (Claude Code, Cursor, Codex, Cline, Aider, …) can mint a working Mem0 API key in under five seconds with no email, no dashboard, and no OTP:
 ```bash
 mem0 init --agent --agent-caller claude-code
 ```
 Replace `claude-code` with your agent's name (e.g. `cursor`, `codex`, `cline`, `aider`, or any custom string). The CLI saves the key to `~/.mem0/config.json` and prints a notice you should surface to your human user. The human can claim the account later — same API key keeps working, memories transfer.
 <Tip>
 **Forgot `--agent-caller`?** Run `mem0 identify <your-name>` after init — same key, just back-fills the attribution. Idempotent.
 </Tip>
 ### Claiming an Agent Mode key (humans)
 When the human is ready, they claim ownership of the agent's key by running:
 ```bash
 mem0 init --email you@yourcompany.com
 ```
 The CLI detects the existing unclaimed Agent Mode config, sends a verification code, and upgrades the shadow account in-place: **the API key never changes, all memories transfer to the human's account, and the agent isn't disrupted**. Pass `--code 123456` for fully non-interactive flows.
 ### Plugin sync
 When you save a Mem0 API key (any flow — Agent Mode, email, or `--api-key`), the CLI also propagates it to ecosystem touchpoints **that already exist**:
 - `~/.claude/settings.json` → `env.MEM0_API_KEY` (Claude Code plugin env injection)
 - `~/.zshrc` / `~/.bashrc` → existing `export MEM0_API_KEY=` lines
 Sync is idempotent and **never creates new entries** — it only updates entries you've already set up. Failures are best-effort and never block the canonical write to `~/.mem0/config.json`.
 ## Authentication (humans)
 Run the interactive setup wizard to configure your API key:
@@ -83,6 +116,7 @@ Interactive setup wizard. Prompts for your API key and default user ID.
 mem0 init
 mem0 init --api-key m0-xxx --user-id alice
 mem0 init --email alice@company.com
 mem0 init --agent --agent-caller claude-code   # zero-friction signup for AI agents
 ```
 If an existing configuration is detected, the CLI will ask for confirmation before overwriting. Use `--force` to skip the prompt (useful in CI/CD pipelines).
@@ -95,13 +129,24 @@ mem0 init --api-key m0-xxx --user-id alice --force
 |------|-------------|
 | `--api-key` | API key (skip prompt) |
 | `-u, --user-id` | Default user ID (skip prompt) |
-| `--email` | Login via email verification code |
+| `--email` | Login via email verification code (also used to claim an Agent Mode key) |
 | `--code` | Verification code (use with `--email` for non-interactive login) |
 | `--agent` | Bootstrap an Agent Mode account — no email, no dashboard |
 | `--agent-caller` | Self-declared agent identity for Agent Mode signups (e.g. `claude-code`, `cursor`) |
 | `--source` | Channel attribution for analytics (e.g. `github`, `hn`, `ph`) |
 | `--force` | Overwrite existing config without confirmation |
-<Note>
+### `mem0 identify`
-AI agents should use `mem0 init --agent` — see [Sign up as an agent](/platform/agent-signup).
+
-</Note>
+Tag your active Agent Mode key with the AI agent that's using it. Run this once after `mem0 init --agent` if you didn't pass `--agent-caller` on init. Idempotent — re-running just overwrites the value.
 ```bash
 mem0 identify claude-code
 mem0 identify cursor
 mem0 identify my-custom-bot
 ```
 The CLI calls `PATCH /api/v1/auth/agent_mode/caller/` against the active key. Only works on unclaimed Agent Mode keys; the backend rejects with 400 otherwise. Agent names are sanitized server-side (lowercased, restricted to `[a-z0-9._/-]`, truncated to 32 chars).
 ### `mem0 add`
@@ -142,24 +142,6 @@ iconType: "solid"
        Setting this environment variable will prevent Mem0 from collecting and sending any usage data, ensuring complete privacy for your application.
    </Accordion>
    <Accordion title="How do I delete my Mem0 account?">
        You can delete your Mem0 account at any time directly from the dashboard:
        1. Sign in at [app.mem0.ai](https://app.mem0.ai).
        2. Go to **Settings → Account**.
        3. Click **Delete account** and confirm.
        Deletion is immediate and irreversible. The following is removed:
        - Your user profile and login credentials
        - All memories, agents, and runs you created
        - API keys and access tokens issued to your account
        - Organizations you solely own, along with their data
        - Your membership in any shared organizations (the orgs themselves are not affected)
        Any application still using your old API keys will start receiving `401 Unauthorized` responses immediately. If you'd like to use Mem0 again later, you can create a new account at any time — it will start fresh with no data carried over.
    </Accordion>
 </AccordionGroup>
@@ -12,7 +12,7 @@ Mem0 is the memory engine that keeps conversations contextual so users never rep
 - **Personalized replies**: Memories persist across users and agents, cutting prompt bloat and repeat questions.
 - **Hosted stack**: Mem0 runs the vector store, graph services, and rerankers—no provisioning, tuning, or maintenance.
- **Enterprise controls**: Audit logs and workspace governance ship by default for production readiness.
+- **Enterprise controls**: SOC 2, audit logs, and workspace governance ship by default for production readiness.
 <AccordionGroup>
  <Accordion title="What you get with Mem0 Platform" icon="sparkles">
@@ -22,7 +22,7 @@ Mem0 is the memory engine that keeps conversations contextual so users never rep
    | Fast setup | Add a few lines of code and you’re production-ready—no vector database or LLM configuration required. |
    | Production scale | Automatic scaling, high availability, and managed infrastructure so you focus on product work. |
    | Advanced features | Graph memory, webhooks, multimodal support, and custom categories are ready to enable. |
-    | Enterprise ready | Audit logs, workspace governance, and dedicated support keep security and governance covered. |
+    | Enterprise ready | SOC 2 Type II, GDPR compliance, and dedicated support keep security and governance covered. |
  </Accordion>
 </AccordionGroup>
@@ -7,10 +7,6 @@ iconType: "solid"
 Get started with Mem0 Platform's hosted API in under 5 minutes. This guide shows you how to authenticate and store your first memory.
 <Note>
 **Are you an AI agent?** See [Sign up as an agent](/platform/agent-signup) — mint a working API key in four commands, no email or dashboard required.
 </Note>
 ## Prerequisites
 - Mem0 Platform account (<a href="https://app.mem0.ai?utm_source=oss&utm_medium=platform-quickstart" rel="nofollow">Sign up here</a>)
@@ -1,6 +1,6 @@
 {
  "name": "mem0",
-  "version": "0.1.3",
+  "version": "0.1.2",
  "description": "Mem0 memory layer for AI applications. Add persistent memory, personalization, and semantic search to Claude workflows using the Mem0 Platform MCP server.",
  "author": {
    "name": "Mem0",
@@ -1,45 +0,0 @@
 # Changelog
 All notable changes to the Mem0 plugin will be documented in this file.
 ## 0.1.3
 ### Fixed
 - **user_id resolution no longer derives from `MEM0_API_KEY`.** v0.1.2 changed the resolver to fall back to `"mem0-" + sha256(MEM0_API_KEY)[:12]` ahead of `$USER`, which silently moved every existing user to a new bucket on update. Memories written under the previous `$USER` value became unreachable from the plugin. Resolution is now back to `MEM0_USER_ID` → `$USER` → `"default"`.
 - Dropped the "regardless of which machine you're on" line from the SessionStart bootstrap, since cross-machine consolidation now requires setting `MEM0_USER_ID` explicitly.
 ### Notes for users upgrading from 0.1.2
 - The `~/.mem0/identity.json` cache file is no longer read or written. Safe to delete.
 - If you wrote memories during the v0.1.2 window, they live under `mem0-<sha256(api_key)[:12]>`. To recover: temporarily `export MEM0_USER_ID=mem0-<hash>`, search/export, then unset.
 - Want a single bucket across machines (the original goal of #5076)? Set `MEM0_USER_ID` explicitly in your shell profile. The plugin will not auto-derive one.
 ## 0.1.2
 ### Added
 - Deterministic `user_id` resolver (`_identity.sh` / `_identity.py`) — **reverted in 0.1.3, see above.**
 - SessionStart-compact handler (`capture_compact_summary.py`) that stores the post-compaction summary as a memory with `metadata.type=compact_summary`.
 - Coding-taxonomy setup script (`setup_coding_categories.py`) — one-shot `project.update(custom_categories=[...])` for `architecture_decisions`, `anti_patterns`, `task_learnings`, `tooling_setup`, `bug_fixes`, `coding_conventions`, `user_preferences`.
 - Opt-in hook logging via `MEM0_DEBUG=1` → `~/.mem0/hooks.log`.
 - `mem0-mcp` skill replacing the Claude-Code-specific `mem0-codex` skill.
 ### Fixed
 - `session_id` now written to memory metadata (`on_pre_compact.py`).
 - SessionStart bootstrap exits silently when `MEM0_API_KEY` is unset.
 - `block_memory_write.sh` regex tightened to `MEMORY.md` / `.claude/memory/*` — no longer blocks `docs/memory/*.md`.
 - Removed duplicate PreCompact write path (kept agent-driven, dropped the parallel Python REST entry from `hooks.json` / `cursor-hooks.json`).
 - Hook-side captures (`session_state`, `compact_summary`) now set `expiration_date = today + 90 days`.
 ## 0.1.1
 - Cursor plugin fully functional (`#4547`).
 - Codex plugin support and integration docs (`#4665`).
 - Codex lifecycle hooks via opt-in installer (`#4917`).
 - Removed invalid keys from Claude plugin config (`#4821`).
 ## 0.1.0
 - Initial release: Mem0 plugin for Claude Code and Cursor (`#4518`).
@@ -1,17 +1,59 @@
-"""Resolve mem0 user_id.
+"""Resolve mem0 user_id with deterministic priority.
 Resolution priority:
  1. MEM0_USER_ID env var (explicit override)
-  2. $USER, else "default"
+  2. ~/.mem0/identity.json cache (pinned to current MEM0_API_KEY fingerprint)
  3. Derived: "mem0-" + sha256(MEM0_API_KEY)[:12]
  4. Fallback: $USER, else "default"
 Same MEM0_API_KEY across machines yields the same user_id, which fixes
 the "47 user buckets per account" symptom from running on multiple
 laptops with different $USER values.
 """
 from __future__ import annotations
 import hashlib
 import json
 import os
 from datetime import datetime, timezone
 _CACHE_PATH = os.path.expanduser("~/.mem0/identity.json")
 def resolve_user_id() -> str:
    explicit = os.environ.get("MEM0_USER_ID", "").strip()
    if explicit:
        return explicit
    api_key = os.environ.get("MEM0_API_KEY", "").strip()
    if api_key:
        digest = hashlib.sha256(api_key.encode("utf-8")).hexdigest()
        fingerprint = digest[:8]
        try:
            with open(_CACHE_PATH, "r") as f:
                cached = json.load(f)
            if cached.get("api_key_fingerprint") == fingerprint and cached.get("user_id"):
                return cached["user_id"]
        except (OSError, json.JSONDecodeError):
            pass
        derived = "mem0-" + digest[:12]
        try:
            os.makedirs(os.path.dirname(_CACHE_PATH), exist_ok=True)
            with open(_CACHE_PATH, "w") as f:
                json.dump(
                    {
                        "user_id": derived,
                        "source": "api_key",
                        "api_key_fingerprint": fingerprint,
                        "resolved_at": datetime.now(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ"),
                    },
                    f,
                )
        except OSError:
            pass
        return derived
    return os.environ.get("USER") or "default"
@@ -2,13 +2,54 @@
 #
 # Resolution priority:
 #   1. MEM0_USER_ID env var (explicit override)
-#   2. $USER, else "default"
+#   2. ~/.mem0/identity.json cache (pinned to current MEM0_API_KEY fingerprint)
 #   3. Derived: "mem0-" + sha256(MEM0_API_KEY)[:12]
 #   4. Fallback: $USER, else "default"
 #
 # Same MEM0_API_KEY across machines yields the same user_id, which fixes
 # the "47 user buckets per account" symptom from running on multiple
 # laptops with different $USER values.
 _mem0_sha256() {
  if command -v sha256sum >/dev/null 2>&1; then
    sha256sum | cut -d' ' -f1
  else
    shasum -a 256 | cut -d' ' -f1
  fi
 }
 _mem0_resolve_identity() {
  if [ -n "${MEM0_USER_ID:-}" ]; then
    printf '%s' "$MEM0_USER_ID"
    return
  fi
  local api_key="${MEM0_API_KEY:-}"
  local cache="$HOME/.mem0/identity.json"
  if [ -n "$api_key" ]; then
    local digest
    digest=$(printf '%s' "$api_key" | _mem0_sha256)
    local fp="${digest:0:8}"
    if [ -f "$cache" ]; then
      local cached_fp cached_id
      cached_fp=$(jq -r '.api_key_fingerprint // ""' "$cache" 2>/dev/null)
      cached_id=$(jq -r '.user_id // ""' "$cache" 2>/dev/null)
      if [ "$cached_fp" = "$fp" ] && [ -n "$cached_id" ]; then
        printf '%s' "$cached_id"
        return
      fi
    fi
    local derived="mem0-${digest:0:12}"
    mkdir -p "$HOME/.mem0" 2>/dev/null && \
      printf '{"user_id":"%s","source":"api_key","api_key_fingerprint":"%s","resolved_at":"%s"}\n' \
        "$derived" "$fp" "$(date -u +%FT%TZ)" > "$cache" 2>/dev/null
    printf '%s' "$derived"
    return
  fi
  printf '%s' "${USER:-default}"
 }
@@ -36,7 +36,7 @@ echo "## Mem0 Identity"
 echo ""
 echo "Active user_id: \`$MEM0_RESOLVED_USER_ID\`"
 echo ""
-echo "Always include \`{\"user_id\": \"$MEM0_RESOLVED_USER_ID\"}\` (wrapped in an \`AND\` clause) in every \`search_memories\` filter and as \`user_id\` on every \`add_memory\` call. This keeps the agent's MCP calls aligned with the bucket the hooks write to."
+echo "Always include \`{\"user_id\": \"$MEM0_RESOLVED_USER_ID\"}\` (wrapped in an \`AND\` clause) in every \`search_memories\` filter and as \`user_id\` on every \`add_memory\` call. This keeps memories under one bucket regardless of which machine you're on."
 echo ""
 if [ "$SOURCE" = "startup" ]; then
@@ -22,7 +22,6 @@ export interface SearchMemoryOptions {
  topK?: number;
  threshold?: number;
  rerank?: boolean;
  latestOnly?: boolean;
  fields?: string[];
  categories?: string[];
 }
@@ -33,7 +32,6 @@ export interface GetAllMemoryOptions {
  pageSize?: number;
  startDate?: string;
  endDate?: string;
  latestOnly?: boolean;
  categories?: string[];
 }
@@ -63,24 +63,6 @@ describe("MemoryClient - search()", () => {
    expect(getFetchBody(call!).filters).toEqual({ user_id: "u1" });
  });
  test("serializes latestOnly as latest_only", async () => {
    const extra = new Map<string, { status: number; body: unknown }>();
    extra.set("/v3/memories/search/", {
      status: 200,
      body: { results: [] },
    });
    const mock = setupMockFetch(extra);
    const client = new MemoryClient({ apiKey: TEST_API_KEY });
    await client.search("test", {
      filters: { user_id: "u1" },
      latestOnly: true,
    });
    const call = findFetchCall(mock, "/v3/memories/search/", "POST");
    expect(getFetchBody(call!).latest_only).toBe(true);
  });
  test("passes complex OR filters through to the API body", async () => {
    const extra = new Map<string, { status: number; body: unknown }>();
    extra.set("/v3/memories/search/", {
@@ -282,22 +264,4 @@ describe("MemoryClient - getAll() entity param rejection", () => {
    await client.getAll({ filters: { user_id: "u1" } });
    expect(findFetchCall(mock, "/v3/memories/", "POST")).toBeDefined();
  });
  test("serializes latestOnly as latest_only", async () => {
    const extra = new Map<string, { status: number; body: unknown }>();
    extra.set("/v3/memories/", {
      status: 200,
      body: { results: [] },
    });
    const mock = setupMockFetch(extra);
    const client = new MemoryClient({ apiKey: TEST_API_KEY });
    await client.getAll({
      filters: { user_id: "u1" },
      latestOnly: true,
    });
    const call = findFetchCall(mock, "/v3/memories/", "POST");
    expect(getFetchBody(call!).latest_only).toBe(true);
  });
 });
@@ -156,4 +156,3 @@ known_first_party = ["mem0", "mem0_cli"]
 # isort scope kept aligned with [tool.ruff.lint.isort] above.
 # black-equivalent profile here matches the formatter behaviour ruff applies.
 # Plugin-version bumps need a touch here to fire required CI checks (path-filter trap).
 # Last touched: plugin v0.1.3