fix(eve): address review — async-write status, reasoning filter, turn-bounded capture, best-effort dedup

Review by @kartik-mem0. Root cause across all four: Mem0's hosted add with infer:true is async and returns a PENDING event before the memory is visible. - store.ts/tools.ts: add() returns AddResult{status,eventId} via parseAddResult; the v3 add path returns {status:"PENDING", event_id}, so remember reports {status:"queued", eventId} for async writes and {status:"saved"} only when resolved. FAILED/unknown status maps to completed, not queued. - messages.ts: drop typed non-text parts (reasoning no longer leaks into memory); bound the captured assistant reply to the current turn and collect all of its text segments (text->tool->text) instead of a stale prior answer. - capture.ts + README + eve.mdx: document operationId dedup as best-effort (lookup+add is not atomic; pending/concurrent windows can double-write); removed the "restart replays cannot write twice" claim. Tests: 68 pass (+15). Added reasoning, tool-only/cross-turn, multi-segment, pending/concurrent capture replay, and PENDING/FAILED add-result cases. Typecheck + build clean.
fix(eve): scope forget, persist capture idempotency, and fail closed
2026-09-12 00:36:29 +09:00 · 2026-09-09 10:48:26 +08:00 · 2026-09-09 10:01:26 +08:00
581 changed files with 29624 additions and 46283 deletions
@@ -8,7 +8,7 @@
      "name": "mem0",
      "source": {
        "source": "local",
-        "path": "./integrations/codex-plugin"
+        "path": "./integrations/mem0-plugin"
      },
      "policy": {
        "installation": "AVAILABLE",
@@ -12,7 +12,7 @@
      "name": "mem0",
      "source": "./integrations/claude-code-plugin",
      "description": "Cross-session memory and token savings for coding agents.",
-      "version": "0.3.3"
+      "version": "0.3.0"
    }
  ]
 }
@@ -8,7 +8,7 @@
      "name": "mem0",
      "source": {
        "source": "local",
-        "path": "./integrations/codex-plugin"
+        "path": "./integrations/mem0-plugin"
      },
      "policy": {
        "installation": "AVAILABLE",
@@ -10,9 +10,9 @@
  "plugins": [
    {
      "name": "mem0",
-      "source": "./integrations/cursor-plugin",
-      "description": "Cross-session memory and token savings for coding agents.",
-      "version": "0.3.3"
+      "source": "./integrations/mem0-plugin",
+      "description": "Mem0 memory layer for AI applications. Add persistent memory, personalization, and semantic search.",
+      "version": "0.2.15"
    }
  ]
 }
@@ -18,14 +18,15 @@ Package workflows keep their own push-to-main and manual triggers. Their `pull_r
 | Python CLI | `cli-python-ci.yml` | Push to main (`cli/python/`), manual | Ruff + pytest + hatch build on Python 3.10, 3.11, 3.12 |
 | Node CLI | `cli-node-ci.yml` | Push to main (`cli/node/`), manual | Biome + tsc + vitest + tsup on Node 20, 22 |
 | OpenClaw | `openclaw-checks.yml` | Push to main (`integrations/openclaw/`), manual | tsc + vitest (Codecov) + tsup on Node 20, 22 |
-| Agent Plugins Python | `agent-plugins-python-checks.yml` | Push to main (shared Python core and native/portable plugin directories), manual | Runtime tests on Python 3.10; full pytest on 3.11, 3.12; ruff + generated-package drift on 3.12 |
-| Agent Plugins TypeScript | `agent-plugins-typescript-checks.yml` | Push to main (`integrations/agent-plugin-core/typescript/`), manual | tsc + node:test on Node 22 |
-| OpenCode Plugin | `opencode-plugin-checks.yml` | Push to main (`integrations/opencode-plugin/`), manual | Bun: tsc + build + dist artifact check |
+| Mem0 Plugin (legacy) | `mem0-plugin-checks.yml` | Push to main (`integrations/mem0-plugin/`, excluding `.opencode-plugin/`), manual | pytest + hook exec bits + JSON manifest validation on Python 3.10, 3.11, 3.12 |
+| Claude Code Plugin | `claude-code-plugin-checks.yml` | Push to main (`integrations/claude-code-plugin/`), manual | pytest + ruff + JSON manifest validation on Python 3.10, 3.11, 3.12 |
+| OpenCode Plugin | `opencode-plugin-checks.yml` | Push to main (`.opencode-plugin/`), manual | Bun: tsc + build + dist artifact check |
 | Pi Agent Plugin | `pi-agent-plugin-checks.yml` | Push to main (`integrations/pi-agent-plugin/`), manual | tsc + vitest + tsup on Node 20, 22 |
 | DeepSeek Harness Plugin | `deepseek-plugin-checks.yml` | Push to main (`integrations/deepseek-plugin/`), manual | tsc + vitest + tsup on Node 20, 22 |
 | n8n Node | `n8n-nodes-mem0-checks.yml` | Push to main (`integrations/n8n-nodes-mem0/`), manual | ESLint + tsc build on Node 20 |
 | Zapier App | `zapier-mem0-checks.yml` | Push to main (`integrations/zapier-mem0/`), manual | tsc + `zapier validate` + offline unit tests on Node 22 |
 | mem0-strands | `mem0-strands-checks.yml` | Push to main (`integrations/mem0-strands/`), manual | Ruff + mypy + pytest + hatch build on Python 3.10, 3.11, 3.12 |
+| Eve | `eve-checks.yml` | Push to main (`integrations/eve/`), manual | tsc + vitest + tsup on Node 24 |
 | docs llms.txt | `docs-llms-txt-check.yml` | Manual | `docs/llms.txt` coverage |
 | GitHub Scripts | inline in `ci-gate.yml` | none | `node` over every `.github/scripts/*.test.js` |

@@ -64,6 +65,7 @@ Requiring `CI Gate` also means fork PRs from first-time contributors cannot merg
 | DeepSeek Harness Plugin | `deepseek-plugin-cd.yml` | `deepseek-plugin-v*` | npm (`@mem0/deepseek-plugin`) |
 | n8n Node | `n8n-nodes-mem0-cd.yml` | `n8n-nodes-mem0-v*` | npm (`@mem0/n8n-nodes-mem0`) |
 | mem0-strands | `mem0-strands-cd.yml` | `mem0-strands-v*` | PyPI (`mem0-strands`) |
+| Eve | `eve-cd.yml` | `eve-v*` | npm (`@mem0/eve`) |

 - Package CD workflows are `workflow_dispatch`-only, with `tag` and `prerelease` inputs. They check out and build the given tag.
 - All publishing uses **OIDC trusted publishing**. No tokens, no secrets.
@@ -1,97 +0,0 @@
-name: Agent Plugins Python Checks
-
-# Python runtime, adapters, generated bundles, and portable plugin validation.
-# On PRs this is invoked by ci-gate.yml (the single required check);
-# push-to-main and manual runs remain standalone.
-on:
-  workflow_dispatch:
-  push:
-    branches: [main]
-    paths:
-      - 'integrations/agent-plugin-core/**'
-      - '!integrations/agent-plugin-core/typescript/**'
-      - 'integrations/mem0-agent-plugin/**'
-      - 'integrations/claude-code-plugin/**'
-      - 'integrations/cursor-plugin/**'
-      - 'integrations/codex-plugin/**'
-      - 'integrations/kimi-plugin/**'
-      - 'integrations/antigravity-plugin/**'
-      - 'marketplace.json'
-      - '.agents/plugins/marketplace.json'
-      - '.claude-plugin/marketplace.json'
-      - '.codex-plugin/marketplace.json'
-      - '.cursor-plugin/marketplace.json'
-      - '.kimi-plugin/marketplace.json'
-      - '.github/workflows/agent-plugins-python-checks.yml'
-  workflow_call:
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: ["3.10", "3.11", "3.12"]
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Install runtime test tooling
-        if: matrix.python-version == '3.10'
-        run: pip install pytest
-
-      - name: Install build and test tooling
-        if: matrix.python-version != '3.10'
-        run: pip install pytest ruff -r integrations/agent-plugin-core/requirements-dev.txt
-
-      - name: Check Python runtime compatibility
-        run: >-
-          python3 -m compileall -q
-          integrations/agent-plugin-core/python
-          integrations/claude-code-plugin/adapters
-          integrations/cursor-plugin/hooks
-          integrations/codex-plugin/hooks
-          integrations/kimi-plugin/hooks
-          integrations/antigravity-plugin/hooks
-
-      - name: Lint
-        if: matrix.python-version == '3.12'
-        run: >-
-          python3 -m ruff check
-          integrations/agent-plugin-core
-          integrations/claude-code-plugin
-          integrations/cursor-plugin
-          integrations/codex-plugin
-          integrations/kimi-plugin
-          integrations/antigravity-plugin
-
-      - name: Verify installable plugins are current
-        if: matrix.python-version == '3.12'
-        run: |
-          for host in claude-code cursor codex kimi antigravity; do
-            python3 integrations/agent-plugin-core/build/build.py "$host" --kind native --check
-          done
-          python3 integrations/agent-plugin-core/build/build.py mem0-agent-plugin --kind portable --check
-
-      - name: Run Python 3.10 runtime tests
-        if: matrix.python-version == '3.10'
-        run: >-
-          python3 -m pytest -q
-          integrations/claude-code-plugin/tests/test_memory_core.py
-          integrations/claude-code-plugin/tests/test_telemetry.py
-
-      - name: Run full tests
-        if: matrix.python-version != '3.10'
-        run: >-
-          python3 -m pytest -q
-          integrations/agent-plugin-core/tests
-          integrations/claude-code-plugin/tests
-          integrations/cursor-plugin/tests
-          integrations/codex-plugin/tests
-          integrations/kimi-plugin/tests
-          integrations/antigravity-plugin/tests
-          --ignore=integrations/claude-code-plugin/tests/integration
@@ -1,42 +0,0 @@
-name: Agent Plugins TypeScript Checks
-
-# Shared TypeScript runtime checks. Each consuming integration keeps its own
-# build workflow, which is also triggered when this shared core changes.
-on:
-  workflow_dispatch:
-  push:
-    branches: [main]
-    paths:
-      - 'integrations/agent-plugin-core/typescript/**'
-      - '.github/workflows/agent-plugins-typescript-checks.yml'
-  workflow_call:
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 10
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: 'pnpm'
-          cache-dependency-path: integrations/agent-plugin-core/typescript/pnpm-lock.yaml
-
-      - name: Install dependencies
-        working-directory: integrations/agent-plugin-core/typescript
-        run: pnpm install --frozen-lockfile
-
-      - name: Type check
-        working-directory: integrations/agent-plugin-core/typescript
-        run: pnpm typecheck
-
-      - name: Run tests
-        working-directory: integrations/agent-plugin-core/typescript
-        run: pnpm test
@@ -38,14 +38,15 @@ jobs:
      cli_python: ${{ steps.filter.outputs.cli_python }}
      cli_node: ${{ steps.filter.outputs.cli_node }}
      openclaw: ${{ steps.filter.outputs.openclaw }}
-      agent_plugins_python: ${{ steps.filter.outputs.agent_plugins_python }}
-      agent_plugins_typescript: ${{ steps.filter.outputs.agent_plugins_typescript }}
+      mem0_plugin: ${{ steps.filter.outputs.mem0_plugin }}
+      claude_code_plugin: ${{ steps.filter.outputs.claude_code_plugin }}
      opencode_plugin: ${{ steps.filter.outputs.opencode_plugin }}
      pi_agent_plugin: ${{ steps.filter.outputs.pi_agent_plugin }}
      deepseek_plugin: ${{ steps.filter.outputs.deepseek_plugin }}
      n8n_nodes_mem0: ${{ steps.filter.outputs.n8n_nodes_mem0 }}
      zapier_mem0: ${{ steps.filter.outputs.zapier_mem0 }}
      mem0_strands: ${{ steps.filter.outputs.mem0_strands }}
+      eve: ${{ steps.filter.outputs.eve }}
      docs_llms_txt: ${{ steps.filter.outputs.docs_llms_txt }}
      github_scripts: ${{ steps.filter.outputs.github_scripts }}
    steps:
@@ -76,43 +77,27 @@ jobs:
              - '.github/workflows/ci-gate.yml'
            openclaw:
              - 'integrations/openclaw/**'
-              - 'integrations/agent-plugin-core/typescript/**'
              - '.github/workflows/openclaw-checks.yml'
              - '.github/workflows/ci-gate.yml'
-            agent_plugins_python:
-              - 'integrations/agent-plugin-core/**'
-              - '!integrations/agent-plugin-core/typescript/**'
-              - 'integrations/mem0-agent-plugin/**'
-              - 'integrations/claude-code-plugin/**'
-              - 'integrations/cursor-plugin/**'
-              - 'integrations/codex-plugin/**'
-              - 'integrations/kimi-plugin/**'
-              - 'integrations/antigravity-plugin/**'
-              - 'marketplace.json'
-              - '.agents/plugins/marketplace.json'
-              - '.claude-plugin/marketplace.json'
-              - '.codex-plugin/marketplace.json'
-              - '.cursor-plugin/marketplace.json'
-              - '.kimi-plugin/marketplace.json'
-              - '.github/workflows/agent-plugins-python-checks.yml'
+            mem0_plugin:
+              - 'integrations/mem0-plugin/**'
+              - '!integrations/mem0-plugin/.opencode-plugin/**'
+              - '.github/workflows/mem0-plugin-checks.yml'
              - '.github/workflows/ci-gate.yml'
-            agent_plugins_typescript:
-              - 'integrations/agent-plugin-core/typescript/**'
-              - '.github/workflows/agent-plugins-typescript-checks.yml'
+            claude_code_plugin:
+              - 'integrations/claude-code-plugin/**'
+              - '.github/workflows/claude-code-plugin-checks.yml'
              - '.github/workflows/ci-gate.yml'
            opencode_plugin:
-              - 'integrations/opencode-plugin/**'
-              - 'integrations/agent-plugin-core/typescript/**'
+              - 'integrations/mem0-plugin/.opencode-plugin/**'
              - '.github/workflows/opencode-plugin-checks.yml'
              - '.github/workflows/ci-gate.yml'
            pi_agent_plugin:
              - 'integrations/pi-agent-plugin/**'
-              - 'integrations/agent-plugin-core/typescript/**'
              - '.github/workflows/pi-agent-plugin-checks.yml'
              - '.github/workflows/ci-gate.yml'
            deepseek_plugin:
              - 'integrations/deepseek-plugin/**'
-              - 'integrations/agent-plugin-core/typescript/**'
              - '.github/workflows/deepseek-plugin-checks.yml'
              - '.github/workflows/ci-gate.yml'
            n8n_nodes_mem0:
@@ -126,6 +111,10 @@ jobs:
              - 'integrations/mem0-strands/**'
              - '.github/workflows/mem0-strands-checks.yml'
              - '.github/workflows/ci-gate.yml'
+            eve:
+              - 'integrations/eve/**'
+              - '.github/workflows/eve-checks.yml'
+              - '.github/workflows/ci-gate.yml'
            docs_llms_txt:
              - 'docs/**/*.mdx'
              - 'docs/llms.txt'
@@ -176,17 +165,18 @@ jobs:
    uses: ./.github/workflows/openclaw-checks.yml
    secrets: inherit

-  agent-plugins-python:
-    name: Agent Plugins Python
+  mem0-plugin:
+    name: Mem0 Plugin
    needs: changes
-    if: needs.changes.outputs.agent_plugins_python == 'true'
-    uses: ./.github/workflows/agent-plugins-python-checks.yml
+    if: needs.changes.outputs.mem0_plugin == 'true'
+    uses: ./.github/workflows/mem0-plugin-checks.yml
+    secrets: inherit

-  agent-plugins-typescript:
-    name: Agent Plugins TypeScript
+  claude-code-plugin:
+    name: Claude Code Plugin
    needs: changes
-    if: needs.changes.outputs.agent_plugins_typescript == 'true'
-    uses: ./.github/workflows/agent-plugins-typescript-checks.yml
+    if: needs.changes.outputs.claude_code_plugin == 'true'
+    uses: ./.github/workflows/claude-code-plugin-checks.yml
    secrets: inherit

  opencode-plugin:
@@ -229,6 +219,13 @@ jobs:
    uses: ./.github/workflows/mem0-strands-checks.yml
    secrets: inherit

+  eve:
+    name: Eve
+    needs: changes
+    if: needs.changes.outputs.eve == 'true'
+    uses: ./.github/workflows/eve-checks.yml
+    secrets: inherit
+
  docs-llms-txt:
    name: docs llms.txt
    needs: changes
@@ -263,14 +260,15 @@ jobs:
      - cli-python
      - cli-node
      - openclaw
-      - agent-plugins-python
-      - agent-plugins-typescript
+      - mem0-plugin
+      - claude-code-plugin
      - opencode-plugin
      - pi-agent-plugin
      - deepseek-plugin
      - n8n-nodes-mem0
      - zapier-mem0
      - mem0-strands
+      - eve
      - docs-llms-txt
      - github-scripts
    if: always()
@@ -0,0 +1,46 @@
+name: Claude Code Plugin Checks
+
+# On PRs this is invoked by ci-gate.yml (the single required check);
+# push-to-main and manual runs remain standalone.
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+    paths:
+      - 'integrations/claude-code-plugin/**'
+      - '.github/workflows/claude-code-plugin-checks.yml'
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install test tooling
+        run: pip install pytest ruff
+        # The plugin itself has zero runtime dependencies — nothing else to install.
+
+      - name: Check manifests are valid JSON
+        working-directory: integrations/claude-code-plugin
+        run: |
+          for f in .claude-plugin/plugin.json .mcp.json hooks/hooks.json; do
+            jq empty "$f" || (echo "Invalid JSON: $f" && exit 1)
+          done
+
+      - name: Lint
+        working-directory: integrations/claude-code-plugin
+        run: python3 -m ruff check .
+
+      - name: Run tests
+        working-directory: integrations/claude-code-plugin
+        run: python3 -m pytest tests -q
@@ -8,7 +8,6 @@ on:
    branches: [main]
    paths:
      - 'integrations/deepseek-plugin/**'
-      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/deepseek-plugin-checks.yml'
  workflow_call:

@@ -85,5 +84,7 @@ jobs:
      - name: Build
        run: cd integrations/deepseek-plugin && pnpm build

-      - name: Verify package artifact
-        run: python3 integrations/agent-plugin-core/conformance/artifacts.py deepseek
+      - name: Verify dist output exists
+        run: |
+          test -f integrations/deepseek-plugin/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
+          test -f integrations/deepseek-plugin/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
@@ -0,0 +1,57 @@
+name: Publish @mem0/eve 📦 to npm
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Release tag to build and publish (e.g. eve-v0.1.0)'
+        required: true
+        type: string
+      prerelease:
+        description: 'Publish under the version preid dist-tag instead of latest'
+        required: false
+        type: boolean
+        default: false
+
+jobs:
+  build-n-publish:
+    name: Build and publish @mem0/eve 📦 to npm
+    if: startsWith(inputs.tag, 'eve-v')
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+    defaults:
+      run:
+        working-directory: integrations/eve
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.tag }}
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '24'
+          registry-url: 'https://registry.npmjs.org'
+          cache: 'pnpm'
+          cache-dependency-path: integrations/eve/pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Build
+        run: pnpm build
+
+      - name: Publish to npm
+        run: |
+          if [ "${{ inputs.prerelease }}" = "true" ]; then
+            PREID=$(node -p "require('./package.json').version.split('-')[1].split('.')[0]")
+            npx npm@latest publish --provenance --access public --tag "$PREID"
+          else
+            npx npm@latest publish --provenance --access public
+          fi
@@ -0,0 +1,85 @@
+name: eve checks
+
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+    paths:
+      - 'integrations/eve/**'
+      - '.github/workflows/eve-checks.yml'
+  workflow_call:
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: 'pnpm'
+          cache-dependency-path: integrations/eve/pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: cd integrations/eve && pnpm install --frozen-lockfile
+
+      - name: Type check
+        run: cd integrations/eve && pnpm typecheck
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: 'pnpm'
+          cache-dependency-path: integrations/eve/pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: cd integrations/eve && pnpm install --frozen-lockfile
+
+      - name: Run tests
+        run: cd integrations/eve && pnpm test
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 9
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: 'pnpm'
+          cache-dependency-path: integrations/eve/pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: cd integrations/eve && pnpm install --frozen-lockfile
+
+      - name: Build
+        run: cd integrations/eve && pnpm build
+
+      - name: Verify dist output exists
+        run: |
+          test -f integrations/eve/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
+          test -f integrations/eve/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
@@ -0,0 +1,58 @@
+name: Mem0 Plugin Checks
+
+# On PRs this is invoked by ci-gate.yml (the single required check);
+# push-to-main and manual runs remain standalone.
+#
+# Covers the Python plugin (scripts/ + tests/). The nested .opencode-plugin/
+# is a separate package with its own workflow (opencode-plugin-checks.yml).
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+    paths:
+      - 'integrations/mem0-plugin/**'
+      - '!integrations/mem0-plugin/.opencode-plugin/**'
+      - '.github/workflows/mem0-plugin-checks.yml'
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        working-directory: integrations/mem0-plugin
+        run: |
+          pip install -r requirements.txt
+          pip install pytest
+
+      - name: Verify hook entry points are executable
+        working-directory: integrations/mem0-plugin
+        run: |
+          missing=$(find scripts -name '*.sh' ! -name '_*' ! -perm -u+x -print)
+          if [ -n "$missing" ]; then
+            echo "Hook entry points must be executable:"
+            echo "$missing"
+            exit 1
+          fi
+
+      - name: Check hook manifests are valid JSON
+        working-directory: integrations/mem0-plugin
+        run: |
+          for f in plugin.json mcp_config.json hooks.json hooks/*.json; do
+            jq empty "$f" || (echo "Invalid JSON: $f" && exit 1)
+          done
+
+      - name: Run tests
+        working-directory: integrations/mem0-plugin
+        run: pytest -q
@@ -8,7 +8,6 @@ on:
    branches: [main]
    paths:
      - 'integrations/openclaw/**'
-      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/openclaw-checks.yml'
  workflow_call:

@@ -94,5 +93,7 @@ jobs:
      - name: Build
        run: cd integrations/openclaw && pnpm build

-      - name: Verify package artifact
-        run: python3 integrations/agent-plugin-core/conformance/artifacts.py openclaw
+      - name: Verify dist output exists
+        run: |
+          test -f integrations/openclaw/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
+          test -f integrations/openclaw/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
@@ -25,7 +25,7 @@ jobs:
      id-token: write
    defaults:
      run:
-        working-directory: integrations/opencode-plugin
+        working-directory: integrations/mem0-plugin/.opencode-plugin
    steps:
      - uses: actions/checkout@v4
        with:
@@ -7,8 +7,7 @@ on:
  push:
    branches: [main]
    paths:
-      - 'integrations/opencode-plugin/**'
-      - 'integrations/agent-plugin-core/typescript/**'
+      - 'integrations/mem0-plugin/.opencode-plugin/**'
      - '.github/workflows/opencode-plugin-checks.yml'
  workflow_call:

@@ -17,7 +16,7 @@ jobs:
    runs-on: ubuntu-latest
    defaults:
      run:
-        working-directory: integrations/opencode-plugin
+        working-directory: integrations/mem0-plugin/.opencode-plugin
    steps:
      - uses: actions/checkout@v4

@@ -32,12 +31,9 @@ jobs:
      - name: Type check
        run: bun run type-check

-      - name: Test
-        run: bun test
-
      - name: Build
        run: bun run build

-      - name: Verify package artifact
-        working-directory: .
-        run: python3 integrations/agent-plugin-core/conformance/artifacts.py opencode
+      - name: Verify dist output exists
+        run: |
+          test -f dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
@@ -8,7 +8,6 @@ on:
    branches: [main]
    paths:
      - 'integrations/pi-agent-plugin/**'
-      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/pi-agent-plugin-checks.yml'
  workflow_call:

@@ -85,5 +84,9 @@ jobs:
      - name: Build
        run: cd integrations/pi-agent-plugin && pnpm build

-      - name: Verify package artifact
-        run: python3 integrations/agent-plugin-core/conformance/artifacts.py pi-agent
+      - name: Verify dist output exists
+        run: |
+          test -f integrations/pi-agent-plugin/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
+          test -f integrations/pi-agent-plugin/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
+          test -f integrations/pi-agent-plugin/dist/entry.js || (echo "Build output missing: dist/entry.js" && exit 1)
+          test -f integrations/pi-agent-plugin/dist/entry.d.ts || (echo "Build output missing: dist/entry.d.ts" && exit 1)
@@ -48,6 +48,7 @@ jobs:
            deepseek-plugin-v*)  workflow="deepseek-plugin-cd.yml" ;;
            n8n-nodes-mem0-v*) workflow="n8n-nodes-mem0-cd.yml" ;;
            mem0-strands-v*)   workflow="mem0-strands-cd.yml" ;;
+            eve-v*)            workflow="eve-cd.yml" ;;
            v*)           workflow="cd.yml" ;;
            *)
              echo "::error::Release tag '$TAG' does not match any known package prefix — nothing will be published. See the tag prefix table in AGENTS.md."
@@ -14,10 +14,6 @@ server/.env
 # Distribution / packaging
 .Python
 build/
-!integrations/agent-plugin-core/build/
-!integrations/agent-plugin-core/build/*.py
-!integrations/agent-plugin-core/build/schemas/
-!integrations/agent-plugin-core/build/schemas/*.json
 develop-eggs/
 dist/
 downloads/
@@ -5,11 +5,11 @@
    {
      "id": "mem0",
      "displayName": "Mem0",
-      "version": "0.3.3",
-      "description": "Cross-session memory and token savings for coding agents.",
+      "version": "0.1.0",
+      "description": "Persistent memory for Kimi Code. Remembers decisions, patterns, and preferences across sessions.",
      "homepage": "https://mem0.ai",
      "keywords": ["memory", "personalization", "mcp", "semantic-search"],
-      "source": "https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin"
+      "source": "https://github.com/mem0ai/mem0/tree/main/integrations/mem0-plugin"
    }
  ]
 }
@@ -14,7 +14,7 @@ This is a polyglot monorepo and **every package sets its own rules**. Read the `
 - Modify anything in `.github/workflows/` without explicit maintainer approval. Publishing credentials are pinned to workflow filenames.
 - Commit `.env` files, API keys, or credentials.
 - Skip pre-commit hooks.
- Use npm or yarn in TypeScript packages. This repo is pnpm-only (Bun in `integrations/opencode-plugin/`).
+- Use npm or yarn in TypeScript packages. This repo is pnpm-only (Bun in `.opencode-plugin/`).
 - Use `require()` in TypeScript. ES module `import` syntax only.
 - Mix up linter configs. Root Python is ruff at line length **120**, `cli/python/` is ruff at **100**, `cli/node/` is Biome, `mem0-ts/` is Prettier, `integrations/vercel-ai-sdk/` is ESLint.
 - Add Python dependencies to the core `dependencies` list in `pyproject.toml`. Use an optional group.
@@ -1,6 +1,6 @@
 {
  "name": "@mem0/cli",
-  "version": "0.2.14",
+  "version": "0.2.13",
  "description": "The official CLI for mem0 — the memory layer for AI agents",
  "type": "module",
  "bin": {
@@ -41,7 +41,7 @@
    "tsup": "^8.0.0",
    "tsx": "^4.7.0",
    "vite": "^6.0.0",
-    "vitest": "^4.1.11",
+    "vitest": "^4.1.0",
    "@biomejs/biome": "^1.7.0",
    "@types/node": "^20.0.0"
  },
@@ -51,8 +51,8 @@ importers:
        specifier: ^6.0.0
        version: 6.4.3(@types/node@20.19.37)(tsx@4.21.0)
      vitest:
-        specifier: ^4.1.11
-        version: 4.1.11(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))
+        specifier: ^4.1.0
+        version: 4.1.8(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))

 packages:

@@ -439,11 +439,11 @@ packages:
  '@types/node@20.19.37':
    resolution: {integrity: sha512-8kzdPJ3FsNsVIurqBs7oodNnCEVbni9yUEkaHbgptDACOPW04jimGagZ51E6+lXUwJjgnBw+hyko/lkFWCldqw==}

-  '@vitest/expect@4.1.11':
-    resolution: {integrity: sha512-VX2x5vNJXET47KAFzwERI+KRMtTTCSWTfSMKsW7JsUsXV4psq++e3DvZpuTDOpHcxytiDs6p2nhVb2tVDiiUYw==}
+  '@vitest/expect@4.1.8':
+    resolution: {integrity: sha512-h3nDO677RDLEGlBxyQ5CW8RlMThSKSRLUePLOx09gNIWRL40edgA1GCZSZgf1W55MFAG6/Sw14KeaAnqv0NKdQ==}

-  '@vitest/mocker@4.1.11':
-    resolution: {integrity: sha512-2XJVD55d1o5AZous5CCGKS74g/riOj9odEt2bQpCVZeblHyHdnMeFl4jl0XjU21stf4mbjUkew2eXQZt65g5CQ==}
+  '@vitest/mocker@4.1.8':
+    resolution: {integrity: sha512-LEiN/xe4OSIbKe9HQIp5OC24agGD9J5CnmMgsLohVVoOPWL9a2sBoR6VBx43jQZb7Kr1l4RCuyCJzcAa0+dojw==}
    peerDependencies:
      msw: ^2.4.9
      vite: ^6.0.0 || ^7.0.0 || ^8.0.0
@@ -453,20 +453,20 @@ packages:
      vite:
        optional: true

-  '@vitest/pretty-format@4.1.11':
-    resolution: {integrity: sha512-yiZzPbGTS9Sr/JpFl8zHrcIkAofNbFV6k21vIgQN/cY/oxZeXhJv5sc/MBJ5jFKWmWs+oJHw0UXLZjmf931+Vw==}
+  '@vitest/pretty-format@4.1.8':
+    resolution: {integrity: sha512-9GasEBxpZ1VYIpqHf/0+YGg121uSNwCKOJqIrTwWP/TB7DmFCiaBpNl3aPZzoLWfWkuqhbH8vJIVobZkvdo2cA==}

-  '@vitest/runner@4.1.11':
-    resolution: {integrity: sha512-LztvUgdwMNJMIkj3hQnnxiC2Xy1zNxq928W/xhjCLaNCzqTZOudjwbQf6v9IntZGPw132i2Lq2rgTRZHD3JHNw==}
+  '@vitest/runner@4.1.8':
+    resolution: {integrity: sha512-EmVxeBAfMJvycdjd6Hm+RbFBbA9fKvo0Kx37hNpBYoYeavH3RNsBXWDooR1mgD52dCrxIIuP7UotpfiwOikvcg==}

-  '@vitest/snapshot@4.1.11':
-    resolution: {integrity: sha512-pN7ikn1ON7h8ee4gIAp4AzyK+zBtJPzVbqOgu5LCEh4VaJVbPQcgYQYJIMGQPXVeJJq1fnfazis7a5pFNPahog==}
+  '@vitest/snapshot@4.1.8':
+    resolution: {integrity: sha512-acfZboRmAIf05DEKcBQy33VXojFJjtUdLyo7oOmV9kebb2xdU01UknNiPuPZoJZQyO7DF0gZdTGTpeAzET9QPQ==}

-  '@vitest/spy@4.1.11':
-    resolution: {integrity: sha512-apNa/prQy2qCeywhnixOHPRCgGNhvg7T4Dapfl1GahLp/R+uhBm5cPyFoNVyqsNd2h1nJxL6BqqdIjiABL60YA==}
+  '@vitest/spy@4.1.8':
+    resolution: {integrity: sha512-6EevtBp6OZOPF7bmz36HrGMeP3txgVSrgebWxHOafDXGkhIzfXK14f8KF6MuFfgXXUeHxmpD3BQxkV00/3s5mA==}

-  '@vitest/utils@4.1.11':
-    resolution: {integrity: sha512-zTCVGpyFsGWBhllOyKlTw/vnr6D9qxsfSDyfbyZmTyjHw5N/VuvzHpHoQjm2ZJzn4RJgx5w4r7V0er69CmLgPQ==}
+  '@vitest/utils@4.1.8':
+    resolution: {integrity: sha512-uOJamYALNhfJ6iolExyQM40yIQwDqYnkKtQ5VCiSe17E33H0aQ/u+1GlRuz4LZBk6Mm3sg90G9hEbmEt37C1Zg==}

  acorn@8.16.0:
    resolution: {integrity: sha512-UVJyE9MttOsBQIDKw1skb9nAwQuR5wuGD3+82K6JgJlm/Y+KI92oNsMNGZCYdDsVtRHSak0pcV5Dno5+4jh9sw==}
@@ -910,20 +910,20 @@ packages:
      yaml:
        optional: true

-  vitest@4.1.11:
-    resolution: {integrity: sha512-fhACrNXUidIbGSBr5FlbuBkO7VWC1ZyLl0DO4CU2DrQoAPxX84Ysxs+HeGQpii5lZWV1Q4gBZTTu49mF+A6Edw==}
+  vitest@4.1.8:
+    resolution: {integrity: sha512-flY6ScbCIt9HThs+C5HS7jvGOB560DJtk/Z15IQROTA6zEy49Nh8T/dofWTQL+n3vswqn87sbJNiuqw1SDp5Ig==}
    engines: {node: ^20.0.0 || ^22.0.0 || >=24.0.0}
    hasBin: true
    peerDependencies:
      '@edge-runtime/vm': '*'
      '@opentelemetry/api': ^1.9.0
      '@types/node': ^20.0.0 || ^22.0.0 || >=24.0.0
-      '@vitest/browser-playwright': 4.1.11
-      '@vitest/browser-preview': 4.1.11
-      '@vitest/browser-webdriverio': 4.1.11
-      '@vitest/coverage-istanbul': 4.1.11
-      '@vitest/coverage-v8': 4.1.11
-      '@vitest/ui': 4.1.11
+      '@vitest/browser-playwright': 4.1.8
+      '@vitest/browser-preview': 4.1.8
+      '@vitest/browser-webdriverio': 4.1.8
+      '@vitest/coverage-istanbul': 4.1.8
+      '@vitest/coverage-v8': 4.1.8
+      '@vitest/ui': 4.1.8
      happy-dom: '*'
      jsdom: '*'
      vite: ^6.0.0 || ^7.0.0 || ^8.0.0
@@ -1186,44 +1186,44 @@ snapshots:
    dependencies:
      undici-types: 6.21.0

-  '@vitest/expect@4.1.11':
+  '@vitest/expect@4.1.8':
    dependencies:
      '@standard-schema/spec': 1.1.0
      '@types/chai': 5.2.3
-      '@vitest/spy': 4.1.11
-      '@vitest/utils': 4.1.11
+      '@vitest/spy': 4.1.8
+      '@vitest/utils': 4.1.8
      chai: 6.2.2
      tinyrainbow: 3.1.0

-  '@vitest/mocker@4.1.11(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))':
+  '@vitest/mocker@4.1.8(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))':
    dependencies:
-      '@vitest/spy': 4.1.11
+      '@vitest/spy': 4.1.8
      estree-walker: 3.0.3
      magic-string: 0.30.21
    optionalDependencies:
      vite: 6.4.3(@types/node@20.19.37)(tsx@4.21.0)

-  '@vitest/pretty-format@4.1.11':
+  '@vitest/pretty-format@4.1.8':
    dependencies:
      tinyrainbow: 3.1.0

-  '@vitest/runner@4.1.11':
+  '@vitest/runner@4.1.8':
    dependencies:
-      '@vitest/utils': 4.1.11
+      '@vitest/utils': 4.1.8
      pathe: 2.0.3

-  '@vitest/snapshot@4.1.11':
+  '@vitest/snapshot@4.1.8':
    dependencies:
-      '@vitest/pretty-format': 4.1.11
-      '@vitest/utils': 4.1.11
+      '@vitest/pretty-format': 4.1.8
+      '@vitest/utils': 4.1.8
      magic-string: 0.30.21
      pathe: 2.0.3

-  '@vitest/spy@4.1.11': {}
+  '@vitest/spy@4.1.8': {}

-  '@vitest/utils@4.1.11':
+  '@vitest/utils@4.1.8':
    dependencies:
-      '@vitest/pretty-format': 4.1.11
+      '@vitest/pretty-format': 4.1.8
      convert-source-map: 2.0.0
      tinyrainbow: 3.1.0

@@ -1627,15 +1627,15 @@ snapshots:
      fsevents: 2.3.3
      tsx: 4.21.0

-  vitest@4.1.11(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0)):
+  vitest@4.1.8(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0)):
    dependencies:
-      '@vitest/expect': 4.1.11
-      '@vitest/mocker': 4.1.11(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))
-      '@vitest/pretty-format': 4.1.11
-      '@vitest/runner': 4.1.11
-      '@vitest/snapshot': 4.1.11
-      '@vitest/spy': 4.1.11
-      '@vitest/utils': 4.1.11
+      '@vitest/expect': 4.1.8
+      '@vitest/mocker': 4.1.8(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))
+      '@vitest/pretty-format': 4.1.8
+      '@vitest/runner': 4.1.8
+      '@vitest/snapshot': 4.1.8
+      '@vitest/spy': 4.1.8
+      '@vitest/utils': 4.1.8
      es-module-lexer: 2.1.0
      expect-type: 1.3.0
      magic-string: 0.30.21
@@ -31,8 +31,7 @@ export class PlatformBackend implements Backend {
 		this.headers = {
 			Authorization: `Token ${config.apiKey}`,
 			"Content-Type": "application/json",
-			"X-Mem0-Source": "CLI",
-			"X-Mem0-Client": `mem0-cli-node/${CLI_VERSION}`,
+			"X-Mem0-Source": "cli",
 			"X-Mem0-Client-Language": "node",
 			"X-Mem0-Client-Version": CLI_VERSION,
 		};
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"

 [project]
 name = "mem0-cli"
-version = "0.2.13"
+version = "0.2.12"
 description = "The official CLI for mem0 — the memory layer for AI agents"
 readme = "README.md"
 license = "Apache-2.0"
@@ -1,3 +1,3 @@
 """mem0 CLI — the command-line interface for the mem0 memory layer."""

-__version__ = "0.2.13"
+__version__ = "0.2.12"
@@ -27,8 +27,7 @@ class PlatformBackend(Backend):
            headers={
                "Authorization": f"Token {config.api_key}",
                "Content-Type": "application/json",
-                "X-Mem0-Source": "CLI",
-                "X-Mem0-Client": f"mem0-cli-python/{__version__}",
+                "X-Mem0-Source": "cli",
                "X-Mem0-Client-Language": "python",
                "X-Mem0-Client-Version": __version__,
            },
@@ -1,6 +1,7 @@
 ---
-title: "API Reference Overview"
-sidebarTitle: "Overview"
+title: "Overview"
+seo:
+  title: "API Reference Overview - Mem0"
 icon: "terminal"
 iconType: "solid"
 description: "REST APIs for memory management, search, and entity operations"
@@ -1,6 +1,7 @@
 ---
-title: "Delete Memory API Endpoint"
-sidebarTitle: "Delete Memory"
+title: 'Delete Memory'
+seo:
+  title: "Delete Memory API Endpoint - Mem0"
 description: "Delete a single memory by its unique memory ID from the Mem0 platform using the DELETE endpoint."
 openapi: delete /v1/memories/{memory_id}/
 ---
@@ -1,6 +1,7 @@
 ---
-title: "Update Memory API Endpoint"
-sidebarTitle: "Update Memory"
+title: 'Update Memory'
+seo:
+  title: "Update Memory API Endpoint - Mem0"
 description: "Update the content, metadata, timestamp, or expiration date of a single memory by its unique ID using the PUT endpoint."
 openapi: put /v1/memories/{memory_id}/
 ---
@@ -1,6 +1,7 @@
 ---
-title: "Add Organization Member API Endpoint"
-sidebarTitle: "Add Member"
+title: 'Add Member'
+seo:
+  title: "Add Organization Member API Endpoint - Mem0"
 description: "Add a new member to an organization with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/members/
 ---
@@ -1,6 +1,7 @@
 ---
-title: "Get Organization Members API Endpoint"
-sidebarTitle: "Get Members"
+title: 'Get Members'
+seo:
+  title: "Get Organization Members API Endpoint - Mem0"
 description: "Retrieve a list of all members belonging to a specific organization on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/members/
 ---
@@ -1,5 +0,0 @@
---
-title: 'Generate Profiles'
-description: "Start one generation: sample a few entities, or build one for a single entity."
-openapi: post /v2/profiles/jobs/
---
@@ -1,5 +0,0 @@
---
-title: 'Get Generation Job'
-description: "Read the progress of a generation, and whether it finished."
-openapi: get /v2/profiles/jobs/{job_id}/
---
@@ -1,5 +0,0 @@
---
-title: 'Get Profile Settings'
-description: "Retrieve the profile schema, custom instructions, and enabled flag for the current project."
-openapi: get /v2/profiles/settings/
---
@@ -1,5 +0,0 @@
---
-title: 'Get Profile'
-description: "Retrieve the structured profile for a user, with a status describing whether generation has completed."
-openapi: get /v2/entities/{entity_type}/{entity_id}/profile/
---
@@ -1,5 +0,0 @@
---
-title: 'Update Profile Settings'
-description: "Set the JSON Schema, custom instructions, or enabled flag that control profile generation for the project."
-openapi: post /v2/profiles/settings/
---
@@ -1,6 +1,7 @@
 ---
-title: "Add Project Member API Endpoint"
-sidebarTitle: "Add Member"
+title: 'Add Member'
+seo:
+  title: "Add Project Member API Endpoint - Mem0"
 description: "Add a new member to a project with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---
@@ -1,6 +1,7 @@
 ---
-title: "Get Project Members API Endpoint"
-sidebarTitle: "Get Members"
+title: 'Get Members'
+seo:
+  title: "Get Project Members API Endpoint - Mem0"
 description: "Retrieve a list of all members belonging to a specific project on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---
@@ -7,36 +7,6 @@ mode: "wide"
 <Tabs>
 <Tab title="Python">

-<Update label="2026-09-25" description="v2.2.1">
-
-**Bug Fixes:**
- **Core:** `add()` (`Memory` and `AsyncMemory`) no longer reports records the vector store rejected as successful `ADD` events. Only records that were actually inserted are written to history, entity-linked, and returned. If none of the extracted memories could be inserted, `add()` now raises `VectorStoreError` instead of returning memories that were never stored ([#7066](https://github.com/mem0ai/mem0/pull/7066))
- **Core:** Restore the context-manager protocol on `Memory` (`with Memory() as m:`) and `AsyncMemory` (`async with AsyncMemory() as m:`), which closes the instance on exit ([#7354](https://github.com/mem0ai/mem0/pull/7354))
- **LLMs:** The AWS Bedrock Anthropic path now returns the first Converse content block that carries text instead of always reading `content[0]`. Claude reasoning models can emit a `reasoningContent` block before the text block, which previously made the call fail with a `KeyError` ([#6369](https://github.com/mem0ai/mem0/pull/6369))
- **Vector Stores:** Turbopuffer filters now apply every operator (`eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`). Only `gte` and `lte` were read before, so any other operator was silently dropped and the query returned unfiltered results. An unsupported operator now raises `ValueError` ([#6564](https://github.com/mem0ai/mem0/pull/6564))
- **Vector Stores:** Turbopuffer `search()` scores now respect `distance_metric`. With `euclidean_squared`, the unbounded squared distance maps to `1 / (1 + distance)` instead of `1 - distance`, which went negative and inverted ranking for any distance above 1 ([#6559](https://github.com/mem0ai/mem0/pull/6559))
- **Vector Stores:** S3 Vectors `search()` scores are now metric-aware. With `euclidean`, the distance maps to `1 / (1 + distance)` instead of `max(0, 1 - distance)`, which collapsed most scores to 0 ([#6547](https://github.com/mem0ai/mem0/pull/6547))
-
-</Update>
-
-<Update label="2026-09-23" description="v2.2.0">
-
-**New Features:**
- **Client:** Add User Profiles to `MemoryClient` and `AsyncMemoryClient`: `get_profile()`, `generate_profile()`, `get_profile_settings()`, `update_profile_settings()`, `sample_profiles()`, and `get_profile_job()`. A profile is a structured, always-current JSON summary of one user, shaped by a JSON Schema you configure per project and filled by an LLM from that user's memories. Generation is asynchronous. Every job POST carries an `Idempotency-Key`; to retry a lost request without starting a second job, pass the same `idempotency_key` on each attempt ([#7340](https://github.com/mem0ai/mem0/pull/7340))
-
-**Bug Fixes:**
- **Vector Stores:** Guard against `None` timestamps in the Valkey vector store's `insert()` and `update()` paths. `created_at` and `updated_at` fields that were present in the payload but set to `None` previously passed the `"created_at" not in payload` / `"updated_at" in payload` checks and raised `TypeError` when `datetime.fromisoformat()` received `None`. Both paths now use `.get()` with a truthiness check so `None` values fall through to the default, matching the Redis provider's behavior ([#6993](https://github.com/mem0ai/mem0/pull/6993))
-
-</Update>
-
-<Update label="2026-09-18" description="v2.1.0">
-
-**Improvements:**
- **Client:** Requests now carry three surface-identity headers so the platform can tell which product made a call. `X-Mem0-Source` names the surface and `X-Application` the host app it runs inside, both set-once so a wrapper that already declared its identity keeps it. `X-Mem0-Client` is append-only and carries `name/version` per layer, outermost first, so a plugin calling this SDK reports the whole chain rather than only the last speaker. `MEM0_SOURCE`, `MEM0_APPLICATION` and `MEM0_CLIENT_STACK` set them from the environment for wrappers that cannot pass options ([#7326](https://github.com/mem0ai/mem0/pull/7326))
- **Client:** The client stack is bounded by dropping whole entries rather than slicing characters, and this SDK's own entry is the reserved one. Truncating the joined string could sever an identifier mid-name and the platform parsed the fragment as a real client ([#7326](https://github.com/mem0ai/mem0/pull/7326))
-
-</Update>
-
 <Update label="2026-09-02" description="v2.0.20">

 **Improvements:**
@@ -204,7 +174,7 @@ mode: "wide"
 <Update label="2026-06-24" description="v2.0.8">

 **New Features:**
- **Embeddings:** Add native `embed_batch` to five embedders for batched embedding requests: LM Studio, Together, HuggingFace, Vertex AI, and Google GenAI ([#5609](https://github.com/mem0ai/mem0/pull/5609))
+- **Embeddings:** Add native `embed_batch` to five embedders: LM Studio, Together, HuggingFace, Vertex AI, and Google GenAI: for batched embedding requests ([#5609](https://github.com/mem0ai/mem0/pull/5609))

 **Bug Fixes:**
 - **Core:** Guard against malformed `image_url` entries in `parse_vision_messages` to prevent crashes ([#5631](https://github.com/mem0ai/mem0/pull/5631))
@@ -994,7 +964,7 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-
 **New Features:**
 - **OpenMemory:** Added OpenMemory support
 - **Neo4j:** Added weights to Neo4j model
- **AWS:** Added support for OpenSearch Serverless
+- **AWS:** Added support for Opsearch Serverless
 - **Examples:** Added ElizaOS Example

 **Improvements:**
@@ -1257,31 +1227,6 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-

 <Tab title="TypeScript">

-<Update label="2026-09-25" description="v3.3.1">
-
-**Bug Fixes:**
- **Config (OSS):** `ConfigManager` no longer injects OpenAI's default `baseURL` and `model` into non-OpenAI LLM providers. The defaults now apply only to `openai` and `openai_structured`, so a DeepSeek, xAI, or other provider config without an explicit `baseURL` or `model` falls back to that provider's own defaults and env vars (`DEEPSEEK_API_BASE`, `XAI_API_BASE`, ...) instead of pointing at OpenAI with an OpenAI model name ([#7350](https://github.com/mem0ai/mem0/pull/7350))
- **Vector Stores:** Turbopuffer filters now apply every operator (`eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`). Only the range operators were read before, so `eq`, `ne`, `in`, and `nin` were silently dropped. A `"*"` value now matches anything instead of nothing, an array value is treated as `in`, and an unsupported operator throws ([#6578](https://github.com/mem0ai/mem0/pull/6578))
- **Vector Stores:** Turbopuffer `search()` with `euclidean_squared` now maps the unbounded squared distance to `1 / (1 + distance)` instead of `1 - distance`, which went negative and inverted ranking for any distance above 1 ([#6580](https://github.com/mem0ai/mem0/pull/6580))
- **Packaging:** `pg`, `@types/pg`, and `natural` are now optional peer dependencies, and `pg` / `@types/pg` accept caret ranges instead of the exact `8.11.3` / `8.11.0` pins, so installing `mem0ai` no longer pulls in `pg` or conflicts with an app's own `pg` version. The PGVector store now imports `pg` only when it is used, so install it alongside `mem0ai` (`npm install pg`) if you use that store. `@types/jest` moved from peer dependencies to dev dependencies ([#7450](https://github.com/mem0ai/mem0/pull/7450))
-
-</Update>
-
-<Update label="2026-09-23" description="v3.3.0">
-
-**New Features:**
- **Client:** Add User Profiles to `MemoryClient`: `getProfile()`, `generateProfile()`, `getProfileSettings()`, `updateProfileSettings()`, `sampleProfiles()`, and `getProfileJob()`. A profile is a structured, always-current JSON summary of one user, shaped by a JSON Schema you configure per project and filled by an LLM from that user's memories. Generation is asynchronous. Every job POST carries an `Idempotency-Key`; to retry a lost request without starting a second job, pass the same `idempotencyKey` on each attempt ([#7340](https://github.com/mem0ai/mem0/pull/7340))
-
-</Update>
-
-<Update label="2026-09-18" description="v3.2.0">
-
-**Improvements:**
- **Client:** Requests now carry `X-Mem0-Source`, `X-Application` and `X-Mem0-Client`, matching the Python SDK. The first two are set-once so an outer wrapper keeps its identity; the third is append-only and reports the whole layer chain. Read from `MEM0_SOURCE`, `MEM0_APPLICATION` and `MEM0_CLIENT_STACK` when set ([#7326](https://github.com/mem0ai/mem0/pull/7326))
- **Client:** The SDK version in `X-Mem0-Client` is injected at build time rather than hardcoded, so it cannot go stale at the next release ([#7326](https://github.com/mem0ai/mem0/pull/7326))
-
-</Update>
-
 <Update label="2026-09-02" description="v3.1.8">

 **Improvements:**
@@ -1919,13 +1864,6 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-

 <Tab title="CLI">

-<Update label="2026-09-18" description="Python v0.2.13 / Node v0.2.14">
-
-**Improvements:**
- **Client:** Requests now carry the three surface-identity headers (`X-Mem0-Source`, `X-Application`, `X-Mem0-Client`) introduced in the Python and TypeScript SDKs, so the platform can attribute calls made through the CLI to the correct surface and version ([#7326](https://github.com/mem0ai/mem0/pull/7326))
-
-</Update>
-
 <Update label="2026-08-24" description="Python v0.2.12 / Node v0.2.13">

 **New Features:**
@@ -2122,29 +2060,6 @@ A full-featured command-line interface for Mem0, available in both Python and No
 <Tabs>
 <Tab title="Mem0 Plugin">

-<Update label="2026-09-08" description="Shared agent plugin runtime">
-
-**Changed:**
- Consolidated the coding-agent integrations into `integrations/agent-plugin-core/`: one Python runtime, one TypeScript utility library, and six canonical Python-plugin skill templates. Native adapters retain each host's event contracts and capabilities.
- Python plugins ship generated, self-contained `core/` and `skills/` directories. Builds validate portable schemas and skills, parse native JSON, and reject generated-file drift, missing files, stale generated files, and symlinks. TypeScript packages bundle the shared source into their distributable JavaScript and verify their entry points.
- Replaced the old `integrations/mem0-plugin/` layout with native host directories and one portable `integrations/mem0-agent-plugin/` package. Updated marketplace paths, installation guides, and integration-skill links. OpenCode now lives in `integrations/opencode-plugin/`.
- Native Python plugins expose one local, read-only `search_memories` MCP tool and six skills: search, remember, forget, status, pause, and resume. The shared search tool accepts optional `run_id` with every scope (`repo`, `dir`, and `mine`) to recall memories from a specific coding-agent session. Omitting it searches across sessions. This local tool is separate from the hosted Mem0 MCP server's tool set.
-
-**Fixes:**
- Hooks, controls, MCP servers, and detached workers use the same host-specific data directory. Detached workers retain the host identity and telemetry source; `--plugin-data-dir` reaches the shared resolver.
- Session-end workers flush the conversation already captured by hooks. Repeated and concurrent response hooks no longer duplicate an answer, while identical answers after separate prompts are preserved.
- Shared prompts and responses are redacted without the previous 6,000-character cutoff. Python extraction splits oversized messages without dropping text to enforce each request's input budget. Flush event selection and claims share one write transaction, delayed handoffs are replaced atomically, and permanent HTTP polling errors fail promptly.
- Extraction instructions refer to the current coding agent. Python redaction covers JSON-shaped credentials; both telemetry runtimes recursively remove sensitive keys, including keys inside nested lists.
- New Git repository writes use a hash of the remote identity in `agent_id`. Search and explicit shared-memory deletion include both current and legacy repository IDs within the repository's `app_id`. Existing memories are not rewritten. Legacy IDs retain their original ambiguity for matching owner/repository names on different Git hosts.
-
-**Packaging:**
- Claude Code, Cursor, Codex, Kimi, Antigravity, and the portable Python bundle are versioned at `0.3.1`. OpenCode and DeepSeek Harness are `0.3.0`; Pi Agent is `0.3.0`; OpenClaw is `1.1.0`. Each host's changes and upgrade considerations are listed in its tab.
- Python and TypeScript CI run their respective runtime suites. Package checks build the installable artifacts, check generated-file consistency, and reject TypeScript output that still imports monorepo source.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-24" description="mem0-plugin v0.2.15">

 **Fixes:**
@@ -2431,163 +2346,8 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex

 </Tab>

-<Tab title="Claude Code">
-
-<Update label="2026-09-23" description="Claude Code plugin v0.3.3">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer tells the agent to call it before answering anything that could depend on prior context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, which reduces unnecessary searches ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Sidekick:** Sidekick searches memories when earlier sessions could help, instead of before every answer ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Extraction:** Repository memory instructions are shorter. They no longer ask for a dedicated memory for each command that failed and was then fixed, and no longer carry separate rules against saving personal preferences or memories that only name the repository, branch, or directory ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Search skill:** `/search` no longer describes categories as best-effort labels or asks for a retry without the category ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.3`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with these prompts ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Claude Code plugin v0.3.2">
-
-**Improvements:**
- **Telemetry:** `PLUGIN_VERSION` bumped to `0.3.2`. The `mem0-plugin/<version>` wire header and `plugin_version` telemetry field now reflect the fixes from #7322 through #7358 ([#7373](https://github.com/mem0ai/mem0/pull/7373))
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-**Changes:**
- **Sidekick:** Sidekick is now available only in Claude Code, with Sonnet, worktree isolation, and parent memories.
-
-</Update>
-
-<Update label="2026-09-08" description="Claude Code plugin v0.3.1">
-
-**Changed:**
- Extracted hook orchestration and memory behavior into the shared Python core; Claude transcript parsing remains in its native adapter. The installed package contains the generated runtime rather than importing files outside its plugin directory.
- Preserves the public `mem0` name, hook declarations, MCP launch configuration, user configuration, and `mem0:sidekick` worktree behavior. The manifest and marketplace version advance from `0.3.0` to `0.3.1` so installations can identify the update.
-
-**Fixes:**
- Session-end extraction no longer appends a final answer already captured from the transcript while an earlier extraction was running.
- Existing repository memories remain searchable after the shared-ID change; explicit shared-memory deletion also covers the legacy ID. Background workers and control skills consistently use Claude's data directory.
- Receives the shared JSON-secret redaction and nested telemetry filtering fixes. The local search tool exposes query, result count, category, scope, and optional `run_id` for session-specific recall across all scopes.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
-</Tab>
-
-<Tab title="Cursor">
-
-<Update label="2026-09-23" description="Cursor plugin v0.3.3">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer tells the agent to call it before answering anything that could depend on prior context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, which reduces unnecessary searches ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Extraction:** Repository memory instructions are shorter. They no longer ask for a dedicated memory for each command that failed and was then fixed, and no longer carry separate rules against saving personal preferences or memories that only name the repository, branch, or directory ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Search skill:** `/search` no longer describes categories as best-effort labels or asks for a retry without the category ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.3`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with these prompts ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Cursor plugin v0.3.2">
-
-**Improvements:**
- **Telemetry:** `PLUGIN_VERSION` bumped to `0.3.2`. The `mem0-plugin/<version>` wire header and `plugin_version` telemetry field now reflect the fixes from #7322 through #7358 ([#7373](https://github.com/mem0ai/mem0/pull/7373))
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-**Changes:**
- **Sidekick:** Removes Sidekick and its start/stop hooks. Memory capture, search, and six skills remain available.
-
-</Update>
-
-<Update label="2026-09-08" description="Cursor plugin v0.3.1">
-
-**Changed:**
- Moves from the legacy shared editor-plugin directory to a native `integrations/cursor-plugin/` package with generated Python core and skills, Cursor variables, local MCP configuration, and a native Sidekick.
- Translates Cursor conversation/workspace fields, response and summary fields, tool outcomes, and subagent lifecycle events into the shared runtime. The Sidekick searches memory itself because Cursor's subagent-start response cannot inject parent context.
-
-**Fixes:**
- Adapter errors are logged and exit successfully so a memory failure does not terminate the host hook. Sidekick telemetry reports zero parent-injected context because this host uses self-search.
- Repeated response events and Stop/session-end capture do not duplicate the same answer.
- Receives shared data-directory handling, background-worker identity, redaction, and legacy-memory retrieval fixes.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
-</Tab>
-
-<Tab title="Codex">
-
-<Update label="2026-09-23" description="Codex plugin v0.3.3">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer tells the agent to call it before answering anything that could depend on prior context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, which reduces unnecessary searches ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Extraction:** Repository memory instructions are shorter. They no longer ask for a dedicated memory for each command that failed and was then fixed, and no longer carry separate rules against saving personal preferences or memories that only name the repository, branch, or directory ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Search skill:** `/search` no longer describes categories as best-effort labels or asks for a retry without the category ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.3`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with these prompts ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Codex plugin v0.3.2">
-
-**Improvements:**
- **Telemetry:** `PLUGIN_VERSION` bumped to `0.3.2`. The `mem0-plugin/<version>` wire header and `plugin_version` telemetry field now reflect the fixes from #7322 through #7358 ([#7373](https://github.com/mem0ai/mem0/pull/7373))
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-**Changes:**
- **Sidekick:** Renames shared tracking to use subagent terminology. Native subagent memory support remains available.
-
-</Update>
-
-<Update label="2026-09-08" description="Codex plugin v0.3.1">
-
-**Changed:**
- Moves from the legacy shared editor-plugin directory to a native `integrations/codex-plugin/` package, with generated Python core and six skills, a local search MCP server, and native lifecycle hooks.
- Resolves MCP repository searches from Codex workspace metadata when supplied. Control skills, hooks, and workers use the same plugin data directory.
- Native subagent start/stop hooks supply parent-retrieved memory context and record completions for every native subagent. Named custom agents remain project/user configuration; the plugin does not distribute a named Codex Sidekick.
-
-**Fixes:**
- Receives shared credential redaction, legacy-memory retrieval, background-worker identity, and duplicate-response fixes. Codex tool outcomes use available structured failure indicators; missing outcome information is recorded as unknown.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
-</Tab>
-
 <Tab title="OpenCode">

-<Update label="2026-09-23" description="OpenCode plugin v0.4.1">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer asks the agent to search proactively or to run several searches for multi-part questions. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, the same wording as the other coding-agent plugins ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Session context:** Removed two system-context lines that told the agent to run 2 parallel searches before responding and 2-4 parallel searches for non-trivial tasks ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Skills:** `/mem0-search` and `/mem0-context-loader` make one `search_memories` call instead of 2 and 2-4 parallel calls. `/mem0-context-loader` now uses the search skill description from the other coding-agent plugins instead of asking to load at every new task or context switch ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="OpenCode plugin v0.4.0">
-
-**Changes:**
- **Telemetry:** The PostHog `source` tag changed from the literal `"plugin"` to `OPENCODE_PLUGIN`, and `project_hash` is now salted. Saved PostHog insights filtering on `source = "plugin"` will stop matching new events; historical data is unaffected ([#7322](https://github.com/mem0ai/mem0/pull/7322))
- **Config:** A new `keyFingerprint` key appears in the install-count deduplication logic; installs are now counted once per key rather than on every activation ([#7325](https://github.com/mem0ai/mem0/pull/7325))
-
-</Update>
-
-<Update label="2026-09-08" description="OpenCode plugin v0.3.0">
-
-**Changed:**
- Moved the source from `integrations/mem0-plugin/.opencode-plugin/` to `integrations/opencode-plugin/`, retaining the `@mem0/opencode-plugin` package name and native OpenCode hooks.
- Reuses shared conversation preparation, redaction, scoping, and telemetry. Builds a self-contained Bun/ESM `dist/index.js` and publishes its TypeScript entry declaration.
- Global memory tool scope requires the user to enable it in plugin settings first; empty and wildcard identities are rejected.
- Retains the seven commands for context loading, search, remember, forget, scope, status, and tour; bundled skills continue loading through OpenCode's native configuration.
-
-**Removed:**
- Removed auto-Dream consolidation, its gates and state handling, and the Dream and pin skills/commands. Existing configurations and workflows that use these features must be updated.
-
-**Builds:**
- Updated build and publish paths for the relocated source directory; the existing release tag prefix and publishing workflow filename are unchanged.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-07-22" description="OpenCode plugin v0.2.2">

 **Fixes:**
@@ -2668,43 +2428,6 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex

 <Tab title="Antigravity">

-<Update label="2026-09-23" description="Antigravity plugin v0.3.3">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer tells the agent to call it before answering anything that could depend on prior context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, which reduces unnecessary searches ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Extraction:** Repository memory instructions are shorter. They no longer ask for a dedicated memory for each command that failed and was then fixed, and no longer carry separate rules against saving personal preferences or memories that only name the repository, branch, or directory ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Search skill:** `/search` no longer describes categories as best-effort labels or asks for a retry without the category ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.3`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with these prompts ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Antigravity plugin v0.3.2">
-
-**Improvements:**
- **Telemetry:** `PLUGIN_VERSION` bumped to `0.3.2`. The `mem0-plugin/<version>` wire header and `plugin_version` telemetry field now reflect the fixes from #7322 through #7358 ([#7373](https://github.com/mem0ai/mem0/pull/7373))
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-**Changes:**
- **Sidekick:** Removes Sidekick. Memory capture, search, and six skills remain available.
-
-</Update>
-
-<Update label="2026-09-08" description="Antigravity plugin v0.3.1">
-
-**Changed:**
- Ships a native package with generated Python core and six skills, a local search MCP server, a Sidekick declaration, and an adapter for `PreInvocation`, `PostToolUse`, and `Stop`.
- Normalizes conversation IDs, transcript paths, workspace paths, tool calls, and errors. The adapter captures all completed user/assistant transcript messages incrementally, including later-turn intent, without replaying earlier messages.
- Sidekick searches Mem0 itself; this plugin does not provide Claude Code's worktree isolation.
-
-**Fixes and host limitations:**
- Accepts `MEM0_CWD` as an explicit workspace fallback when the host omits `workspacePaths`. Skips capture when neither is available, rather than writing under an unrelated directory.
- Documents global MCP registration with `agy mcp add` when the host does not register the plugin-scoped server. Recall on the initial invocation depends on the host providing a prompt or readable transcript.
- Receives the shared data-directory, redaction, legacy-memory retrieval, and duplicate-response fixes.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-24" description="Antigravity plugin v0.1.7">

 **Fixes:**
@@ -2781,45 +2504,6 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="Kimi">

-<Update label="2026-09-23" description="Kimi Code plugin v0.3.3">
-
-**Improvements:**
- **Search:** The `search_memories` tool description no longer tells the agent to call it before answering anything that could depend on prior context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help, which reduces unnecessary searches ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Extraction:** Repository memory instructions are shorter. They no longer ask for a dedicated memory for each command that failed and was then fixed, and no longer carry separate rules against saving personal preferences or memories that only name the repository, branch, or directory ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Search skill:** `/search` no longer describes categories as best-effort labels or asks for a retry without the category ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.3`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with these prompts ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Kimi Code plugin v0.3.2">
-
-**Improvements:**
- **Telemetry:** `PLUGIN_VERSION` bumped to `0.3.2`. The `mem0-plugin/<version>` wire header and `plugin_version` telemetry field now reflect the fixes from #7322 through #7358 ([#7373](https://github.com/mem0ai/mem0/pull/7373))
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-**Changes:**
- **Sidekick:** Removes Sidekick and its start/stop hooks. Memory capture, recall, and six skills remain available.
-
-</Update>
-
-<Update label="2026-09-08" description="Kimi Code plugin v0.3.1">
-
-**Changed:**
- Ships a self-contained native package with six skills, nine lifecycle hooks, a local search MCP server, and a native Sidekick declaration. Added a dedicated installation and troubleshooting guide.
- Translates Kimi's session, prompt, tool, compaction, shutdown, and subagent events into the shared Python runtime. Sidekicks receive parent memory context through Kimi's native lifecycle.
-
-**Fixes:**
- Recovers completed assistant output from Kimi's indexed v2 wire transcript when Stop events omit the response text. Repeated Sidekick invocations receive distinct run identifiers. Stops without a host ID are left uncorrelated when multiple matching runs are active, preserving their responses without assigning them to the wrong run.
- Keeps controls, hooks, MCP, and detached workers on the same Kimi data directory and preserves host identity in background workers.
- Receives the shared redaction, legacy-memory retrieval, and duplicate-response fixes.
-
-**Host compatibility:**
- Documents `CHOKIDAR_USEPOLLING=1` for the observed macOS watcher issue. Filesystem isolation remains Kimi's responsibility.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-24" description="kimi-plugin v0.1.0">

 **Initial release** of the Mem0 plugin for Kimi Code, sharing its scripts, skills, and marketplace listing with the Claude Code / Cursor / Codex / Antigravity plugin family ([#6919](https://github.com/mem0ai/mem0/pull/6919))
@@ -2836,39 +2520,6 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="OpenClaw">

-<Update label="2026-09-23" description="openclaw-mem0 v1.2.1">
-
-**Improvements:**
- **Search:** The `memory_search` tool description no longer asks the agent to search proactively or to run several searches for multi-part questions. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help. Recall strategies (`smart`, `always`, `manual`) are unchanged ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="openclaw-mem0 v1.2.0">
-
-**Changes:**
- **Config:** Added `keyFingerprint` to the config schema for install-count deduplication; installs are now counted once per key rather than on every activation ([#7325](https://github.com/mem0ai/mem0/pull/7325))
- **Telemetry:** Events are no longer delivered twice, and the `plugin_version` field now reflects the plugin that produced the event ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-</Update>
-
-<Update label="2026-09-08" description="openclaw-mem0 v1.1.0">
-
-**Changed:**
- Reuses shared conversation preparation, redaction, and telemetry while retaining OpenClaw's native memory backend, tools, CLI, and Platform/OSS modes.
- Continues to publish a self-contained ESM package under `@mem0/openclaw-mem0`; the plugin manifest and package version now agree.
-
-**Removed:**
- Removed Dream consolidation: automatic scheduling and locking, `openclaw mem0 dream`, Dream configuration, the memory-dream skill, and Dream-state public artifacts. Triage, recall, and memory/entity artifacts remain available. Update configurations or integrations that use the removed Dream surface.
-
-**Fixes:**
- `openclaw mem0 status` handles an unconfigured installation without crashing and directs users to setup.
- Removed OpenClaw's separate 2,000-character extraction cutoff. Selected user and assistant messages retain their full redacted text; recent-message selection, earlier summary selection, and noise filtering still apply.
- Telemetry removes sensitive properties recursively and uses the shared failure-safe delivery implementation.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-24" description="openclaw-mem0 v1.0.16">

 **Security:**
@@ -3139,40 +2790,6 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="Pi Agent">

-<Update label="2026-09-23" description="Pi Agent plugin v0.3.2">
-
-**Improvements:**
- **Search:** The memory policy, `mem0_memory` tool description, and prompt guidelines no longer ask the agent to search before answering anything that may depend on earlier context or to run several searches per question. They now ask for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Skills:** `context-loader` makes one search instead of 2-4 parallel searches, and uses the search skill description from the other coding-agent plugins ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Automatic recall:** Injected memories are introduced as "Mem0 found these relevant memories from earlier work in this repository:", the same heading as the Python plugins. The old heading called them a shallow first pass and told the agent to search again ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="Pi Agent plugin v0.3.1">
-
-**Improvements:**
- **Telemetry:** Events are no longer delivered twice, no longer lose parked events, and now attribute each event to the plugin that produced it. The `plugin_version` wire field reflects the fixed release ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-</Update>
-
-<Update label="2026-09-08" description="Pi Agent plugin v0.3.0">
-
-**Changed:**
- Reuses shared conversation preparation, memory formatting, project/session/global scope utilities, and telemetry while preserving Pi's native extension API and `@mem0/pi-agent-plugin` package name.
- Pi loads the built `dist/entry.js` extension instead of executing source TypeScript from an installed package. Builds also publish the library entry point and declarations.
-
-**Removed:**
- Removed Dream consolidation and pin commands, skills, configuration, types, and exports. The remaining commands are remember, search, forget, tour, scope, and status. Update integrations that import removed APIs or invoke removed commands.
-
-**Fixes:**
- Global memory tool scope requires the user to select `/mem0-scope global` or configure a global default first. Empty and wildcard identities are rejected.
- Memory update and delete accept the `mem0:<uuid>` and `[mem0:<uuid>]` citations displayed in tool results, as well as raw IDs.
- Shared capture preparation filters conversation roles and redacts content; telemetry removes sensitive keys inside nested structures.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-24" description="Pi Agent plugin v0.1.5">

 **Security:**
@@ -3268,38 +2885,6 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="DeepSeek Harness">

-<Update label="2026-09-23" description="deepseek-plugin v0.3.2">
-
-**Improvements:**
- **Search:** The `search_memory` tool description no longer asks the agent to search proactively before answering anything that may depend on earlier context. It now asks for a search before repeating investigation or when earlier decisions, fixes, commands, or results may help ([#7420](https://github.com/mem0ai/mem0/pull/7420))
- **Automatic recall:** Injected memories are introduced as "Mem0 found these relevant memories from earlier work:". The old heading called them a shallow first pass and told the agent to search again with `mem0_memory`, a tool DeepSeek does not have ([#7420](https://github.com/mem0ai/mem0/pull/7420))
-
-</Update>
-
-<Update label="2026-09-18" description="deepseek-plugin v0.3.1">
-
-**Improvements:**
- **Telemetry:** Rebuild with the fixed shared telemetry core from `agent-plugin-core`. Events are no longer delivered twice, no longer lose parked events on flush, and now attribute each event to the plugin that produced it ([#7323](https://github.com/mem0ai/mem0/pull/7323), [#7324](https://github.com/mem0ai/mem0/pull/7324), [#7358](https://github.com/mem0ai/mem0/pull/7358))
-
-</Update>
-
-<Update label="2026-09-08" description="deepseek-plugin v0.3.0">
-
-**Added:**
- Automatic recall during `system-prompt/assemble`, using the latest human prompt and avoiding repeated context injection within a session.
- Automatic capture from the durable `session/event` stream after a completed turn. Interrupted or incomplete turns are not sent through this automatic capture path. `autoRecall` and `autoCapture` default to `true` and can be disabled.
-
-**Changed:**
- Reuses shared lifecycle, redaction, identity, and telemetry utilities while retaining the explicit `search_memory` and `add_memory` tools and their per-call agent/session scope. Cross-user `userId` overrides now require operator opt-in with `allowUserOverride: true`.
- Publishes a self-contained ESM artifact under `@mem0/deepseek-plugin`; native Harness services and the Mem0 SDK remain external dependencies. Plugin cleanup remains tied to the native Cordis lifecycle.
-
-**Host compatibility:**
- Supports the declared Harness runtime dependencies and documents the macOS watcher workaround. The plugin does not bundle a named Sidekick or provide child filesystem isolation.
-
-[#7203](https://github.com/mem0ai/mem0/pull/7203)
-
-</Update>
-
 <Update label="2026-08-25" description="deepseek-plugin v0.1.1">

 **New Features:**
@@ -3327,13 +2912,6 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="Vercel AI SDK">

-<Update label="2026-09-18" description="Vercel AI SDK v3.0.3">
-
-**Improvements:**
- **Client:** Inherits the three surface-identity headers (`X-Mem0-Source`, `X-Application`, `X-Mem0-Client`) from the TypeScript SDK bump, so platform calls made through the Vercel AI SDK provider are now correctly attributed ([#7326](https://github.com/mem0ai/mem0/pull/7326))
-
-</Update>
-
 <Update label="2026-08-24" description="Vercel AI SDK v3.0.2">

 **Security:**
@@ -1,6 +1,7 @@
 ---
-title: "Embedder Configuration Reference"
-sidebarTitle: "Configurations"
+title: Configurations
+seo:
+  title: "Embedder Configuration Reference - Mem0"
 description: "Reference for embedder configuration options in Mem0, including provider selection and model settings."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "AWS Bedrock as Embedding Provider"
-sidebarTitle: "AWS Bedrock"
+title: AWS Bedrock
+seo:
+  title: "AWS Bedrock as Embedding Provider - Mem0"
 description: "Configure AWS Bedrock as an embedding provider in Mem0 with IAM credentials and boto3 authentication."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Azure OpenAI as Embedding Provider"
-sidebarTitle: "Azure OpenAI"
+title: Azure OpenAI
+seo:
+  title: "Azure OpenAI as Embedding Provider - Mem0"
 description: "Configure Azure OpenAI as an embedding provider in Mem0 with API key, deployment, and endpoint settings."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Google AI as Embedding Provider"
-sidebarTitle: "Google AI"
+title: Google AI
+seo:
+  title: "Google AI as Embedding Provider - Mem0"
 description: "Configure Google AI as an embedding provider in Mem0 using Gemini models and the GOOGLE_API_KEY variable."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LangChain as Embedding Provider"
-sidebarTitle: "LangChain"
+title: LangChain
+seo:
+  title: "LangChain as Embedding Provider - Mem0"
 description: "Use LangChain as an embedding provider in Mem0 to access a wide range of models through a unified interface."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LM Studio as Embedding Provider"
-sidebarTitle: "LM Studio"
+title: "LM Studio"
+seo:
+  title: "LM Studio as Embedding Provider - Mem0"
 description: "Configure LM Studio as an embedding provider in Mem0 for local embedding generation with models like nomic-embed-text."
 ---
 You can use embedding models from LM Studio to run Mem0 locally.
@@ -1,6 +1,7 @@
 ---
-title: "Ollama as Embedding Provider"
-sidebarTitle: "Ollama"
+title: "Ollama"
+seo:
+  title: "Ollama as Embedding Provider - Mem0"
 description: "Configure Ollama as an embedding provider in Mem0 to generate embeddings locally using open-source models."
 ---
 You can use embedding models from Ollama to run Mem0 locally.
@@ -1,6 +1,7 @@
 ---
-title: "OpenAI as Embedding Provider"
-sidebarTitle: "OpenAI"
+title: OpenAI
+seo:
+  title: "OpenAI as Embedding Provider - Mem0"
 description: "Configure OpenAI as an embedding provider in Mem0 using models like text-embedding-3-large for vector generation."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Together AI as Embedding Provider"
-sidebarTitle: "Together"
+title: Together
+seo:
+  title: "Together AI as Embedding Provider - Mem0"
 description: "Configure Together AI as an embedding provider in Mem0 with support for 1024-dimensional embedding models."
 ---

@@ -11,7 +12,7 @@ To use Together embedding models, set the `TOGETHER_API_KEY` environment variabl
 <Note> The `embedding_model_dims` parameter for `vector_store` should be set to `1024` for Together embedder. </Note>

 <Warning>
-**Breaking default change.** The default Together embedding model is now `intfloat/multilingual-e5-large-instruct` (**1024-dim**), replacing the previous default `togethercomputer/m2-bert-80M-8k-retrieval` (**768-dim**). If you created a self-hosted vector store with the old default, its collection is 768-dim and will reject the new 1024-dim vectors — **recreate/reindex the collection at 1024 dimensions** after upgrading. To defer the change, pin the previous values explicitly (`model="togethercomputer/m2-bert-80M-8k-retrieval"`, `embedding_dims=768`) — note Together no longer lists this model among its recommended embeddings, so reindexing at 1024 is the durable path.
+**Breaking default change.** The default Together embedding model is now `intfloat/multilingual-e5-large-instruct` (**1024-dim**), replacing the previous default `togethercomputer/m2-bert-80M-8k-retrieval` (**768-dim**). If you created a self-hosted vector store with the old default, its collection is 768-dim and will reject the new 1024-dim vectors **recreate/reindex the collection at 1024 dimensions** after upgrading. To defer the change, pin the previous values explicitly (`model="togethercomputer/m2-bert-80M-8k-retrieval"`, `embedding_dims=768`) note Together no longer lists this model among its recommended embeddings, so reindexing at 1024 is the durable path.
 </Warning>

 <CodeGroup>
@@ -1,6 +1,7 @@
 ---
-title: "Embedding Providers Overview"
-sidebarTitle: Overview
+title: Overview
+seo:
+  title: "Embedding Providers Overview - Mem0"
 description: "Overview of all supported embedding model providers in Mem0, including OpenAI, Azure, Ollama, and more."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LLM Configuration Reference"
-sidebarTitle: "Configurations"
+title: Configurations
+seo:
+  title: "LLM Configuration Reference - Mem0"
 description: "Reference for LLM configuration options in Mem0 for Python and TypeScript, including value precedence rules."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "AWS Bedrock as LLM Provider"
-sidebarTitle: "AWS Bedrock"
+title: AWS Bedrock
+seo:
+  title: "AWS Bedrock as LLM Provider - Mem0"
 description: "Configure AWS Bedrock as an LLM provider in Mem0 with IAM authentication and Claude model support."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Azure OpenAI as LLM Provider"
-sidebarTitle: "Azure OpenAI"
+title: Azure OpenAI
+seo:
+  title: "Azure OpenAI as LLM Provider - Mem0"
 description: "Configure Azure OpenAI as an LLM provider in Mem0 with Azure Identity authentication and deployment settings."
 ---

@@ -3,7 +3,7 @@ title: DeepSeek
 description: "Configure DeepSeek as an LLM provider in Mem0 with API key setup and optional custom endpoint configuration."
 ---

-To use DeepSeek LLM models, you have to set the `DEEPSEEK_API_KEY` environment variable. You can also optionally set `DEEPSEEK_API_BASE` if you need to use a different API endpoint (defaults to `https://api.deepseek.com`).
+To use DeepSeek LLM models, you have to set the `DEEPSEEK_API_KEY` environment variable. You can also optionally set `DEEPSEEK_API_BASE` if you need to use a different API endpoint (defaults to "https://api.deepseek.com").

 ## Usage

@@ -1,6 +1,7 @@
 ---
-title: "Google AI as LLM Provider"
-sidebarTitle: "Google AI"
+title: Google AI
+seo:
+  title: "Google AI as LLM Provider - Mem0"
 description: "Configure Google Gemini as an LLM provider in Mem0 using the google.genai SDK and GOOGLE_API_KEY variable."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LangChain as LLM Provider"
-sidebarTitle: "LangChain"
+title: LangChain
+seo:
+  title: "LangChain as LLM Provider - Mem0"
 description: "Use LangChain as an LLM provider in Mem0 to integrate with various chat models through a unified interface."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LM Studio as LLM Provider"
-sidebarTitle: "LM Studio"
+title: LM Studio
+seo:
+  title: "LM Studio as LLM Provider - Mem0"
 description: "Configure LM Studio as an LLM provider in Mem0 for running local language models via an OpenAI-compatible API."
 ---

@@ -77,7 +78,7 @@ m.add(messages, user_id="alice123", metadata={"category": "movies"})
  To use LM Studio, you need to:
  1. Download and install [LM Studio](https://lmstudio.ai/)
  2. Start a local server from the "Server" tab
-  3. Set the appropriate `lmstudio_base_url` in your configuration (default is usually `http://localhost:1234/v1`)
+  3. Set the appropriate `lmstudio_base_url` in your configuration (default is usually http://localhost:1234/v1)
 </Note>

 ## Config
@@ -3,7 +3,7 @@ title: MiniMax
 description: "Configure MiniMax as an LLM provider in Mem0 with API key setup and optional custom endpoint configuration."
 ---

-To use MiniMax LLM models, you have to set the `MINIMAX_API_KEY` environment variable. You can also optionally set `MINIMAX_API_BASE` if you need to use a different API endpoint (defaults to `https://api.minimax.io/v1`).
+To use MiniMax LLM models, you have to set the `MINIMAX_API_KEY` environment variable. You can also optionally set `MINIMAX_API_BASE` if you need to use a different API endpoint (defaults to "https://api.minimax.io/v1").

 ## Usage

@@ -1,6 +1,7 @@
 ---
-title: "Ollama as LLM Provider"
-sidebarTitle: "Ollama"
+title: Ollama
+seo:
+  title: "Ollama as LLM Provider - Mem0"
 description: "Configure Ollama as an LLM provider in Mem0 for running local language models with tool-calling support."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "OpenAI as LLM Provider"
-sidebarTitle: "OpenAI"
+title: OpenAI
+seo:
+  title: "OpenAI as LLM Provider - Mem0"
 description: "Configure OpenAI as an LLM provider in Mem0 with support for GPT models and Openrouter compatibility."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Together AI as LLM Provider"
-sidebarTitle: "Together"
+title: Together
+seo:
+  title: "Together AI as LLM Provider - Mem0"
 description: "Configure Together AI as an LLM provider in Mem0 with API key setup and optional custom endpoint configuration."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "xAI Grok as LLM Provider"
-sidebarTitle: "xAI"
+title: xAI
+seo:
+  title: "xAI Grok as LLM Provider - Mem0"
 description: "Configure xAI Grok models as an LLM provider in Mem0 with API key setup and usage examples."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "LLM Providers Overview"
-sidebarTitle: Overview
+title: Overview
+seo:
+  title: "LLM Providers Overview - Mem0"
 description: "Overview of all supported LLM providers in Mem0, including OpenAI, Anthropic, Groq, Ollama, and more."
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Reranker Providers Overview"
-sidebarTitle: "Overview"
+title: Overview
+seo:
+  title: "Reranker Providers Overview - Mem0"
 description: 'Pick the right reranker path to boost Mem0 search relevance.'
 ---

@@ -1,6 +1,7 @@
 ---
-title: "Vector Store Configuration Reference"
-sidebarTitle: "Configurations"
+title: Configurations
+seo:
+  title: "Vector Store Configuration Reference - Mem0"
 description: "Reference for vector database configuration options in Mem0, including provider selection and connection settings."
 ---

@@ -95,7 +95,7 @@ Uses the identity from Azure PowerShell (`Connect-AzAccount`).
 7. **Azure Developer CLI Credential:**
 Uses the session from Azure Developer CLI (`azd auth login`).

-<Note> If an API key is provided, it will be used for authentication over an Azure Identity </Note>
+<Note> If an API is provided, it will be used for authentication over an Azure Identity </Note>
 To enable Role-Based Access Control (RBAC) for Azure AI Search, follow these steps:

 1. In the Azure Portal, navigate to your **Azure AI Search** service.
@@ -1,6 +1,7 @@
 ---
-title: "LangChain as Vector Store Provider"
-sidebarTitle: "LangChain"
+title: LangChain
+seo:
+  title: "LangChain as Vector Store Provider - Mem0"
 description: "Use LangChain as a unified vector store provider in Mem0 to access multiple vector databases through one interface."
 ---

@@ -5,12 +5,6 @@ description: "Use pgvector as a vector store in Mem0 for PostgreSQL-based vector

 [pgvector](https://github.com/pgvector/pgvector) is an open-source vector similarity search extension for Postgres. After connecting to Postgres, run `CREATE EXTENSION IF NOT EXISTS vector;` to create the vector extension.

-The TypeScript SDK loads the `pg` driver only when you use this store, so install it alongside `mem0ai`:
-
-```bash
-npm install pg
-```
-
 ### Usage

 <CodeGroup>
@@ -94,7 +94,6 @@ Here are the parameters available for configuring Pinecone:
 | `hybrid_search` | Whether to enable hybrid search | `False` |
 | `metric` | Distance metric for vector similarity | `"cosine"` |
 | `batch_size` | Batch size for operations | `100` |
-| `extra_params` | Additional keyword arguments passed to the `Pinecone` client constructor. Ignored when `client` is supplied. | `None` |
 | `namespace` | Namespace for the collection, useful for multi-tenancy. | `None` |
 </Tab>
 <Tab title="TypeScript">
@@ -102,7 +102,7 @@ Here are the parameters available for configuring Upstash Vector:
 | `url`               | URL for the Upstash Vector index   | `None`        |
 | `token`             | Token for the Upstash Vector index | `None`        |
 | `client`            | An `upstash_vector.Index` instance | `None`        |
-| `collection_name`   | The default namespace used         | `"mem0"`      |
+| `collection_name`   | The default namespace used         | `""`          |
 | `enable_embeddings` | Whether to use Upstash embeddings  | `False`       |

 <Note>
@@ -1,6 +1,7 @@
 ---
-title: "Vector Store Providers Overview"
-sidebarTitle: "Overview"
+title: Overview
+seo:
+  title: "Vector Store Providers Overview - Mem0"
 description: "Overview of all supported vector databases in Mem0, including Qdrant, Chroma, PGVector, Pinecone, Oracle, and more."
 ---

@@ -30,7 +30,7 @@ pip install google-adk mem0ai python-dotenv

 ## Code Breakdown

-Let's get started and understand the different components required in building a healthcare assistant powered by memory.
+Let's get started and understand the different components required in building a healthcare assistant powered by memory

 ```python
 # Import dependencies
@@ -1,388 +0,0 @@
---
-title: Build a Company Brain with Mem0 Platform and Supabase
-description: "Build a shared company brain using Mem0 Platform as the managed memory layer, Supabase as your system of record, and the Mem0 MCP server."
---
-
-<Info icon="server">
-**Uses:** Mem0 **Platform** (`MemoryClient`) · **System of record:** Supabase (Postgres + Auth) · **Access layer:** the hosted Mem0 MCP server. **You'll build:** a company brain your whole org (and every agent) writes to and queries, ending with a new-hire onboarding demo.
-</Info>
-
-Companies lose knowledge constantly: why you picked Postgres over Mongo, who owns billing, the deploy rule only one engineer remembers. A **company brain** captures this and answers questions about it, for every employee and every agent, and keeps it after people leave.
-
-We'll build one on **Mem0 Platform** (the managed memory layer, so there's no vector DB to run) with **Supabase as the system of record** (where your employees, teams, and source documents actually live) and the **Mem0 MCP server** as the wire that lets Claude Code, Cursor, or a Slack bot all reach the same brain.
-
-<Note>
-**How Platform and Supabase divide the work.** Mem0 Platform manages storage and extraction server-side, you do **not** point it at your own database. Supabase is your app's source of truth and identity provider; we *ingest* knowledge from Supabase into the brain and use Supabase Auth to decide who's asking. (If you want to self-host the vector store instead, that's the OSS path, see the [Supabase vector store reference](/components/vectordbs/dbs/supabase).)
-</Note>
-
-## Architecture
-
-```mermaid
-flowchart LR
-  subgraph SB["Supabase: system of record"]
-    K[(knowledge / employees / teams)]
-    AU[Auth · who is asking]
-  end
-  subgraph M0["Mem0 Platform: the brain"]
-    B[(managed memory)]
-  end
-  K -->|ingest| B
-  AU -->|maps to scope| B
-  CC[Claude Code] --> MCP[Mem0 MCP server]
-  CU[Cursor] --> MCP
-  SL[Slack bot] --> MCP
-  MCP --> B
-```
-
-Memory splits by entity. An individual is a **`user_id`** (their Supabase Auth id). Shared knowledge lives on an **`agent_id`**: the company-wide brain is `org:acme`, and each team is its own agent, e.g. `team:payments`. A person's own facts route to their `user_id`; company and team facts route to the agent. This split is what lets one search return "my" context alongside the shared org knowledge.
-
-## Prerequisites
-
- **Python 3.9+**
- A **Mem0 Platform API key**, [app.mem0.ai/dashboard/api-keys](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-company-brain). (Platform runs extraction and embeddings for you, so there's no OpenAI key to manage.)
- A **Supabase** project, [supabase.com](https://supabase.com)
-
-About 20 minutes.
-
---
-
-## Step 1: Get your Mem0 Platform API key
-
-Sign in at [app.mem0.ai](https://app.mem0.ai) and copy a key from **Dashboard → API Keys**. The key is scoped to your org and project; Mem0 resolves both server-side, so you never pass IDs by hand.
-
-## Step 2: Create the Supabase system of record
-
-In the Supabase **SQL editor**, create the tables your company already thinks in: people, teams, and a `knowledge` table the brain will ingest from. Identity reuses Supabase Auth's built-in `auth.users`.
-
-```sql
-- Employees extend Supabase Auth's users; identity is auth.users.id (uuid)
-create table public.employees (
-  id     uuid primary key references auth.users (id) on delete cascade,
-  name   text not null,
-  team   text not null
-);
-
-- The company knowledge the brain ingests. `scope` decides who can recall it.
-create table public.knowledge (
-  id             bigint generated always as identity primary key,
-  scope          text not null,                    -- the shared agent this belongs to: 'org:acme' | 'team:payments'
-  content        text not null,
-  author         uuid references auth.users (id),   -- who recorded it (their user_id); null for org seed data
-  created_at     timestamptz default now(),
-  mem0_synced_at timestamptz                        -- null until ingested into the brain
-);
-create index on public.knowledge (mem0_synced_at, created_at);
-
-- Seed a little company knowledge to ingest.
-insert into public.knowledge (scope, content) values
-  ('org:acme', 'We chose Postgres over MongoDB for the core product for strong transactional guarantees and relational joins.'),
-  ('org:acme', 'All production deploys go out Tuesday and Thursday; never on Fridays.'),
-  ('org:acme', 'Customer data must stay in the EU region for GDPR compliance.'),
-  ('org:acme', 'Billing is owned by the Payments team, and Alice is the Payments tech lead.'),
-  ('team:payments', 'Stripe is our processor; webhooks are verified with PAYMENTS_WEBHOOK_SECRET.');
-```
-
-Grab your project URL and **service-role** key from **Settings → API** (the ingestion job runs server-side and needs to read every scope).
-
-## Step 3: Project setup
-
-```bash
-mkdir company-brain && cd company-brain
-pip install "mem0ai>=2.0.17" supabase requests   # 2.0.17+ for agent_custom_instructions
-```
-
-```bash
-export MEM0_API_KEY="m0-..."
-export SUPABASE_URL="https://<project-ref>.supabase.co"
-export SUPABASE_SERVICE_KEY="<service-role-key>"
-```
-
-## Step 4: Configure the brain
-
-Create **`brain.py`**. This constructs the Platform client and teaches it what to remember. The key is the **two** instruction sets: `custom_instructions` governs a person's own (`user_id`) memories, and `agent_custom_instructions` governs shared (`agent_id`) memories, phrased in the third person so company facts read "The company…", not "The user's organization…". `custom_categories` files each memory under a useful label.
-
-```python
-# brain.py
-import os
-from mem0 import MemoryClient
-
-client = MemoryClient(api_key=os.environ["MEM0_API_KEY"])
-
-# Steer extraction (project-wide). Runs server-side; no LLM key needed here.
-client.project.update(
-    # Governs a person's OWN memories (user_id).
-    custom_instructions=(
-        "Extract the individual's own durable preferences, context, and how they work. "
-        "Ignore greetings and one-off chatter."
-    ),
-    # Governs SHARED memories (agent_id); write them in the third person.
-    agent_custom_instructions=(
-        "Extract durable company/team knowledge in the third person "
-        "(\"The company...\", \"The team...\"): decisions and their rationale, ownership "
-        "(who owns what), processes, policies, tooling choices, and gotchas. "
-        "Ignore greetings, scheduling, and one-off chatter."
-    ),
-    custom_categories=[
-        {"decision": "Architectural or product decisions and why they were made"},
-        {"ownership": "Who owns a system, service, or process"},
-        {"policy": "Compliance, security, and process rules"},
-        {"tooling": "Tools, services, and how they're configured"},
-    ],
-)
-
-# Scopes. A person is a user_id; shared brains are agent_ids.
-COMPANY = "org:acme"                       # agent_id: company-wide shared brain
-def team(name):   return f"team:{name}"    # agent_id: a team's shared brain
-def person(uid):  return uid               # user_id: an individual (Supabase auth id)
-```
-
-Run it once to apply the project settings:
-
-```bash
-python -c "import brain; print('brain configured')"
-```
-
-
-## Step 5: Ingest company knowledge from Supabase
-
-This is where Supabase and the brain connect. Create **`ingest.py`**: read un-synced rows from `knowledge`, add each to the Platform brain under its scope, then mark it synced. Platform `add()` is **asynchronous**, it returns an `event_id` you can poll, so we include a small `wait_for` helper.
-
-```python
-# ingest.py
-import os, time, requests
-from supabase import create_client
-from brain import client, person
-
-sb = create_client(os.environ["SUPABASE_URL"], os.environ["SUPABASE_SERVICE_KEY"])
-MEM0_HEADERS = {"Authorization": f"Token {os.environ['MEM0_API_KEY']}"}
-
-def wait_for(event_id, timeout=30):
-    """Platform extraction is async; poll the event until it settles."""
-    for _ in range(timeout):
-        r = requests.get(f"https://api.mem0.ai/v1/event/{event_id}/", headers=MEM0_HEADERS).json()
-        if r.get("status") in ("SUCCEEDED", "FAILED"):
-            return r["status"]
-        time.sleep(1)
-    return "TIMEOUT"
-
-# 1. Read knowledge that hasn't been ingested yet
-rows = sb.table("knowledge").select("*").is_("mem0_synced_at", "null").execute().data
-
-for row in rows:
-    # 2. Add it. agent_id = the shared scope (org/team); user_id = who recorded it.
-    #    Mem0 routes shared facts to the agent and personal facts to the individual,
-    #    so pass both when there's an author.
-    add_kwargs = {
-        "agent_id": row["scope"],
-        "metadata": {"source": "supabase", "knowledge_id": row["id"]},
-    }
-    if row["author"]:
-        add_kwargs["user_id"] = person(row["author"])
-    res = client.add([{"role": "user", "content": row["content"]}], **add_kwargs)
-    # 3. Platform returns an event_id; wait for extraction to finish
-    event_id = res.get("event_id") if isinstance(res, dict) else None
-    if event_id:
-        wait_for(event_id)
-    # 4. Mark the row synced so we never double-ingest
-    sb.table("knowledge").update({"mem0_synced_at": "now()"}).eq("id", row["id"]).execute()
-
-print(f"Ingested {len(rows)} knowledge items into the company brain.")
-```
-
-```bash
-python ingest.py
-```
-
-```text
-Ingested 5 knowledge items into the company brain.
-```
-
-Re-running is safe, `mem0_synced_at` gates it, so a nightly cron can keep the brain in step with Supabase.
-
-## Step 6: Ask the brain
-
-Create **`ask.py`**. It searches everything relevant to the asker: their own (`user_id`) memories **plus** the shared company and team (`agent_id`) memories. This has to be an **`OR`**, each memory row belongs to exactly one entity, so a flat filter or an `AND` of a `user_id` and an `agent_id` matches nothing.
-
-```python
-# ask.py
-import sys
-from brain import client, COMPANY, team, person
-
-def ask(question: str, uid: str | None = None, user_team: str | None = None) -> str:
-    scopes = [{"agent_id": COMPANY}]              # company-wide brain
-    if user_team:
-        scopes.append({"agent_id": team(user_team)})   # the asker's team
-    if uid:
-        scopes.append({"user_id": person(uid)})        # the asker's own memories
-    hits = client.search(
-        query=question,
-        filters={"OR": scopes},   # OR, never AND (one FK per memory row)
-        top_k=5,
-        rerank=True,
-    )
-    return "\n".join(f"- {h['memory']}" for h in hits.get("results", hits))
-
-if __name__ == "__main__":
-    print(ask(" ".join(sys.argv[1:]) or "When can we deploy?"))
-```
-
-```bash
-python ask.py "Why did we pick Postgres, and can I deploy on Friday?"
-```
-
-```text
- The company chose Postgres over MongoDB for strong transactional guarantees and relational joins
- The company's production deploys go out Tuesday and Thursday, never on Fridays
-```
-
-Search returns every relevant memory, so a question resolves across separate facts, here it pulls both the owning team and the person:
-
-```bash
-python ask.py "Who should I talk to about billing?"
-```
-
-```text
- Billing is owned by the Payments team
- Alice is the Payments tech lead
-```
-
-## Step 7: Sharper retrieval
-
-Platform search is hybrid (semantic + keyword) and filterable. Combine a keyword pass with a category filter to answer precise questions:
-
-```python
-client.search(
-    query="webhook signing secret",
-    filters={"agent_id": "team:payments", "categories": {"in": ["tooling"]}},
-    keyword_search=True,     # hybrid keyword + semantic
-    rerank=True,
-    threshold=0.3,
-)
-```
-
-Filters use keyword operators (`in`, `gte`, `contains`, …) and AND/OR/NOT, so you can scope by date, category, or metadata, for example the company's policies added this quarter:
-
-```python
-client.search(
-    query="compliance rules",
-    filters={"AND": [
-        {"agent_id": "org:acme"},
-        {"categories": {"in": ["policy"]}},
-        {"created_at": {"gte": "2026-01-01"}},
-    ]},
-)
-```
-
-## Step 8: Expose the brain to every agent (MCP)
-
-A brain only your script can reach isn't a company brain. Mem0's **hosted MCP server** lets any agent (Claude Code, Cursor, a Slack bot) query and contribute to the *same* brain. The endpoint is `https://mcp.mem0.ai/mcp`, and the supported way to connect is the `mcp-add` helper, which registers the server and runs Mem0's OAuth login so no key ever lands in a config file.
-
-<Tabs>
-<Tab title="Claude Code / Cursor">
-```bash
-npx mcp-add --url "https://mcp.mem0.ai/mcp" --clients "claude code,cursor"
-```
-Complete the browser login on first connect. Now the agent has the brain's memory tools (`add_memory`, `search_memories`, and more) available in-editor.
-</Tab>
-<Tab title="Manual (.mcp.json)">
-```json
-{
-  "mcpServers": {
-    "mem0": { "url": "https://mcp.mem0.ai/mcp" }
-  }
-}
-```
-Auth happens via Mem0's OAuth flow on first use, don't paste a static token into the file (the hosted gateway may reject a raw `Token` header).
-</Tab>
-<Tab title="Slack bot">
-```python
-# A Slack bot is just another MCP client. Point its MCP layer at the same URL,
-# authenticate via Mem0's OAuth flow, and pass the company scope on each call.
-await mcp.call_tool("search_memories", {
-    "query": user_message,
-    "agent_id": "org:acme",
-})
-```
-</Tab>
-</Tabs>
-
-With this, an engineer asks the brain from their editor and a teammate asks it from Slack, one shared memory behind both.
-
-## Step 9: Onboard a new hire (the payoff)
-
-This is what a company brain is *for*. Dana joins, and her identity comes from **Supabase Auth**, which maps straight to her Mem0 `user_id`. She asks the questions every new hire asks and gets real answers on day one, drawn from the shared company (and her team's) brain, plus anything she's told it herself.
-
-```python
-# onboarding.py
-from brain import client, person
-from ask import ask
-
-# In a real app these come from sb.auth.get_user(jwt) and the employees table.
-dana_uid, dana_team = "8f3c...-dana", "payments"
-
-# Dana also tells the brain how *she* works. This is personal, so it goes to her
-# user_id, not the shared agent, and stays scoped to her.
-client.add(
-    [{"role": "user", "content": "I prefer early returns over nested ifs, and I review PRs in the morning."}],
-    user_id=person(dana_uid),
-)
-
-for q in [
-    "Who owns billing and who do I talk to?",   # company (agent) knowledge
-    "When are deploys, and are there hard rules?",
-    "How do I like to write code?",             # Dana's own (user) knowledge
-]:
-    print(f"Q: {q}\nA: {ask(q, uid=dana_uid, user_team=dana_team)}\n")
-```
-
-```text
-Q: Who owns billing and who do I talk to?
-A: - Billing is owned by the Payments team; Alice is the Payments tech lead
-
-Q: When are deploys, and are there hard rules?
-A: - The company's production deploys go out Tuesday and Thursday, never on Fridays
-
-Q: How do I like to write code?
-A: - User prefers early returns over nested ifs
-```
-
-The same `ask()` blends the shared company facts with Dana's own preference, because the `OR` filter spans both her `user_id` and the org and team `agent_id`s.
-
-Dana onboarded herself by asking, drawing on the shared brain the rest of the team had been filling.
-
-## Production notes
-
-<Warning>
-**`user_id` vs `agent_id`.** An individual is a `user_id`; shared brains (company, team) are `agent_id`s. Keeping them separate is what gives you the third-person "The company…" framing and lets a person's own context sit alongside org knowledge. Put a secret like a webhook key on a **team** agent, never the company agent, or everyone can recall it, and mirror the boundary in Supabase with a Row Level Security policy on `knowledge`.
-</Warning>
-
-<Warning>
-**Search must `OR` the scopes.** A memory row belongs to exactly one entity, so `filters={"OR": [{"user_id": ...}, {"agent_id": "org:acme"}, {"agent_id": "team:..."}]}`. A flat filter, or an `AND` of a `user_id` and an `agent_id`, returns nothing.
-</Warning>
-
-<Warning>
-**`add()` is asynchronous.** It returns `{event_id, status: "PENDING"}` and extraction finishes a moment later, poll `GET /v1/event/{event_id}/` (as in Step 5) when you need to know a write has landed before searching for it.
-</Warning>
-
-<Note>
-**Where the entity ID goes differs by call.** `search()` and `get_all()` take the scope inside `filters={...}` (a top-level `user_id=`/`agent_id=` is rejected). `add()` and `delete_all()` are the opposite, they take it as a top-level keyword: `client.delete_all(agent_id="team:payments")`. Deletes are asynchronous too, so a `get_all` right after a `delete_all` can still show rows for a few seconds.
-</Note>
-
-## Where to take it next
-
- **Auto-feed the brain** from PR descriptions, RFCs, and incident write-ups so it grows without anyone thinking about it, just insert into Supabase `knowledge` and let the cron ingest.
- **Scope by real identity** end to end: verify the Supabase JWT, read `sb.auth.get_user(jwt).user.id` for the `user_id`, look up the person's team, and `OR` their `user_id` with the company and team `agent_id`s on every recall.
- **Give teams a private view** with Supabase RLS so `team:` knowledge is only readable by that team.
-
---
-
-<CardGroup cols={2}>
-  <Card title="Mem0 MCP Server" icon="plug" href="/platform/mem0-mcp">
-    Connect any agent or editor to the brain over MCP.
-  </Card>
-  <Card title="Custom Categories & Instructions" icon="sliders" href="/platform/features/custom-instructions">
-    Steer exactly what the brain extracts and how it's filed.
-  </Card>
-</CardGroup>
-
-<Snippet file="star-on-github.mdx" />
@@ -1,212 +0,0 @@
---
-title: "Shared Project Memory for a Team Repo"
-description: "Give everyone on a repository one shared project memory across Claude Code, Codex, Cursor, Kimi Code and Antigravity, while personal preferences stay private."
-icon: "users"
---
-
-<Info icon="cloud">
-**Works with:** Mem0 Platform · Claude Code, Codex, Cursor, Kimi Code and Antigravity plugins
-</Info>
-
-<Info icon="clock">
-**Time to complete:** ~15 minutes · **Tools:** two coding agents, one Git repository
-</Info>
-
-Maya and Dev both work on `payments-api`. Maya uses Claude Code, Dev uses Codex. On Monday Maya learns the hard way that the payments service must never call the ledger API directly, and that unit tests only run with `pnpm test:unit`. On Tuesday Dev's agent has no idea, and he hits the same wall.
-
-With the Mem0 plugins, what Maya's agent learns about the repository becomes shared project memory. Dev's agent recalls it in his next session, in a different tool, while Maya's personal preferences stay hers.
-
-## How shared memory works
-
-Every memory the plugin saves goes into one of two lanes:
-
-| Lane | What goes in it | Who can read it |
-| --- | --- | --- |
-| **Shared project memory** | Facts about the repository: conventions, decisions, constraints, commands and fixes that work | Everyone working on the same repository |
-| **Personal memory** | Facts about you: preferred tools, style, and anything you asked to be remembered about yourself | Only you |
-
-Mem0 picks the lane from what a fact is about. A fact about the repository goes to shared memory, a fact about you goes to personal memory.
-
-The repository is identified by its Git remote (`origin`), so every clone of the same repo lands in the same shared lane. Claude Code, Codex, Cursor, Kimi Code and Antigravity share the same memory core, so a teammate on any of these tools reads the same project memory.
-
-## Setup
-
-### 1. Put the team in one Mem0 project
-
-Memories live inside a Mem0 project. Everyone's API key must come from the **same project**, or their agents will not see each other's memories.
-
-<Steps>
-  <Step title="Invite teammates to the organization">
-    In the [Mem0 dashboard](https://app.mem0.ai/dashboard?utm_source=oss&utm_medium=cookbook-team-memory), the team lead opens **Settings**, goes to the organization members, and uses **Invite Member**. Teammates without a Mem0 account get an email to sign up.
-  </Step>
-  <Step title="Add them to the project">
-    Once they have joined the organization, open the project's settings and use **Invite Member** again to add each teammate to the project. A teammate has to be in the organization before they can be added to a project.
-  </Step>
-  <Step title="Each teammate creates a key in that project">
-    Each teammate selects the project in the dashboard and creates their own key under [API Keys](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-team-memory). The default Reader role can create keys and save memories.
-  </Step>
-</Steps>
-
-### 2. Install the plugin with a unique user ID
-
-Each person needs a stable user ID. Without one, the plugin uses your computer's account name, and two teammates who are both `dev` on their laptops would share a personal lane.
-
-<Tabs>
-  <Tab title="Maya: Claude Code">
-    ```bash
-    export MEM0_API_KEY='m0-maya-key'
-    claude plugin marketplace add mem0ai/mem0
-    claude plugin install mem0@mem0-plugins --scope user \
-      --config api_key="$MEM0_API_KEY" \
-      --config user_id="maya"
-    unset MEM0_API_KEY
-    ```
-
-    Restart Claude Code, or run `/reload-plugins`. Full details: [Claude Code plugin](/integrations/claude-code).
-  </Tab>
-  <Tab title="Dev: Codex">
-    Add the key and a user ID to your shell profile, so Codex sees them in every session:
-
-    ```bash
-    echo 'export MEM0_API_KEY="m0-dev-key"' >> ~/.zshrc
-    echo 'export MEM0_USER_ID="dev"' >> ~/.zshrc
-    source ~/.zshrc
-    ```
-
-    Then install the plugin:
-
-    ```bash
-    codex plugin marketplace add mem0ai/mem0
-    codex plugin add mem0@mem0-plugins
-    ```
-
-    Restart Codex from a terminal that has the variables set. Full details: [Codex plugin](/integrations/codex).
-  </Tab>
-  <Tab title="Cursor">
-    Install the full plugin as described on the [Cursor plugin](/integrations/cursor) page. When Cursor asks for the plugin configuration, enter your API key and your name in **Memory user ID**, then restart Cursor.
-  </Tab>
-</Tabs>
-
-For [Kimi Code](/integrations/kimi) and [Antigravity](/integrations/antigravity), export `MEM0_USER_ID` next to `MEM0_API_KEY` in your shell profile before starting the tool.
-
-## Maya's session: memory gets captured
-
-Maya opens `payments-api` in Claude Code and works normally:
-
-```text
-Set up the unit tests for the payments service. In this repo we use pnpm, never npm,
-and the payments service must never call the ledger API directly; it always goes
-through the events queue.
-```
-
-Claude runs `pnpm test:unit`, the tests pass, and Maya adds one personal note:
-
-```text
-Thanks. Personally I like very short answers with no summary at the end.
-```
-
-She does not have to save anything. The plugin flushes the session to Mem0 after every five exchanges, when the session ends or compacts, or after five idle minutes. Extraction then takes under a minute. Mem0 splits what it heard into the two lanes:
-
-```text
-Shared project memory:
-  Unit tests for the payments service have been set up and pass (148 tests) using pnpm,
-  and the service communicates with the ledger through the events queue rather than directly
-
-Personal memory (maya):
-  User prefers very short answers with no summary at the end
-  User prefers pnpm over npm as the package manager
-```
-
-An LLM writes each memory, so your wording will differ from these examples.
-
-Maya can check that capture is working with `/mem0:status`.
-
-## Dev's session: memory gets recalled
-
-The next morning Dev opens his own clone of `payments-api` in Codex and starts with:
-
-```text
-I need to add a refund flow to the payments service. How do we run the tests here,
-and how should payments talk to the ledger?
-```
-
-Before Codex answers, the plugin searches with this first prompt and adds the relevant memories to its context:
-
-```text
-Mem0 found these relevant memories from earlier work in this repository:
-1. Unit tests for the payments service have been set up and pass (148 tests) using pnpm,
-   and the service communicates with the ledger through the events queue rather than directly
-```
-
-Codex now uses `pnpm`, runs `pnpm test:unit`, and routes the refund through the events queue, without Dev explaining any of it. Maya's preference for short answers is not in his context: personal memory never crosses to another user.
-
-<Note>
-  Automatic recall runs on the first prompt of a session when it has at least 20 characters. Later in the session, the agent can still call `search_memories`, or you can ask it to search Mem0.
-</Note>
-
-## What else your team gets
-
-### A fix one person finds, everyone keeps
-
-Later that week Maya works on refunds on a feature branch. Her unit tests fail with `STRIPE_WEBHOOK_SECRET is not set`, she copies `.env.example` to `.env.test`, and the tests pass. She also mentions that refunds over $500 always need manual approval. Nobody writes any of this down.
-
-When Dev's tests fail the same way, his agent searches Mem0 and gets:
-
-```text
-1. All unit tests now pass (152 tests) after copying .env.example to .env.test and setting
-   STRIPE_WEBHOOK_SECRET [learnt on branch feature/refunds]
-2. Unit tests for the payments service have been set up and pass (148 tests) using pnpm, ...
-3. POST /refunds endpoint added to the payments service [learnt on branch feature/refunds]
-```
-
-### Branch-aware recall
-
-Memories learned on a branch other than `main` or `master` come back labeled with that branch, as in `[learnt on branch feature/refunds]` above. Dev's agent knows the knowledge may not have reached `main` yet.
-
-### Look up decisions only
-
-Every memory gets a category: `project_knowledge`, `decisions_and_constraints`, `workflows`, `problems_and_fixes`, or `results`. To see what the team has decided about refunds:
-
-```text
-/mem0:search refunds --category decisions_and_constraints
-```
-
-```text
-1. Refunds over $500 are routed to manual approval [learnt on branch feature/refunds]
-2. User prefers very short answers with no summary at the end
-3. User prefers pnpm over npm as the package manager
-```
-
-The team's decision comes first. Maya also sees her own preferences, because every search covers your personal memory too. Teammates never see them.
-
-In Codex, Cursor, Kimi Code and Antigravity, the `search_memories` tool takes the same `category` argument.
-
-## Production patterns
-
-**Narrow recall in a monorepo.** Searches default to the whole repository. Use the `dir` scope to get project memory for the directory you are in. See [Search scope](/integrations/claude-code#search-scope).
-
-**Forgetting stays personal by default.** `/mem0:forget` deletes your memories for the repository. Shared project memory is kept unless you pass `--include-project-memory`, so one teammate cannot wipe the team's knowledge by accident.
-
-**Same remote, same memory.** Clones are matched by their Git `origin` URL. A repository with no remote gets a memory lane tied to its local path, which teammates cannot share.
-
-<Warning>
-  OpenCode and Pi Agent keep memory per user and repository. They do not read or write the shared project lane, so use one of the five plugins above for team memory.
-</Warning>
-
-## What you built
-
- **One project memory per repository**, written by whoever learns something and read by everyone on the team.
- **Cross-tool recall**: knowledge captured in Claude Code reaches a teammate in Codex.
- **Fixes, decisions and branch context** that travel with the repository.
- **Private personal memory** that stays with each developer.
-
-<CardGroup cols={2}>
-  <Card title="Agent Plugins Overview" icon="puzzle-piece" href="/integrations/agent-plugins">
-    Compare every Mem0 plugin and what each one captures and recalls.
-  </Card>
-  <Card title="Company Brain with Supabase" icon="database" href="/cookbooks/integrations/supabase">
-    Turn company data into shared memory that any agent can query.
-  </Card>
-</CardGroup>
-
-<Snippet file="star-on-github.mdx" />
@@ -1,6 +1,7 @@
 ---
-title: "Cookbooks and Tutorials"
-sidebarTitle: "Overview"
+title: Overview
+seo:
+  title: "Cookbooks and Tutorials - Mem0"
 description: "Browse cookbook examples and tutorials for building AI applications with Mem0, from companion chatbots to AI agents."
 ---

@@ -36,7 +37,7 @@ Every cookbook opens with a **Works with** badge naming the SDK surface it uses.
    | [Memory-Powered Support Agent](/cookbooks/operations/support-inbox) | Operations | OSS only |
  </Tab>
  <Tab title="Hosted Platform">
-    Twenty-one cookbooks run on the hosted Platform, using `MemoryClient` or the Mem0 MCP server with a `MEM0_API_KEY`.
+    Twenty cookbooks run on the hosted Platform, using `MemoryClient` or the Mem0 MCP server with a `MEM0_API_KEY`.

    | Cookbook | Category | Works with |
    | --- | --- | --- |
@@ -57,7 +58,6 @@ Every cookbook opens with a **Works with** badge naming the SDK surface it uses.
    | [Memory-Powered Agent SDK](/cookbooks/integrations/agents-sdk-tool) | Integrations | Platform only |
    | [Persistent Mastra Agents](/cookbooks/integrations/mastra-agent) | Integrations | Platform only |
    | [Search with Personal Context](/cookbooks/integrations/tavily-search) | Integrations | Platform only |
-    | [Shared Project Memory for a Team Repo](/cookbooks/integrations/team-project-memory) | Integrations | Platform only |
    | [Automated Email Intelligence](/cookbooks/operations/email-automation) | Operations | OSS and Platform |
    | [Content Creation Workflow](/cookbooks/operations/content-writing) | Operations | OSS and Platform |
    | [Multi-Session Research Agent](/cookbooks/operations/deep-research) | Operations | Platform only |
@@ -89,8 +89,8 @@ On Mem0 Platform, these stores are managed for you. In OSS, you choose and opera
 ## Next steps

 <CardGroup cols={3}>
-  <Card title="Entity scoping" icon="brain" href="/platform/features/entity-scoped-memory">
-    Organize Platform memories by user, agent, app, and run.
+  <Card title="Memory types" icon="brain" href="/core-concepts/memory-types">
+    Choose the right scope for user, agent, run, and session memory.
  </Card>
  <Card title="Memory operations" icon="database" href="/core-concepts/memory-operations/add">
    Add, search, update, and delete memories from your app.
@@ -1,6 +1,7 @@
 ---
-title: "Delete Memory Operation"
-sidebarTitle: "Delete Memory"
+title: Delete Memory
+seo:
+  title: "Delete Memory Operation - Mem0"
 description: Remove memories from Mem0 either individually, in bulk, or via filters.
 icon: "trash"
 iconType: "solid"
@@ -1,6 +1,7 @@
 ---
-title: "Update Memory Operation"
-sidebarTitle: "Update Memory"
+title: Update Memory
+seo:
+  title: "Update Memory Operation - Mem0"
 description: Modify an existing memory by updating its content or metadata.
 icon: "pen-to-square"
 iconType: "solid"
@@ -0,0 +1,118 @@
+---
+title: Memory Types
+description: "What memory_type actually does in Mem0: procedural memory is implemented, semantic and episodic are not."
+icon: "tag"
+iconType: "solid"
+---
+
+# Memory Types
+
+Mem0's Python SDK exposes a `memory_type` parameter on `add()`. The underlying `MemoryType` enum defines three values, but only one of them is wired up. This page states plainly which is which so you don't build against a type that doesn't exist yet.
+
+## Status
+
+| Type | Enum value | Status | Notes |
+| --- | --- | --- | --- |
+| Procedural memory | `procedural_memory` | **Implemented** | Python OSS only (`Memory`/`AsyncMemory`). Pass `memory_type="procedural_memory"` and `agent_id` to `add()`. Not available on the Platform `MemoryClient`, and not available in the TypeScript SDK (OSS or Platform). |
+| Semantic memory | `semantic_memory` | **Not implemented** | Defined in the `MemoryType` enum but never read anywhere else in the codebase. Passing it to `add()` raises a validation error. There is no evidence in this repo of a roadmap date for this. |
+| Episodic memory | `episodic_memory` | **Not implemented** | Same as above: defined, never wired into the extraction pipeline, rejected by validation, no documented roadmap. |
+
+<Warning>
+  Only `procedural_memory` is a real, working value. Calling `memory.add(messages, memory_type="semantic_memory")` (or `episodic_memory`) is rejected and tells you to pass `procedural_memory` instead. Sync `Memory.add()` raises `Mem0ValidationError`; `AsyncMemory.add()` raises a plain `ValueError`.
+</Warning>
+
+## Procedural memory
+
+Procedural memory stores step-by-step task knowledge (how an agent performs a workflow) rather than facts about a user. It requires `agent_id`:
+
+```python
+from mem0 import Memory
+
+memory = Memory()
+
+memory.add(
+    [
+        {"role": "user", "content": "Book a flight from SFO to NYC"},
+        {"role": "assistant", "content": "1. Search flights. 2. Filter by price. 3. Confirm booking."},
+    ],
+    agent_id="travel-agent",
+    memory_type="procedural_memory",
+)
+```
+
+Omit `memory_type` entirely and Mem0 stores the messages as an ordinary memory: there is no semantic/episodic pathway for it to fall into. Any other explicit value is rejected by validation rather than quietly falling back to an ordinary memory.
+
+## How every other memory is scoped
+
+Outside of the `procedural_memory` special case, Mem0 does not sort memories into named types. Every memory is scoped by the identifiers you pass in, and the same identifiers are used to retrieve it later:
+
+- **`user_id`**: ties a memory to a specific person or account.
+- **`agent_id`**: ties a memory to a specific agent or assistant persona.
+- **`run_id`**: ties a memory to a specific session, task, or conversation thread.
+- **`app_id`** (Platform only): ties a memory to a specific application or tenant, in addition to the three above. See <Link href="/platform/features/entity-scoped-memory">Entity-Scoped Memory</Link>.
+
+At least one identifier is required on `add()`. Passing more than one narrows the scope further (for example, `user_id` + `run_id` together).
+
+```python
+from mem0 import Memory
+
+memory = Memory()
+
+memory.add(
+    "I'm Alex and I prefer boutique hotels.",
+    user_id="alex",
+    run_id="trip-planning-2025",
+)
+
+results = memory.search(
+    "Any hotel preferences?",
+    filters={"user_id": "alex", "run_id": "trip-planning-2025"},
+)
+```
+
+<Tip>
+  Use `run_id` when you want a set of memories to stay tied to one session or task; use `user_id` alone for anything that should persist across every session for that person.
+</Tip>
+
+## How memories are extracted and updated
+
+When `infer=True` (the default) on `add()`, Mem0 runs a single pipeline rather than routing through separate type-specific paths:
+
+1. **Context gathering**: pulls the most recent messages already stored for the same `user_id`/`agent_id`/`run_id` scope.
+2. **Existing memory retrieval**: embeds the new messages and runs a vector search against memories already in that same scope, to find candidates that might need to change.
+3. **Extraction**: a single LLM call compares the new messages against the retrieved candidates and decides, per fact, whether to `ADD`, `UPDATE`, `DELETE`, or leave a memory alone.
+
+Alongside this, both OSS and Platform extract named entities (people, places, organizations) from memory text and use shared entities between memories to boost related results at search time. On Platform, that entity graph is also queryable directly; see <Link href="/platform/features/graph-memory">Graph Memory</Link>. In OSS, entities only affect ranking, there is no separate graph to query.
+
+<Warning>
+  Avoid storing secrets or unredacted PII in memories: they are retrievable by design. Encrypt or hash sensitive values before calling `add()`.
+</Warning>
+
+## Put it into practice
+
+<CardGroup cols={2}>
+  <Card
+    title="Explore Memory Operations"
+    description="Dive into the add/search/update/delete operations next."
+    icon="circle-check"
+    href="/core-concepts/memory-operations/add"
+  />
+  <Card
+    title="Advanced Memory Operations"
+    description="Tune metadata, filters, and retrieval on Platform."
+    icon="sliders"
+    href="/platform/advanced-memory-operations"
+  />
+  <Card
+    title="AI Tutor Cookbook"
+    description="See user_id-scoped memory used in a real tutoring agent."
+    icon="rocket"
+    href="/cookbooks/companions/ai-tutor"
+  />
+  <Card
+    title="Support Inbox Cookbook"
+    description="See user_id-scoped memory used in a support workflow."
+    icon="inbox"
+    href="/cookbooks/operations/support-inbox"
+  />
+</CardGroup>
@@ -41,7 +41,6 @@
                    "pages": [
                      "platform/quickstart",
                      "platform/overview",
-                      "platform/copilot",
                      "platform/agent-signup",
                      "vibecoding",
                      "platform/cli",
@@ -54,6 +53,7 @@
                    "icon": "brain",
                    "pages": [
                      "core-concepts/how-it-works",
+                      "core-concepts/memory-types",
                      "core-concepts/memory-operations/add",
                      "core-concepts/memory-operations/search",
                      "core-concepts/memory-operations/update",
@@ -71,7 +71,6 @@
                        "pages": [
                          "platform/features/v2-memory-filters",
                          "platform/features/entity-scoped-memory",
-                          "platform/features/user-profiles",
                          "platform/features/graph-memory",
                          "platform/features/async-client",
                          "platform/features/multimodal-support",
@@ -326,6 +325,7 @@
                      "integrations/google-ai-adk",
                      "integrations/mastra",
                      "integrations/vercel-ai-sdk",
+                      "integrations/eve",
                      "integrations/vercel",
                      "integrations/chatdev",
                      "integrations/strands"
@@ -366,13 +366,6 @@
              {
                "tab": "Agent Plugins",
                "groups": [
-                  {
-                    "group": "Overview",
-                    "icon": "puzzle-piece",
-                    "pages": [
-                      "integrations/agent-plugins"
-                    ]
-                  },
                  {
                    "group": "Coding Agents",
                    "icon": "terminal",
@@ -381,7 +374,6 @@
                      "integrations/claude-ai",
                      "integrations/cursor",
                      "integrations/codex",
-                      "integrations/kimi",
                      "integrations/opencode",
                      "integrations/antigravity"
                    ]
@@ -451,9 +443,7 @@
                      "cookbooks/integrations/mastra-agent",
                      "cookbooks/integrations/healthcare-google-adk",
                      "cookbooks/integrations/aws-bedrock",
-                      "cookbooks/integrations/tavily-search",
-                      "cookbooks/integrations/supabase",
-                      "cookbooks/integrations/team-project-memory"
+                      "cookbooks/integrations/tavily-search"
                    ]
                  },
                  {
@@ -521,17 +511,6 @@
                      "api-reference/entities/delete-user"
                    ]
                  },
-                  {
-                    "group": "Profiles",
-                    "icon": "id-card",
-                    "pages": [
-                      "api-reference/profiles/get-profile",
-                      "api-reference/profiles/get-profile-settings",
-                      "api-reference/profiles/update-profile-settings",
-                      "api-reference/profiles/generate-profiles",
-                      "api-reference/profiles/get-profile-job"
-                    ]
-                  },
                  {
                    "group": "Organizations",
                    "icon": "building",
@@ -1040,11 +1019,7 @@
    },
    {
      "source": "/concepts/memory-scoring",
-      "destination": "/core-concepts/how-it-works"
-    },
-    {
-      "source": "/core-concepts/memory-types",
-      "destination": "/core-concepts/how-it-works"
+      "destination": "/core-concepts/memory-types"
    },
    {
      "source": "/cookbooks/research-copilot",
@@ -1 +0,0 @@
-<svg height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Claude</title><path d="M4.709 15.955l4.72-2.647.08-.23-.08-.128H9.2l-.79-.048-2.698-.073-2.339-.097-2.266-.122-.571-.121L0 11.784l.055-.352.48-.321.686.06 1.52.103 2.278.158 1.652.097 2.449.255h.389l.055-.157-.134-.098-.103-.097-2.358-1.596-2.552-1.688-1.336-.972-.724-.491-.364-.462-.158-1.008.656-.722.881.06.225.061.893.686 1.908 1.476 2.491 1.833.365.304.145-.103.019-.073-.164-.274-1.355-2.446-1.446-2.49-.644-1.032-.17-.619a2.97 2.97 0 01-.104-.729L6.283.134 6.696 0l.996.134.42.364.62 1.414 1.002 2.229 1.555 3.03.456.898.243.832.091.255h.158V9.01l.128-1.706.237-2.095.23-2.695.08-.76.376-.91.747-.492.584.28.48.685-.067.444-.286 1.851-.559 2.903-.364 1.942h.212l.243-.242.985-1.306 1.652-2.064.73-.82.85-.904.547-.431h1.033l.76 1.129-.34 1.166-1.064 1.347-.881 1.142-1.264 1.7-.79 1.36.073.11.188-.02 2.856-.606 1.543-.28 1.841-.315.833.388.091.395-.328.807-1.969.486-2.309.462-3.439.813-.042.03.049.061 1.549.146.662.036h1.622l3.02.225.79.522.474.638-.079.485-1.215.62-1.64-.389-3.829-.91-1.312-.329h-.182v.11l1.093 1.068 2.006 1.81 2.509 2.33.127.578-.322.455-.34-.049-2.205-1.657-.851-.747-1.926-1.62h-.128v.17l.444.649 2.345 3.521.122 1.08-.17.353-.608.213-.668-.122-1.374-1.925-1.415-2.167-1.143-1.943-.14.08-.674 7.254-.316.37-.729.28-.607-.461-.322-.747.322-1.476.389-1.924.315-1.53.286-1.9.17-.632-.012-.042-.14.018-1.434 1.967-2.18 2.945-1.726 1.845-.414.164-.717-.37.067-.662.401-.589 2.388-3.036 1.44-1.882.93-1.086-.006-.158h-.055L4.132 18.56l-1.13.146-.487-.456.061-.746.231-.243 1.908-1.312-.006.006z" fill="#D97757" fill-rule="nonzero"></path></svg>
@@ -1 +0,0 @@
-<svg height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Claude Code</title><path clip-rule="evenodd" d="M20.998 10.949H24v3.102h-3v3.028h-1.487V20H18v-2.921h-1.487V20H15v-2.921H9V20H7.488v-2.921H6V20H4.487v-2.921H3V14.05H0V10.95h3V5h17.998v5.949zM6 10.949h1.488V8.102H6v2.847zm10.51 0H18V8.102h-1.49v2.847z" fill="#D97757" fill-rule="evenodd"></path></svg>
@@ -1 +0,0 @@
-<svg height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Codex</title><path d="M19.503 0H4.496A4.496 4.496 0 000 4.496v15.007A4.496 4.496 0 004.496 24h15.007A4.496 4.496 0 0024 19.503V4.496A4.496 4.496 0 0019.503 0z" fill="#fff"></path><path d="M9.064 3.344a4.578 4.578 0 012.285-.312c1 .115 1.891.54 2.673 1.275.01.01.024.017.037.021a.09.09 0 00.043 0 4.55 4.55 0 013.046.275l.047.022.116.057a4.581 4.581 0 012.188 2.399c.209.51.313 1.041.315 1.595a4.24 4.24 0 01-.134 1.223.123.123 0 00.03.115c.594.607.988 1.33 1.183 2.17.289 1.425-.007 2.71-.887 3.854l-.136.166a4.548 4.548 0 01-2.201 1.388.123.123 0 00-.081.076c-.191.551-.383 1.023-.74 1.494-.9 1.187-2.222 1.846-3.711 1.838-1.187-.006-2.239-.44-3.157-1.302a.107.107 0 00-.105-.024c-.388.125-.78.143-1.204.138a4.441 4.441 0 01-1.945-.466 4.544 4.544 0 01-1.61-1.335c-.152-.202-.303-.392-.414-.617a5.81 5.81 0 01-.37-.961 4.582 4.582 0 01-.014-2.298.124.124 0 00.006-.056.085.085 0 00-.027-.048 4.467 4.467 0 01-1.034-1.651 3.896 3.896 0 01-.251-1.192 5.189 5.189 0 01.141-1.6c.337-1.112.982-1.985 1.933-2.618.212-.141.413-.251.601-.33.215-.089.43-.164.646-.227a.098.098 0 00.065-.066 4.51 4.51 0 01.829-1.615 4.535 4.535 0 011.837-1.388zm3.482 10.565a.637.637 0 000 1.272h3.636a.637.637 0 100-1.272h-3.636zM8.462 9.23a.637.637 0 00-1.106.631l1.272 2.224-1.266 2.136a.636.636 0 101.095.649l1.454-2.455a.636.636 0 00.005-.64L8.462 9.23z" fill="url(#lobe-icons-codex-_R_0_)"></path><defs><linearGradient gradientUnits="userSpaceOnUse" id="lobe-icons-codex-_R_0_" x1="12" x2="12" y1="3" y2="21"><stop stop-color="#B1A7FF"></stop><stop offset=".5" stop-color="#7A9DFF"></stop><stop offset="1" stop-color="#3941FF"></stop></linearGradient></defs></svg>
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>Cursor</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4.000 4.000) scale(0.66667)" fill="#ffffff" fill-rule="evenodd"><path d="M22.106 5.68L12.5.135a.998.998 0 00-.998 0L1.893 5.68a.84.84 0 00-.419.726v11.186c0 .3.16.577.42.727l9.607 5.547a.999.999 0 00.998 0l9.608-5.547a.84.84 0 00.42-.727V6.407a.84.84 0 00-.42-.726zm-.603 1.176L12.228 22.92c-.063.108-.228.064-.228-.061V12.34a.59.59 0 00-.295-.51l-9.11-5.26c-.107-.062-.063-.228.062-.228h18.55c.264 0 .428.286.296.514z"/></g></svg>
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>Kimi</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4 4) scale(0.66667)"><path d="M21.846 0a1.923 1.923 0 110 3.846H20.15a.226.226 0 01-.227-.226V1.923C19.923.861 20.784 0 21.846 0z" fill="#1783FF"></path><path d="M11.065 11.199l7.257-7.2c.137-.136.06-.41-.116-.41H14.3a.164.164 0 00-.117.051l-7.82 7.756c-.122.12-.302.013-.302-.179V3.82c0-.127-.083-.23-.185-.23H3.186c-.103 0-.186.103-.186.23V19.77c0 .128.083.23.186.23h2.69c.103 0 .186-.102.186-.23v-3.25c0-.069.025-.135.069-.178l2.424-2.406a.158.158 0 01.205-.023l6.484 4.772a7.677 7.677 0 003.453 1.283c.108.012.2-.095.2-.23v-3.06c0-.117-.07-.212-.164-.227a5.028 5.028 0 01-2.027-.807l-5.613-4.064c-.117-.078-.132-.279-.028-.381z" fill="#fff"></path></g></svg>
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>opencode</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4.000 4.000) scale(0.66667)" fill="#ffffff" fill-rule="evenodd"><path d="M16 6H8v12h8V6zm4 16H4V2h16v20z"/></g></svg>
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>Pi</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4.000 4.000) scale(0.02857)" fill="#ffffff" fill-rule="evenodd"><path d="M420 280H280V140H0V0H420V280Z"/><path d="M560 560H420V280H560V560Z"/><path d="M140 560H0V140H140V280H280V420H140V560Z"/></g></svg>
@@ -1,6 +1,7 @@
 ---
-title: "Integrations Overview"
-sidebarTitle: "Overview"
+title: Overview
+seo:
+  title: "Integrations Overview - Mem0"
 description: "Overview of Mem0 integrations with popular AI frameworks and tools for persistent memory and context management."
 ---

@@ -16,8 +17,6 @@ Mem0 seamlessly integrates with popular AI frameworks and tools to enhance your
  **Universal Integration**: Use <Link href="/platform/mem0-mcp">Mem0 MCP</Link> for a standardized protocol that works with ANY AI client.
 </Callout>

-Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent). Other plugins, including the portable package, provide memory without Sidekick.
-
 Here are the available integrations for Mem0:

 ## Integrations
@@ -1,111 +0,0 @@
---
-title: "Agent Plugins Overview"
-sidebarTitle: "Overview"
-description: "Add persistent memory to the coding agent or agent harness you already use. Compare the Mem0 plugins and pick yours."
---
-
-Coding agents forget everything when a session ends: your conventions, the bug you fixed yesterday, the command that finally worked. A Mem0 plugin fixes that inside the tool you already use. It captures what matters while you work and brings it back in the next session.
-
-<Info>
-  Plugins use a [Mem0 Platform](https://app.mem0.ai?utm_source=oss&utm_medium=agent-plugins-overview) account. OpenClaw and Hermes can also run fully self-hosted.
-</Info>
-
-## How a plugin works
-
-<Steps>
-  <Step title="Capture">
-    While you work, the plugin records your prompts, the agent's answers and useful tool results. Credentials are redacted before anything leaves your machine.
-  </Step>
-  <Step title="Extract">
-    Mem0 turns each session into short, durable memories: project conventions, decisions, fixes that worked, and your personal preferences.
-  </Step>
-  <Step title="Recall">
-    In the next session, relevant memories are added to the agent's context automatically or found with a search tool, depending on the plugin.
-  </Step>
-</Steps>
-
-## Coding agents
-
-<CardGroup cols={3}>
-  <Card title="Claude Code" icon="/images/provider-icons/claudecode-color.svg" href="/integrations/claude-code">
-    Automatic capture and recall, six commands, and the Sidekick agent.
-  </Card>
-  <Card title="Codex" icon="/images/provider-icons/codex-color.svg" href="/integrations/codex">
-    Automatic capture and recall in the Codex CLI and app.
-  </Card>
-  <Card title="Cursor" icon="/images/provider-icons/cursor.svg" href="/integrations/cursor">
-    Automatic capture, with recall through a search tool.
-  </Card>
-  <Card title="OpenCode" icon="/images/provider-icons/opencode.svg" href="/integrations/opencode">
-    Recall before every prompt and ten native memory tools.
-  </Card>
-  <Card title="Kimi Code" icon="/images/provider-icons/kimi-color.svg" href="/integrations/kimi">
-    Automatic capture and recall in the Kimi Code CLI.
-  </Card>
-  <Card title="Antigravity" icon="/images/provider-icons/antigravity-color.svg" href="/integrations/antigravity">
-    Automatic capture, with recall through a search tool.
-  </Card>
-</CardGroup>
-
-## Agent harnesses and chat apps
-
-<CardGroup cols={3}>
-  <Card title="OpenClaw" icon="/images/provider-icons/openclaw.svg" href="/integrations/openclaw">
-    Recall and capture on every turn. Platform or self-hosted.
-  </Card>
-  <Card title="Hermes Agent" icon="/images/provider-icons/hermes-tile.svg" href="/integrations/hermes">
-    Mem0 as Hermes' memory provider. Platform or self-hosted.
-  </Card>
-  <Card title="Pi Agent" icon="/images/provider-icons/pi.svg" href="/integrations/pi-agent">
-    Recall before every turn and automatic capture.
-  </Card>
-  <Card title="DeepSeek Harness" icon="/images/provider-icons/deepseek-color.svg" href="/integrations/deepseek-plugin">
-    Automatic recall and capture with two native tools.
-  </Card>
-  <Card title="Claude.ai" icon="/images/provider-icons/claude-color.svg" href="/integrations/claude-ai">
-    Add the verified Mem0 connector from Claude's directory and sign in. No API key needed.
-  </Card>
-  <Card title="Any MCP client" icon="plug" href="/platform/mem0-mcp">
-    Your tool is not listed? Connect it to the hosted Mem0 MCP server.
-  </Card>
-</CardGroup>
-
-## Compare plugins
-
-<Tabs>
-  <Tab title="Coding agents">
-    | Plugin | Auto capture | Auto recall | Skills | Team |
-    | --- | --- | --- | --- | --- |
-    | [Claude Code](/integrations/claude-code) | Yes | First prompt | 6, plus Sidekick | Shared |
-    | [Codex](/integrations/codex) | Yes | First prompt | 6 | Shared |
-    | [Cursor](/integrations/cursor) | Yes | Search tool | 6 | Shared |
-    | [Kimi Code](/integrations/kimi) | Yes | First prompt | 6 | Shared |
-    | [Antigravity](/integrations/antigravity) | Yes | Search tool | 6 | Shared |
-    | [OpenCode](/integrations/opencode) | Yes | Every prompt | 7 | Per user |
-
-    **First prompt:** relevant memories are added before the agent answers the first prompt of a session. **Search tool:** the agent calls `search_memories` when it needs context. **Shared:** teammates on the same repo share project memory.
-  </Tab>
-  <Tab title="Harnesses and chat apps">
-    | Plugin | Auto capture | Auto recall | Tools | Self-hosted |
-    | --- | --- | --- | --- | --- |
-    | [OpenClaw](/integrations/openclaw) | Yes | Every turn | Tools and skills | Yes |
-    | [Hermes Agent](/integrations/hermes) | Yes | Every turn | 4 | Yes |
-    | [Pi Agent](/integrations/pi-agent) | Yes | Every turn | 1 | No |
-    | [DeepSeek Harness](/integrations/deepseek-plugin) | Yes | Every prompt | 2 | No |
-    | [Claude.ai](/integrations/claude-ai) | When asked | When relevant | 9 | No |
-  </Tab>
-</Tabs>
-
-<Note>
-  Claude Code, Codex, Cursor, Kimi Code and Antigravity share the same memory core. Teammates working in the same repository, in any of these tools, read and write one shared project memory while their personal preferences stay private. See [Shared project memory for a team repo](/cookbooks/integrations/team-project-memory).
-</Note>
-
-## Which plugin should I use?
-
- **You code in a terminal or IDE agent:** install the plugin for that tool from the cards above. Each page has its own install steps.
- **Your team uses different agents on the same repo:** pick any of Claude Code, Codex, Cursor, Kimi Code or Antigravity. They share project memory across tools.
- **You chat in Claude:** add the [Mem0 connector](https://claude.com/connectors/mem0) from Claude's directory.
- **Your tool has no plugin:** connect it to the [hosted Mem0 MCP server](/platform/mem0-mcp).
- **You need to keep data on your own infrastructure:** use OpenClaw or Hermes in self-hosted mode.
-
-<Snippet file="star-on-github.mdx" />
@@ -1,22 +1,16 @@
 ---
 title: Antigravity
-description: "Add persistent memory to Google Antigravity with the Mem0 plugin: a search tool, lifecycle hooks, and memory skills."
+description: "Add persistent memory to Google Antigravity with the Mem0 plugin: MCP server, lifecycle hooks, and slash commands."
 ---

-Add persistent memory to [**Google Antigravity**](https://antigravity.google) (`agy` CLI and Desktop IDE) with the Mem0 plugin. The plugin captures completed work, and Antigravity can search those memories in later sessions.
-
-<Info>Current plugin version: `0.3.1`.</Info>
-
-Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+Add persistent memory to [**Google Antigravity**](https://antigravity.google) (`agy` CLI and Desktop IDE) with the Mem0 plugin. Your agent forgets everything between sessions. Mem0 fixes that by storing decisions, preferences, and learnings so they carry over automatically.

 ## Prerequisites

 1. A Mem0 API key (starts with `m0-`):
   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-antigravity">Get your API key</a> (free sign-up at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-antigravity">app.mem0.ai</a>)

-2. Python 3.10 or newer available as `python3`
-
-3. Add the key to your shell profile so it persists across sessions:
+2. Add it to your shell profile so it persists across sessions:

 <CodeGroup>
 ```bash zsh
@@ -32,32 +26,22 @@ echo 'export MEM0_API_KEY="m0-your-api-key"' >> ~/.bashrc && source ~/.bashrc

 **Option A: degit** (recommended):

-<Warning>
-  When upgrading an existing installation, move `~/.gemini/config/plugins/mem0` aside first. Installing over that directory can leave obsolete files from older plugin versions.
-</Warning>
-
 ```bash
 # Install the plugin (MCP server, hooks, scripts)
-npx degit mem0ai/mem0/integrations/antigravity-plugin ~/.gemini/config/plugins/mem0
+npx degit mem0ai/mem0/integrations/mem0-plugin ~/.gemini/config/plugins/mem0
 ```

-This installs the generated Antigravity bundle with the Mem0 server, lifecycle hooks, and six memory skills.
+This installs the MCP server, lifecycle hooks, and shared scripts.

 ## What's Included

 | Component | Included |
 |-----------|:--------:|
-| Local MCP Server (`search_memories`) | Yes |
+| MCP Server (9 memory tools) | Yes |
 | Lifecycle Hooks | Yes |
-| 6 Memory Skills | Yes |
+| 16 Slash Commands | Yes |

-## Memory tools and skills
-
-The full plugin exposes a focused `search_memories` tool and captures completed work through lifecycle hooks. Six skills provide search, status, remember, forget, pause, and resume workflows.
-
-If you need the full set of direct CRUD tools, connect the [hosted Mem0 MCP server](/platform/mem0-mcp) separately instead of installing both configurations under the same server name.
-
-## Hosted MCP tools
+## Available MCP Tools

 | Tool | Description |
 |------|-------------|
@@ -73,52 +57,23 @@ If you need the full set of direct CRUD tools, connect the [hosted Mem0 MCP serv

 ## Lifecycle Hooks

-The plugin translates Antigravity events into the shared Mem0 capture lifecycle.
+The plugin uses the same shell scripts as Claude Code, Cursor, and Codex: hooks bridge environment variables using `${extensionPath}` (Antigravity's plugin-root token).

 | Hook | Event | What it does |
 |------|-------|-------------|
-| **Invocation** | `PreInvocation` | Initializes the first invocation and recovers pending capture |
-| **Post-tool** | `PostToolUse` | Records useful tool results and failures |
-| **Stop** | `Stop` | Reads completed transcript messages and starts a background flush |
+| **Session start** | `SessionStart` | Loads prior memories and displays status banner |
+| **User prompt** | `UserPromptSubmit` | Searches relevant memories before each message |
+| **Pre-tool** | `PreToolUse` | Blocks MEMORY.md writes, enforces `user_id`/`app_id` on mem0 tools |
+| **Post-tool** | `PostToolUse` | Tracks stats, scans bash errors for related memories |
+| **Stop** | `Stop` | Stores a session summary at the end of every assistant turn (not just at session end) |

-Recall is explicit through `search_memories` and the search skill. The current Antigravity adapter does not inject query-specific memory during `PreInvocation` because that event does not include the user's prompt.
-
-What you type is stored as yours. Captured agent summaries are stored as the assistant's, so its suggestions never become your stated preferences.
-
-## Antigravity 1.1.25 workarounds
-
-Antigravity 1.1.25 can validate a plugin's `mcp_config.json` without loading the server. Check whether Mem0 is registered:
-
-```bash
-agy mcp list
-```
-
-If `mem0` is absent, register the plugin's bundled server with Antigravity's supported global MCP command, then start a new session:
-
-```bash
-agy mcp add mem0 python3 ~/.gemini/config/plugins/mem0/core/mcp_server.py
-```
-
-The same release can send hooks with an empty `workspacePaths` array. For the `agy` CLI, pass the current repository explicitly:
-
-```bash
-MEM0_CWD="$PWD" agy
-```
-
-The adapter uses `MEM0_CWD` only when Antigravity omits the workspace. If neither value is available, it skips recall and capture instead of writing memories under an incorrect repository scope.
-
-## Search and capture
-
-The local `search_memories` tool accepts `query`, `top_k`, `category`, `scope` (`repo`, `dir`, or `mine`), and optional `run_id` with every scope. Use a known session ID to recall memories saved in that session; omit it to search across sessions. See [search scopes](/integrations/claude-code#search-scope) for the shared Python search contract, including legacy repository memory compatibility.
-
-Captured prompts and responses retain their full redacted text without a per-message character cutoff. Large extraction inputs are split across requests without dropping message text; recall output and tool-result previews have separate limits.
+What you type is stored as yours. What the agent produces (session summaries and compaction summaries) is stored as the assistant's, so its suggestions never become your stated preferences.

 ## Troubleshooting

 - **No tools appearing**: Restart your Antigravity session after installation
- **No `mem0` entry in `agy mcp list`**: Use the Antigravity 1.1.25 global MCP registration command above
- **Hooks do not capture in the CLI**: Launch `agy` with `MEM0_CWD="$PWD"`
- **"Connection failed"**: Verify your key is set without printing it: `test -n "$MEM0_API_KEY" && echo configured`
+- **"Connection failed"**: Verify your key is set: `echo $MEM0_API_KEY`
+- **MCP 401 Unauthorized**: If `${MEM0_API_KEY}` interpolation doesn't work in your `agy` version, replace with your literal key in `mcp_config.json`

 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
@@ -1,6 +1,7 @@
 ---
-title: "AWS Bedrock Integration"
-sidebarTitle: "AWS Bedrock"
+title: AWS Bedrock
+seo:
+  title: "AWS Bedrock Integration with Mem0"
 description: "Use Mem0 with AWS Bedrock and OpenSearch Service for cloud-native persistent semantic memory storage."
 ---

@@ -130,10 +130,10 @@ print(response.msgs[0].content)

 <CardGroup cols={2}>
  <Card
-    title="How Mem0 works"
-    description="Understand how Mem0 extracts, stores, and retrieves memories for your Camel agents."
+    title="Memory types in Mem0"
+    description="Choose between chat history and semantic search for your Camel agents."
    icon="sparkles"
-    href="/core-concepts/how-it-works"
+    href="/core-concepts/memory-types"
  />
  <Card
    title="Try LangChain next"
@@ -5,8 +5,6 @@ description: "Persistent cross-session memory for Claude Code. Install once, mem

 Claude Code forgets everything between sessions. This plugin fixes that. Install it, work normally, and Claude remembers what happened across sessions.

-<Info>Current plugin version: `0.3.1`.</Info>
-
 ## Prerequisites

 1. A Mem0 Platform account and API key (starts with `m0-`):
@@ -42,14 +40,14 @@ claude plugin uninstall mem0@mem0-plugins      # uninstall the plugin (keeps the

 Once installed, memory works without any action from you:

- **Capture** happens in the background as you work. Hooks save user messages, Claude's answers, changed files, and test/build results locally. Capture records evidence locally; memory extraction runs through Mem0 in a background worker.
- **Recall** happens automatically before Claude's first response in a new session. If the first prompt has at least 20 characters, the plugin searches with that prompt and injects up to five relevant memories. For shorter prompts or later questions, use explicit search.
+- **Capture** happens in the background as you work. Hooks save user messages, Claude's answers, changed files, and test/build results locally. Nothing calls a model or slows your session.
+- **Recall** happens automatically before Claude's first response in a new session. The plugin searches your memories with your prompt and injects up to five relevant ones.

 ### Commands

 | Command | What it does |
 | --- | --- |
-| `/mem0:search` | Search memories from earlier sessions. Supports `--top-k <n>`, `--category <name>`, `--scope <repo\|dir\|mine>`, and `--run-id <session-id>`. |
+| `/mem0:search` | Search memories from earlier sessions. Supports `--top-k <n>`, `--category <name>`, and `--scope <repo\|dir\|mine>`. |
 | `/mem0:status` | Check if memory is working: config, capture state, pending flushes, API key validity. |
 | `/mem0:forget` | Delete your memories for this repo (shared project memory stays unless you pass `--include-project-memory`). |
 | `/mem0:pause` | Pause memory capture. |
@@ -60,12 +58,10 @@ Categories for `--category`: `project_knowledge`, `decisions_and_constraints`, `

 ### Search tool

-After the automatic first-prompt search, Claude can also call `search_memories` with a specific question, and you can run `/mem0:search` yourself. Explicit searches return up to 3 results by default (configurable to 20). The combined search output is capped at 4,000 characters by default, configurable with `max_context_chars`. This recall limit does not truncate captured messages sent for extraction.
+After the automatic first-prompt search, Claude can also call `search_memories` with a specific question, and you can run `/mem0:search` yourself. Explicit searches return up to 3 results by default (configurable to 20). All results are capped at 4,000 characters.

 ### Sidekick agent

-Sidekick is available only in Claude Code.
-
 `mem0:sidekick` is a Sonnet coding agent that runs in a separate Git worktree. Use it to offload investigation, implementation, testing, or review without burning main-session context.

 ```text
@@ -75,23 +71,21 @@ Review its result and send any corrections back to the same sidekick.

 Changes stay in the sidekick's worktree until the main agent reviews and copies them over. By default the worktree branches from the repo's default branch. Set `worktree.baseRef` to `"head"` in your Claude settings to branch from the current commit instead. Uncommitted changes are not copied into the sidekick's worktree.

-At startup, Sidekick receives the memories already recalled for its parent session. It can also call the Mem0 search tool for its assigned task. Start and completion hooks track its work locally; completing a Sidekick task does not independently send a memory-extraction request. Sidekick returns its result, validation, and a local commit when it changes files, so the main agent can review the work before incorporating it.
-
 ## How it works

 The plugin follows a simple cycle: capture during a session, extract memories in the background, recall in the next session.

 <Frame>
-  <img src="/images/plugin-sequence.svg" alt="Sequence diagram: the first user prompt triggers search, hooks capture activity during the session, a background worker extracts memories after every five exchanges or on idle/exit, and the next session recalls them." />
+  <img src="/images/plugin-sequence.svg" alt="Sequence diagram: session start triggers first-prompt search, hooks capture activity during the session, a background worker extracts memories after every five exchanges or on idle/exit, and the next session recalls them." />
 </Frame>

 **Step by step:**

-1. **Capture.** Hooks save the main agent's activity locally: user messages, Claude's answers, changed files, and short test/build results. Direct Sidekick lifecycle records stay local. Subagent results included in the main transcript can provide supporting evidence for extraction; the main agent's final response establishes the outcome. Capture does not call a model.
+1. **Capture.** Hooks save the main agent's activity locally: user messages, Claude's answers, changed files, and short test/build results. Subagent (sidekick) output is excluded. No model calls, no blocking.

 2. **Flush.** After every five completed exchanges, a detached background worker sends that batch to Mem0. Large exchanges flush sooner. Ending or compacting the session flushes anything remaining. If the session sits idle, an auto-flush runs after five minutes (configurable with `MEM0_CODE_IDLE_FLUSH_SECONDS`). The timer resets on each new exchange. The worker survives Claude Code exiting.

-3. **Extract.** Each flush sends `add` calls with `agent_id` (the project identity), `user_id` (you), `app_id` (the repository), and `run_id` (the session). Prompts and responses are redacted without a character cutoff. Large conversations are split across requests without dropping message text. Mem0 classifies each extracted memory as shared project knowledge or a personal preference.
+3. **Extract.** Each flush sends a single `add` call with `agent_id` (the project identity), `user_id` (you), `app_id` (the repository), and `run_id` (the session). Mem0 classifies each extracted memory as shared project knowledge or a personal preference.

 4. **Recall.** On the next session's first prompt, the plugin searches automatically and supplies up to five relevant memories. No model is called to write the query.

@@ -116,14 +110,10 @@ Every memory carries identifiers showing where it came from:
 | Identifier | What it is | Example |
 | --- | --- | --- |
 | `user_id` | You (personal memory only) | Your Mem0 user ID |
-| `agent_id` | The project identity (shared memory only) | `acme-payments-api-<hash>` |
+| `agent_id` | The project identity (shared memory only) | `acme-payments-api` |
 | `app_id` | The repository (scopes both lanes) | `acme-payments-api` |
 | `run_id` | The Claude Code session | The session ID |

-New Git repository memories use an `agent_id` with a hash of the Git remote identity so matching owner/repository names on different hosts stay separate. Searches also include the previous unhashed `agent_id`, scoped by the repository's `app_id`, so existing shared memories remain available after upgrading. Those older memories retain their original namespace, which did not distinguish Git hosts. Local folders continue using a hash of their path.
-
-Explicitly forgetting shared project memory with `--include-project-memory` covers both repository IDs. Without that option, shared memories are preserved.
-
 A search returns the union of shared project memory and your personal preferences. The scope narrows the project part:

 | Scope | What you get |
@@ -134,7 +124,7 @@ A search returns the union of shared project memory and your personal preference

 The `dir` scope is hierarchical: a parent directory sees everything in its children, but a child never sees the parent's memories.

-The search tool accepts an optional `run_id` with every scope (`repo`, `dir`, and `mine`); `/mem0:search` exposes it as `--run-id session-id`. It restricts both shared and personal results to memories saved in that coding-agent session. Omit it to search across sessions. This is a memory filter, not a label for the session making the request; automatically filtering by the current session would hide earlier-session memories. Each memory update still records the session's `run_id`. Set the default scope with the `search_scope` setting or `MEM0_CODE_SEARCH_SCOPE` env var.
+Pass `--run-id <session-id>` to see only what one specific session recorded. Set the default scope with the `search_scope` setting or `MEM0_CODE_SEARCH_SCOPE` env var.

 ## Settings

@@ -155,7 +145,7 @@ Breaking update. Your memories carry over, most local config does not.
 - **Commands replaced.** Old commands replaced by `/mem0:search`, `/mem0:status`, `/mem0:forget`, `/mem0:pause`, `/mem0:resume`, `/mem0:remember`.
 - **MCP server replaced.** Nine read/write tools replaced by the single read-only `search_memories` tool.
 - **Local config ignored.** `~/.mem0/settings.json` and per-project `mem0.md` files are no longer read.
- **Old memories remain searchable.** Pre-upgrade memories may use different categories. Omit category filters if an older memory is missing from the results.
+- **Old memories searchable, not by category.** Normal search finds pre-upgrade memories, but category filters do not.

 ```bash
 claude plugin marketplace update mem0-plugins
@@ -172,36 +162,6 @@ claude plugin update mem0@mem0-plugins --scope user
 | Sidekick won't start | Must be in a Git repo. Check that your Claude Code version supports plugin agents and worktrees. |
 | Remove the plugin | `claude plugin uninstall mem0@mem0-plugins` |

-## Telemetry
-
-The plugin sends usage events (which hook ran, timing, result counts, failure
-types) so Mem0 can see what's used and what's breaking.
-
-These events are **not anonymous**. When an API key is configured, which
-installing the plugin requires, they are sent under your Mem0 account email,
-the same way the Python SDK and the CLI attribute theirs. Without a key they
-are sent under a random per-machine id.
-
-Each event carries the event name, the plugin version, the harness it ran in,
-your OS and Python version, and per-event properties describing what happened:
-timings, counts, coarse outcome and failure labels, and which model was
-configured. Repository and session identifiers are hashed with a random salt
-generated on your machine, so they cannot be linked back to a repository name
-or path.
-
-The exact set is enforced in code rather than by this list: every property is
-filtered through a denylist of sensitive keys and credential-shaped values are
-redacted before anything is sent.
-
-Prompts, memory text, queries, file paths, repository names, and API keys are
-never sent.
-
-Turn it off:
-
-```bash
-export MEM0_TELEMETRY=false
-```
-
 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
    Detailed MCP configuration for all clients
@@ -1,13 +1,9 @@
 ---
 title: Codex
-description: "Add persistent memory to OpenAI Codex with automatic capture, automatic recall, a search tool, and six memory skills."
+description: "Add persistent memory to OpenAI Codex with the Mem0 plugin: MCP server, lifecycle hooks, and SDK skill."
 ---

-Add persistent memory to [**OpenAI Codex**](https://openai.com/codex/) with the Mem0 plugin. Codex forgets everything between tasks. This plugin fixes that by connecting to Mem0's cloud memory layer via MCP, automatically capturing learnings at key lifecycle points, and retrieving relevant context on the first prompt of a session. Codex can use the search tool for recall later in the session.
-
-<Info>Current plugin version: `0.3.1`.</Info>
-
-Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+Add persistent memory to [**OpenAI Codex**](https://openai.com/codex/) with the Mem0 plugin. Codex forgets everything between tasks. This plugin fixes that by connecting to Mem0's cloud memory layer via MCP, automatically capturing learnings at key lifecycle points, and retrieving relevant context before every response.

 ## Prerequisites

@@ -19,9 +15,7 @@ Before setting up Mem0 with Codex, ensure you have:

 2. OpenAI Codex access

-3. Python 3.10 or newer available as `python3`
-
-4. Your API key added to your shell profile (persists across sessions):
+3. Your API key added to your shell profile (persists across sessions):

 <CodeGroup>
 ```bash zsh
@@ -39,7 +33,7 @@ source ~/.bashrc

 ### Option A: Plugin Marketplace (Recommended)

-Install the full plugin, including automatic capture and recall, the `search_memories` tool, and six memory skills.
+Install the full plugin including MCP server, lifecycle hooks, and SDK skill.

 1. Add the Mem0 marketplace:

@@ -81,7 +75,7 @@ bearer_token_env_var = "MEM0_API_KEY"

 Make sure `MEM0_API_KEY` is exported in the shell you launch Codex from, then restart Codex.

-This gives you the hosted MCP tools but not the plugin's lifecycle hooks or six memory skills.
+This gives you the MCP tools but not the lifecycle hooks or SDK skill.

 ### Managing the Plugin

@@ -94,7 +88,7 @@ codex plugin marketplace remove mem0-plugins   # unregister the marketplace enti
 To update, run `codex plugin marketplace upgrade` to pull the latest from the Mem0 repo.

 <Info icon="check">
-  After Option A, ask Codex to search memory for a recent project decision. After Option B, ask it to list your Mem0 entities. If the matching tool responds, the connection is ready.
+  After either option, start a new Codex task and ask: *"List my mem0 entities"* or *"Search my memories for hello"*. If the `mem0` tools appear and respond, you're all set.
 </Info>

 ## Codex Cloud
@@ -112,16 +106,13 @@ Lifecycle hooks that shell out to local scripts (Option A) are not applicable in

 | Component | Plugin Install | MCP Only |
 |-----------|:--------------:|:--------:|
-| Memory tools | `search_memories` | 9 CRUD tools |
-| Lifecycle hooks | Yes | No |
-| Native subagent memory lifecycle | Yes | No |
-| Memory skills | 6 | No |
+| MCP Server (9 memory tools) | Yes | Yes |
+| Lifecycle Hooks | Opt-in (see below) | No |
+| Mem0 SDK Skill | Yes | No |

-Mem0's Codex package does not bundle a named custom agent. If you define project or user agents under `.codex/agents/` or `~/.codex/agents/`, the full Mem0 plugin gives every native subagent the parent turn's retrieved memory context and records its completed result.
+## Available MCP Tools

-## Direct MCP tools
-
-Option B exposes the following hosted tools. The full plugin in Option A uses the focused `search_memories` tool and captures writes through lifecycle hooks.
+Once installed, the following tools are available in every Codex session:

 | Tool | Description |
 |------|-------------|
@@ -135,33 +126,46 @@ Option B exposes the following hosted tools. The full plugin in Option A uses th
 | `delete_entities` | Delete a user/agent/app/run entity and its memories |
 | `list_entities` | List users/agents/apps/runs stored in Mem0 |

-## Lifecycle hooks
+## Lifecycle Hooks

-Option A registers the hooks with the plugin. No separate hook installer or global `hooks.json` edit is required.
+Unlike Claude Code, Codex has no plugin-host mechanism for auto-wiring hooks from an installed plugin: it only reads hooks from `~/.codex/hooks.json` (or `<repo>/.codex/hooks.json`). Installing the plugin (Option A) does **not** turn hooks on by itself. To enable them, run the bundled installer once against your local clone:
+
+```bash
+python3 <path-to-your-clone>/integrations/mem0-plugin/scripts/install_codex_hooks.py
+```
+
+This merges Mem0's entries into `~/.codex/hooks.json` and is idempotent (safe to re-run after upgrading). It also requires the `codex_hooks` feature flag in `~/.codex/config.toml`:
+
+```toml
+[features]
+codex_hooks = true
+```
+
+The installer prints a reminder if the flag isn't set. Restart Codex after installing hooks or editing the config. To remove: `python3 .../install_codex_hooks.py --uninstall`.
+
+Once enabled, Mem0 hooks into Codex's lifecycle to automatically manage memory:

 | Hook | Event | What it does |
 |------|-------|-------------|
-| **Session start** | `SessionStart` | Initializes the project session and recovers pending capture |
-| **User prompt** | `UserPromptSubmit` | Records each prompt; searches on the first prompt when it has at least 20 characters |
-| **Post-tool** | `PostToolUse` | Records useful tool outcomes for the completed exchange |
-| **Subagent start** | `SubagentStart` | Reuses the parent turn's retrieved memory context in the child |
-| **Subagent stop** | `SubagentStop` | Records the child transcript path and completed result |
-| **Stop** | `Stop` | Captures completed work and starts a background flush when needed |
-| **Pre-compact** | `PreCompact` | Flushes pending capture before context compaction |
-| **Session end** | `SessionEnd` | Flushes any remaining capture in the background |
+| **Session start** | `SessionStart` | Loads prior memories and displays status banner |
+| **User prompt** | `UserPromptSubmit` | Searches relevant memories before each message |
+| **Pre-tool (3 handlers)** | `PreToolUse` | Blocks MEMORY.md writes; enforces `user_id`/`app_id` on mem0 tool calls; scans files being read for relevant memory context |
+| **Post-tool** | `PostToolUse` | Tracks stats, scans bash errors for related memories |
+| **Stop** | `Stop` | Stores a session summary at the end of every assistant turn (not just at session end) |
+| **Pre-compact** | `PreCompact` | Stores a summary before the context is compacted |

-What you type is stored as yours. Codex's captured responses are stored as the assistant's, so its suggestions never become your stated preferences.
+What you type is stored as yours. What Codex produces (session summaries and compaction summaries) is stored as the assistant's, so its suggestions never become your stated preferences.

 ## Example Workflow

 ```text
 # Task 1: Setting up a new service
-You: Create a REST API for the notifications service using Express and TypeScript. Prefer explicit error types over generic catch-all handlers.
+You: Create a REST API for the notifications service using Express and TypeScript.

 # Codex searches memories, finds your preferences from prior tasks.
 # Mem0 stores what you said as yours:
 #   - Your preference: "Prefers explicit error types over generic catch-all"
-# ...and completed work reported by Codex as the assistant's:
+# ...and what Codex did as the assistant's, in the session summary:
 #   - Decision: "Notifications service uses Express + TypeScript + Zod validation"
 #   - Convention: "All API routes follow /api/v1/{resource} pattern"

@@ -172,18 +176,12 @@ You: Add WebSocket support for real-time notification delivery.
 # Follows the same patterns established in the first task.
 ```

-## Search and capture
-
-The local `search_memories` tool accepts `query`, `top_k`, `category`, `scope` (`repo`, `dir`, or `mine`), and optional `run_id` with every scope. Use a known session ID to recall memories saved in that session; omit it to search across sessions. See [search scopes](/integrations/claude-code#search-scope) for the shared Python search contract, including legacy repository memory compatibility.
-
-Captured prompts and responses retain their full redacted text without a per-message character cutoff. Large extraction inputs are split across requests without dropping message text; recall output and tool-result previews have separate limits.
-
 ## Troubleshooting

 - **"Connection failed"**: Verify `MEM0_API_KEY` is set: `echo $MEM0_API_KEY`
 - **No tools appearing**: Restart your Codex session after installation
 - **Duplicate `mem0` MCP / "tool collision" errors**: You combined Option A with Option B. Remove the `[mcp_servers.mem0]` block from `~/.codex/config.toml`; the plugin registers it automatically
- **Hooks not firing**: Confirm you installed Option A and restart Codex. MCP-only installs (Option B) do not include hooks.
+- **Hooks not firing**: Hooks are opt-in and are not installed by the marketplace install itself. Run `scripts/install_codex_hooks.py` (see [Lifecycle Hooks](#lifecycle-hooks)), confirm `codex_hooks = true` is set under `[features]` in `~/.codex/config.toml`, and restart Codex. MCP-only installs (Option B) never include hooks

 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
@@ -1,13 +1,9 @@
 ---
 title: Cursor
-description: "Add persistent memory to Cursor with automatic capture, explicit recall, a search tool, and six memory skills."
+description: "Add persistent memory to Cursor with the Mem0 MCP server for context-aware coding."
 ---

-Add persistent memory to [**Cursor**](https://cursor.com) with the Mem0 plugin. Cursor captures completed work in the background, and its agent can search relevant project context in later sessions. You can also connect only the hosted MCP server when you do not need lifecycle capture.
-
-<Info>Current plugin version: `0.3.1`.</Info>
-
-Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+Add persistent memory to [**Cursor**](https://cursor.com) with the Mem0 MCP server. Your AI assistant forgets everything between sessions. Mem0 fixes that by connecting Cursor to Mem0's cloud memory layer via MCP so you can save and retrieve relevant context during coding sessions.

 ## Prerequisites

@@ -19,9 +15,7 @@ Before setting up Mem0 with Cursor, ensure you have:

 2. Cursor installed ([cursor.com](https://cursor.com))

-3. Python 3.10 or newer available as `python3`
-
-4. Your API key added to your shell profile (persists across sessions):
+3. Your API key added to your shell profile (persists across sessions):

 <CodeGroup>
 ```bash zsh
@@ -41,25 +35,13 @@ source ~/.bashrc

 ## Installation

-### Option A: Full Plugin (Recommended)
-
-Add the Mem0 marketplace:
-
-```bash
-cursor-agent plugin marketplace add https://github.com/mem0ai/mem0
-```
-
-Open Cursor's **Customize** page or run `/plugins`, select the **Mem0 Plugins** marketplace, and install **Mem0** at user or project scope. Enter your Mem0 API key when Cursor asks for the plugin configuration, then restart Cursor.
-
-The full plugin includes automatic capture, the `search_memories` recall tool, lifecycle hooks, and six memory skills.
-
-### Option B: One-Click Deeplink (MCP Only)
+### Option A: One-Click Deeplink (MCP Only)

 The fastest way to get started. Click the link below to install the Mem0 MCP server directly in Cursor:

 [Install Mem0 MCP in Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=mem0&config=eyJtY3BTZXJ2ZXJzIjp7Im1lbTAiOnsidXJsIjoiaHR0cHM6Ly9tY3AubWVtMC5haS9tY3AvIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiVG9rZW4gJHtlbnY6TUVNMF9BUElfS0VZfSJ9fX19)

-### Option C: npx (MCP Only)
+### Option B: npx (MCP Only)

 ```bash
 npx mcp-add \
@@ -69,7 +51,7 @@ npx mcp-add \
  --clients "cursor"
 ```

-### Option D: Manual Configuration (MCP Only)
+### Option C: Manual Configuration (MCP Only)

 Add the following to your `.cursor/mcp.json`:

@@ -91,19 +73,9 @@ Add the following to your `.cursor/mcp.json`:
 </Info>


-## What's included
+## Available MCP Tools

-| Component | Full plugin | MCP only |
-| --- | :---: | :---: |
-| Memory tools | `search_memories` | 9 CRUD tools |
-| Automatic capture | Yes | No |
-| Recall | `search_memories` | MCP search tools |
-| Lifecycle hooks | Yes | No |
-| Memory skills | 6 | No |
-
-## MCP-only tools
-
-Options B, C, and D expose the following hosted tools. The full plugin uses the focused `search_memories` tool and captures writes through lifecycle hooks.
+Once installed, the following tools are available in every Cursor session:

 | Tool | Description |
 |------|-------------|
@@ -117,29 +89,11 @@ Options B, C, and D expose the following hosted tools. The full plugin uses the
 | `delete_entities` | Delete a user/agent/app/run entity and its memories |
 | `list_entities` | List users/agents/apps/runs stored in Mem0 |

-## Lifecycle hooks
-
-The full plugin translates Cursor's native events into the shared Mem0 memory lifecycle:
-
-| Cursor event | What Mem0 does |
-| --- | --- |
-| `sessionStart` | Initializes the project session and recovers pending capture |
-| `beforeSubmitPrompt` | Observes the submitted prompt; recall stays tool-driven because this event cannot inject context |
-| `postToolUse` / `postToolUseFailure` | Records useful tool results and failures |
-| `afterAgentResponse` / `stop` | Captures the completed exchange |
-| `preCompact` / `sessionEnd` | Flushes pending capture in the background |
-
-<Note>
-  Cursor's `beforeSubmitPrompt` hook cannot add context to a prompt. Use `search_memories` to recall memories.
-</Note>
-
-The plugin does not register subagent start or stop hooks.
-
 ## Example Workflow

 ```text
 # Session 1: Debugging a performance issue
-You: The API endpoint /users is taking 3 seconds. Help me optimize it. Prefer query-level fixes over caching.
+You: The API endpoint /users is taking 3 seconds. Help me optimize it.

 # Cursor agent searches memories, proceeds with investigation.
 # Mem0 stores what you said as yours:
@@ -155,16 +109,10 @@ You: The /orders endpoint is also slow, same pattern as before.
 # Immediately checks for N+1 queries and missing indexes.
 ```

-## Search and capture
-
-The local `search_memories` tool accepts `query`, `top_k`, `category`, `scope` (`repo`, `dir`, or `mine`), and optional `run_id` with every scope. Use a known session ID to recall memories saved in that session; omit it to search across sessions. See [search scopes](/integrations/claude-code#search-scope) for the shared Python search contract, including legacy repository memory compatibility.
-
-Captured prompts and responses retain their full redacted text without a per-message character cutoff. Large extraction inputs are split across requests without dropping message text; recall output and tool-result previews have separate limits.
-
 ## Troubleshooting

 - **"Connection failed"**: Verify `MEM0_API_KEY` is set: `echo $MEM0_API_KEY`
- **Duplicate tools**: Do not combine the full plugin with an MCP-only option. Remove the standalone `mem0` MCP entry before installing the plugin.
+- **Duplicate tools**: If you had a previous MCP config for `mem0`, remove it before installing the plugin
 - **No tools appearing**: Go to Cursor Settings > MCP and verify the `mem0` server shows as connected

 <CardGroup cols={2}>
@@ -1,38 +1,24 @@
 ---
 title: DeepSeek Harness
-description: "Add persistent memory to DeepSeek Harness with automatic recall, automatic capture, and two native Mem0 tools."
+description: "Add persistent Mem0 memory to the DeepSeek Harness (Cordis) agent with two native tools: search and add."
 ---

-Add persistent memory to the [**DeepSeek Harness**](https://github.com/deepseek-ai/deepseek-harness) with `@mem0/deepseek-plugin`. The plugin recalls relevant context before a model request, captures completed turns, and provides explicit Mem0 tools when the agent needs them.
-
-<Info>Current package version: `0.3.0`.</Info>
-
-Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+Add persistent memory to the [**DeepSeek Harness**](https://github.com/deepseek-ai/deepseek-harness) with `@mem0/deepseek-plugin`. The Harness agent forgets everything between sessions. This plugin gives it two Mem0-backed tools so recall and writes persist across runs, sharing the same memory bank you already use from Claude Code, Codex, and other agents.

 ## Overview

-The plugin provides automatic memory plus two agent-callable tools:
+The plugin registers two agent-callable tools:

-| Capability | What it does |
+| Tool | Does |
 |---|---|
-| Automatic recall | Searches with the latest human prompt and adds unseen results to the model context |
-| Automatic capture | Stores the human and assistant messages from each completed turn |
 | `search_memory` | Recall facts from Mem0 relevant to a query |
 | `add_memory` | Store a fact in Mem0 for future sessions |

-Unlike file-based memory plugins, Mem0 is a managed backend: server-side extraction, semantic dedup, and conflict resolution, with memories reusable by integrations that use compatible user identities and search filters.
+Unlike file-based memory plugins, Mem0 is a managed backend: server-side extraction, semantic dedup, and conflict resolution, with the same memory reusable across every agent you connect.

 ## How it works

-A Cordis plugin is a module exporting `apply(ctx, config)`. This plugin waits for the Harness tool and system-prompt services, then uses their native extension points:
-
- `system-prompt/assemble` recalls memory before a model request.
- `session/event` captures only completed turns from the durable event stream.
- `ctx.tools.register(...)` exposes explicit search and add tools.
-
-Cordis removes the listeners and tools when the plugin unmounts. Memory failures are fail-open, so a Mem0 outage does not stop the agent from completing its normal work.
-
-DeepSeek Harness provides subagents through separate host-composition packages. This Mem0 package does not register a named Sidekick or claim child filesystem isolation. A Harness child uses Mem0 only when its own agent preset includes the Mem0 plugin.
+A Cordis plugin is a module exporting `apply(ctx, config)`. This one declares `inject = ['tools']` so it waits for the harness tool registry, then registers the two tools via `ctx.tools.register(...)`. When the plugin unmounts, the tools are removed automatically (Cordis revertible effects).

 ## Prerequisites

@@ -58,28 +44,19 @@ source ~/.bashrc

 ## Try it locally

-1. Build and pack the plugin:
+1. Build the plugin:
   ```sh
   cd integrations/deepseek-plugin
-   pnpm install --frozen-lockfile
+   pnpm install
   pnpm build
-   mkdir -p /tmp/mem0-deepseek-plugin
-   pnpm pack --pack-destination /tmp/mem0-deepseek-plugin
   ```

-2. Install it into a disposable Harness profile so Harness supplies its peer dependencies:
+2. Point the Harness at it. Copy `cordis.example.yml`, set the absolute path to `dist/index.js` and your `userId`, then load it:
   ```sh
-   DSH_HOME=/tmp/mem0-dsh-dev pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2 \
-     plugin --profile headless add /tmp/mem0-deepseek-plugin/mem0-deepseek-plugin-0.3.0.tgz
+   pnpm dsh web --patch ./integrations/deepseek-plugin/cordis.example.yml
   ```

-3. Copy `cordis.example.yml`, set its installed package path and your `userId`, then load it with the same profile:
-   ```sh
-   DSH_HOME=/tmp/mem0-dsh-dev pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2 \
-     web --patch ./integrations/deepseek-plugin/cordis.example.yml
-   ```
-
-4. Open the web UI and ask the agent to remember something, then recall it in a later turn.
+3. Open the web UI and ask the agent to remember something, then recall it in a later turn.

 The `cordis.yml` entry looks like this:

@@ -88,12 +65,10 @@ The `cordis.yml` entry looks like this:
 - name: "@deepseek-ai/dsh-tools"
 - insert:
    - id: mem0
-      name: "/tmp/mem0-dsh-dev/profiles/headless/node_modules/@mem0/deepseek-plugin/dist/index.js"
+      name: "/absolute/path/to/integrations/deepseek-plugin/dist/index.js"
      config:
        # apiKey is read from MEM0_API_KEY when omitted here.
        userId: "your-user-id"
-        autoRecall: true
-        autoCapture: true
        # host: "https://your-onprem.mem0.ai"   # optional: Platform on-prem / dedicated base URL
 ```

@@ -105,25 +80,10 @@ For a Mem0 Platform on-prem or dedicated deployment, point `config.host` at that
 |---|---|---|---|
 | `apiKey` | no | `$MEM0_API_KEY` | Mem0 platform API key |
 | `userId` | yes | | Default entity that owns the memories |
-| `allowUserOverride` | no | `false` | Permit model-selected access to a different user only in a trusted multi-user deployment |
 | `host` | no | `api.mem0.ai` | Platform base URL (on-prem / dedicated) |
-| `autoRecall` | no | `true` | Recall relevant memory before model requests |
-| `autoCapture` | no | `true` | Store completed human and assistant turns |

-Both tools also accept optional per-call `userId`, `agentId`, and `runId` params so a single install can partition memory by entity, agent, or session; `userId` defaults to the configured user, while `agentId` and `runId` are omitted unless supplied. Automatic recall and capture use the configured user without an agent, repository, or session filter. Automatic capture preserves full redacted user and assistant message text without a per-message character cutoff.
+Both tools also accept optional per-call `userId`, `agentId`, and `runId` params so a single install can partition memory by entity, agent, or session; when omitted they fall back to the configured `userId`.

 ## Telemetry

-Writes are tagged `source="DEEPSEEK_HARNESS"` so Mem0 can attribute usage to this integration. Usage events include operation names, durations, result counts, and coarse failure kinds. They are **not anonymous**: when an API key is configured they are sent under your Mem0 account email, the same way the SDK attributes its own. Queries, memory text, entity IDs, and API keys are never included. Set `MEM0_TELEMETRY=false` to opt out.
-
-<Note>
-  This plugin is a developer preview and tracks the evolving DeepSeek Harness plugin API.
-</Note>
-
-## Troubleshooting
-
- **`MISSING_CREDENTIAL` for `deepseek-official`**: Configure `DEEPSEEK_API_KEY` through Harness's Models page or export it in the shell that launches Harness.
- **`EMFILE: too many open files, watch` on macOS**: Launch Harness with `CHOKIDAR_USEPOLLING=1`.
- **Mem0 tools do not appear**: Run Harness with `--dump-config` and confirm the final composition contains the `mem0` row and the installed `dist/index.js` path.
-
-Per-call `userId` overrides are rejected unless the operator enables `allowUserOverride: true`. Automatic recall and capture always use the configured user.
+Writes are tagged `source="DEEPSEEK_HARNESS"` so Mem0's backend can attribute usage to this integration.
@@ -0,0 +1,64 @@
+---
+title: Eve
+description: "Use Mem0 as a first-class memory provider for Vercel Eve agents."
+---
+
+[Eve](https://eve.dev/docs/memory) is Vercel's agent framework. A memory provider sits in the agent loop: Eve recalls context before each turn, captures completed turns, and exposes provider tools. `@mem0/eve` is Mem0's implementation of that contract.
+
+This is not the Mem0 MCP connection. MCP gives the model tools it may or may not call. The memory provider runs automatically. The live MCP install is `eve add connection/mem0`.
+
+## Install
+
+```bash
+npm install @mem0/eve
+```
+
+`eve` is a peer dependency. Get an API key from the [Mem0 dashboard](https://app.mem0.ai/dashboard/api-keys).
+
+Create `agent/memory/mem0.ts`:
+
+```ts
+import { defineMemory } from "eve/memory";
+import { byPrincipal } from "eve/memory/scope";
+import { mem0Provider } from "@mem0/eve";
+
+export default defineMemory({
+  description: "Recall and manage durable context for the current user.",
+  provider: mem0Provider({
+    apiKey: process.env.MEM0_API_KEY!,
+  }),
+  scope: byPrincipal,
+});
+```
+
+`eve add memory/mem0` is not in Eve's catalog yet. After Mem0 is listed in the official registry, that command will create the same slot file.
+
+## How it works
+
+1. **Recall.** Before each turn and after compaction, Mem0 searches memories for the locked Eve scope and returns `{ id, content }` messages. Eve injects those as user-role messages attributed to the slot.
+2. **Capture.** After a successful turn, Mem0 adds the user messages from that turn and, when present, that turn's assistant reply. By default (`infer: true`) Mem0 extracts durable facts. Capture is deduplicated per `operationId` on a best-effort basis (an in-process gate plus a durable `metadata.operation_id` lookup); because that check and the write are not atomic and platform writes are asynchronous, a restart or concurrent worker can occasionally capture a turn twice.
+3. **Tools.** The model can call `search`, `remember`, and `forget`. Eve qualifies them as `mem0__search`, `mem0__remember`, and `mem0__forget` when the slot file is `mem0.ts`. `remember` returns `{ status: "saved" }` on a resolved write or `{ status: "queued" }` when the platform accepts it for asynchronous extraction.
+
+Eve owns namespace, scope, and when recall/capture run. Mem0 owns storage, ranking, and extraction. Search, capture, remember, and forget are partitioned by `memory.scope.key`. Forget deletes by id only after confirming the memory belongs to that key.
+
+## Options
+
+```ts
+mem0Provider({
+  apiKey: process.env.MEM0_API_KEY!,
+  topK: 5,
+  threshold: 0.1,
+  rerank: false,
+  infer: true,
+  autoSearch: { enabled: true },
+  capture: { enabled: true },
+});
+```
+
+See the [`@mem0/eve` README](https://github.com/mem0ai/mem0/tree/main/integrations/eve) for the full option list.
+
+## Related
+
+- [Eve memory docs](https://eve.dev/docs/memory)
+- [Build a memory provider](https://eve.dev/docs/memory/custom-provider)
+- [Vercel AI SDK](/integrations/vercel-ai-sdk) for `generateText` / `streamText` apps that are not Eve agents
--- a/Show More
+++ b/Show More
				`@@ -1 +0,0 @@`
				<svg height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Claude</title><path d="M4.709 15.955l4.72-2.647.08-.23-.08-.128H9.2l-.79-.048-2.698-.073-2.339-.097-2.266-.122-.571-.121L0 11.784l.055-.352.48-.321.686.06 1.52.103 2.278.158 1.652.097 2.449.255h.389l.055-.157-.134-.098-.103-.097-2.358-1.596-2.552-1.688-1.336-.972-.724-.491-.364-.462-.158-1.008.656-.722.881.06.225.061.893.686 1.908 1.476 2.491 1.833.365.304.145-.103.019-.073-.164-.274-1.355-2.446-1.446-2.49-.644-1.032-.17-.619a2.97 2.97 0 01-.104-.729L6.283.134 6.696 0l.996.134.42.364.62 1.414 1.002 2.229 1.555 3.03.456.898.243.832.091.255h.158V9.01l.128-1.706.237-2.095.23-2.695.08-.76.376-.91.747-.492.584.28.48.685-.067.444-.286 1.851-.559 2.903-.364 1.942h.212l.243-.242.985-1.306 1.652-2.064.73-.82.85-.904.547-.431h1.033l.76 1.129-.34 1.166-1.064 1.347-.881 1.142-1.264 1.7-.79 1.36.073.11.188-.02 2.856-.606 1.543-.28 1.841-.315.833.388.091.395-.328.807-1.969.486-2.309.462-3.439.813-.042.03.049.061 1.549.146.662.036h1.622l3.02.225.79.522.474.638-.079.485-1.215.62-1.64-.389-3.829-.91-1.312-.329h-.182v.11l1.093 1.068 2.006 1.81 2.509 2.33.127.578-.322.455-.34-.049-2.205-1.657-.851-.747-1.926-1.62h-.128v.17l.444.649 2.345 3.521.122 1.08-.17.353-.608.213-.668-.122-1.374-1.925-1.415-2.167-1.143-1.943-.14.08-.674 7.254-.316.37-.729.28-.607-.461-.322-.747.322-1.476.389-1.924.315-1.53.286-1.9.17-.632-.012-.042-.14.018-1.434 1.967-2.18 2.945-1.726 1.845-.414.164-.717-.37.067-.662.401-.589 2.388-3.036 1.44-1.882.93-1.086-.006-.158h-.055L4.132 18.56l-1.13.146-.487-.456.061-.746.231-.243 1.908-1.312-.006.006z" fill="#D97757" fill-rule="nonzero"></path></svg>
				`@@ -1 +0,0 @@`
				`<svg height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Claude Code</title><path clip-rule="evenodd" d="M20.998 10.949H24v3.102h-3v3.028h-1.487V20H18v-2.921h-1.487V20H15v-2.921H9V20H7.488v-2.921H6V20H4.487v-2.921H3V14.05H0V10.95h3V5h17.998v5.949zM6 10.949h1.488V8.102H6v2.847zm10.51 0H18V8.102h-1.49v2.847z" fill="#D97757" fill-rule="evenodd"></path></svg>`
				`@@ -1 +0,0 @@`
				<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>Cursor</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4.000 4.000) scale(0.66667)" fill="#ffffff" fill-rule="evenodd"><path d="M22.106 5.68L12.5.135a.998.998 0 00-.998 0L1.893 5.68a.84.84 0 00-.419.726v11.186c0 .3.16.577.42.727l9.607 5.547a.999.999 0 00.998 0l9.608-5.547a.84.84 0 00.42-.727V6.407a.84.84 0 00-.42-.726zm-.603 1.176L12.228 22.92c-.063.108-.228.064-.228-.061V12.34a.59.59 0 00-.295-.51l-9.11-5.26c-.107-.062-.063-.228.062-.228h18.55c.264 0 .428.286.296.514z"/></g></svg>
				`@@ -1 +0,0 @@`
				`<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><title>opencode</title><rect x="0.25" y="0.25" width="23.5" height="23.5" rx="5.5" fill="#161616" stroke="#3a3a3a" stroke-width="0.5"/><g transform="translate(4.000 4.000) scale(0.66667)" fill="#ffffff" fill-rule="evenodd"><path d="M16 6H8v12h8V6zm4 16H4V2h16v20z"/></g></svg>`