docs(skills): refresh mem0 skills against SDK 2.2.1 / TS 3.3.1 (#7548 )

fix(vector-store): stop writing service account private key to DEBUG logs in GoogleMatchingEngine (#7506 )
Co-authored-by: rupak-eng <rupak-eng@users.noreply.github.com>
2026-10-07 18:36:15 +05:30 · 2026-10-07 16:20:38 +05:30 · 2026-10-07 15:53:25 +05:30 · 2026-10-05 20:52:59 +05:30 · 2026-10-01 21:46:18 +05:30 · 2026-09-25 23:04:12 +05:30
611 changed files with 47540 additions and 24287 deletions
@@ -8,7 +8,7 @@
      "name": "mem0",
      "source": {
        "source": "local",
-        "path": "./integrations/mem0-plugin"
+        "path": "./integrations/codex-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.0"
+      "version": "0.3.3"
    }
  ]
 }
@@ -8,7 +8,7 @@
      "name": "mem0",
      "source": {
        "source": "local",
-        "path": "./integrations/mem0-plugin"
+        "path": "./integrations/codex-plugin"
      },
      "policy": {
        "installation": "AVAILABLE",
@@ -10,9 +10,9 @@
  "plugins": [
    {
      "name": "mem0",
-      "source": "./integrations/mem0-plugin",
-      "description": "Mem0 memory layer for AI applications. Add persistent memory, personalization, and semantic search.",
-      "version": "0.2.15"
+      "source": "./integrations/cursor-plugin",
+      "description": "Cross-session memory and token savings for coding agents.",
+      "version": "0.3.3"
    }
  ]
 }
@@ -18,9 +18,9 @@ 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 |
-| 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 |
+| 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 |
 | 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 |
@@ -0,0 +1,97 @@
+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
@@ -0,0 +1,42 @@
+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,8 +38,8 @@ jobs:
      cli_python: ${{ steps.filter.outputs.cli_python }}
      cli_node: ${{ steps.filter.outputs.cli_node }}
      openclaw: ${{ steps.filter.outputs.openclaw }}
-      mem0_plugin: ${{ steps.filter.outputs.mem0_plugin }}
-      claude_code_plugin: ${{ steps.filter.outputs.claude_code_plugin }}
+      agent_plugins_python: ${{ steps.filter.outputs.agent_plugins_python }}
+      agent_plugins_typescript: ${{ steps.filter.outputs.agent_plugins_typescript }}
      opencode_plugin: ${{ steps.filter.outputs.opencode_plugin }}
      pi_agent_plugin: ${{ steps.filter.outputs.pi_agent_plugin }}
      deepseek_plugin: ${{ steps.filter.outputs.deepseek_plugin }}
@@ -76,27 +76,43 @@ jobs:
              - '.github/workflows/ci-gate.yml'
            openclaw:
              - 'integrations/openclaw/**'
+              - 'integrations/agent-plugin-core/typescript/**'
              - '.github/workflows/openclaw-checks.yml'
              - '.github/workflows/ci-gate.yml'
-            mem0_plugin:
-              - 'integrations/mem0-plugin/**'
-              - '!integrations/mem0-plugin/.opencode-plugin/**'
-              - '.github/workflows/mem0-plugin-checks.yml'
-              - '.github/workflows/ci-gate.yml'
-            claude_code_plugin:
+            agent_plugins_python:
+              - 'integrations/agent-plugin-core/**'
+              - '!integrations/agent-plugin-core/typescript/**'
+              - 'integrations/mem0-agent-plugin/**'
              - 'integrations/claude-code-plugin/**'
-              - '.github/workflows/claude-code-plugin-checks.yml'
+              - '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'
+              - '.github/workflows/ci-gate.yml'
+            agent_plugins_typescript:
+              - 'integrations/agent-plugin-core/typescript/**'
+              - '.github/workflows/agent-plugins-typescript-checks.yml'
              - '.github/workflows/ci-gate.yml'
            opencode_plugin:
-              - 'integrations/mem0-plugin/.opencode-plugin/**'
+              - 'integrations/opencode-plugin/**'
+              - 'integrations/agent-plugin-core/typescript/**'
              - '.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:
@@ -160,18 +176,17 @@ jobs:
    uses: ./.github/workflows/openclaw-checks.yml
    secrets: inherit

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

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

  opencode-plugin:
@@ -248,8 +263,8 @@ jobs:
      - cli-python
      - cli-node
      - openclaw
-      - mem0-plugin
-      - claude-code-plugin
+      - agent-plugins-python
+      - agent-plugins-typescript
      - opencode-plugin
      - pi-agent-plugin
      - deepseek-plugin
@@ -1,46 +0,0 @@
-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,6 +8,7 @@ on:
    branches: [main]
    paths:
      - 'integrations/deepseek-plugin/**'
+      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/deepseek-plugin-checks.yml'
  workflow_call:

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

-      - 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)
+      - name: Verify package artifact
+        run: python3 integrations/agent-plugin-core/conformance/artifacts.py deepseek
@@ -1,58 +0,0 @@
-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,6 +8,7 @@ on:
    branches: [main]
    paths:
      - 'integrations/openclaw/**'
+      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/openclaw-checks.yml'
  workflow_call:

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

-      - 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)
+      - name: Verify package artifact
+        run: python3 integrations/agent-plugin-core/conformance/artifacts.py openclaw
@@ -25,7 +25,7 @@ jobs:
      id-token: write
    defaults:
      run:
-        working-directory: integrations/mem0-plugin/.opencode-plugin
+        working-directory: integrations/opencode-plugin
    steps:
      - uses: actions/checkout@v4
        with:
@@ -7,7 +7,8 @@ on:
  push:
    branches: [main]
    paths:
-      - 'integrations/mem0-plugin/.opencode-plugin/**'
+      - 'integrations/opencode-plugin/**'
+      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/opencode-plugin-checks.yml'
  workflow_call:

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

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

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

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

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

-      - 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)
+      - name: Verify package artifact
+        run: python3 integrations/agent-plugin-core/conformance/artifacts.py pi-agent
@@ -14,6 +14,10 @@ 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.1.0",
-      "description": "Persistent memory for Kimi Code. Remembers decisions, patterns, and preferences across sessions.",
+      "version": "0.3.3",
+      "description": "Cross-session memory and token savings for coding agents.",
      "homepage": "https://mem0.ai",
      "keywords": ["memory", "personalization", "mcp", "semantic-search"],
-      "source": "https://github.com/mem0ai/mem0/tree/main/integrations/mem0-plugin"
+      "source": "https://github.com/mem0ai/mem0/tree/main/integrations/kimi-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 `.opencode-plugin/`).
+- Use npm or yarn in TypeScript packages. This repo is pnpm-only (Bun in `integrations/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.13",
+  "version": "0.2.14",
  "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.0",
+    "vitest": "^4.1.11",
    "@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.0
-        version: 4.1.8(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))
+        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))

 packages:

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

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

-  '@vitest/mocker@4.1.8':
-    resolution: {integrity: sha512-LEiN/xe4OSIbKe9HQIp5OC24agGD9J5CnmMgsLohVVoOPWL9a2sBoR6VBx43jQZb7Kr1l4RCuyCJzcAa0+dojw==}
+  '@vitest/mocker@4.1.11':
+    resolution: {integrity: sha512-2XJVD55d1o5AZous5CCGKS74g/riOj9odEt2bQpCVZeblHyHdnMeFl4jl0XjU21stf4mbjUkew2eXQZt65g5CQ==}
    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.8':
-    resolution: {integrity: sha512-9GasEBxpZ1VYIpqHf/0+YGg121uSNwCKOJqIrTwWP/TB7DmFCiaBpNl3aPZzoLWfWkuqhbH8vJIVobZkvdo2cA==}
+  '@vitest/pretty-format@4.1.11':
+    resolution: {integrity: sha512-yiZzPbGTS9Sr/JpFl8zHrcIkAofNbFV6k21vIgQN/cY/oxZeXhJv5sc/MBJ5jFKWmWs+oJHw0UXLZjmf931+Vw==}

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

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

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

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

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

-  vitest@4.1.8:
-    resolution: {integrity: sha512-flY6ScbCIt9HThs+C5HS7jvGOB560DJtk/Z15IQROTA6zEy49Nh8T/dofWTQL+n3vswqn87sbJNiuqw1SDp5Ig==}
+  vitest@4.1.11:
+    resolution: {integrity: sha512-fhACrNXUidIbGSBr5FlbuBkO7VWC1ZyLl0DO4CU2DrQoAPxX84Ysxs+HeGQpii5lZWV1Q4gBZTTu49mF+A6Edw==}
    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.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
+      '@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
      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.8':
+  '@vitest/expect@4.1.11':
    dependencies:
      '@standard-schema/spec': 1.1.0
      '@types/chai': 5.2.3
-      '@vitest/spy': 4.1.8
-      '@vitest/utils': 4.1.8
+      '@vitest/spy': 4.1.11
+      '@vitest/utils': 4.1.11
      chai: 6.2.2
      tinyrainbow: 3.1.0

-  '@vitest/mocker@4.1.8(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))':
+  '@vitest/mocker@4.1.11(vite@6.4.3(@types/node@20.19.37)(tsx@4.21.0))':
    dependencies:
-      '@vitest/spy': 4.1.8
+      '@vitest/spy': 4.1.11
      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.8':
+  '@vitest/pretty-format@4.1.11':
    dependencies:
      tinyrainbow: 3.1.0

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

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

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

-  '@vitest/utils@4.1.8':
+  '@vitest/utils@4.1.11':
    dependencies:
-      '@vitest/pretty-format': 4.1.8
+      '@vitest/pretty-format': 4.1.11
      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.8(@types/node@20.19.37)(vite@6.4.3(@types/node@20.19.37)(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)):
    dependencies:
-      '@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
+      '@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
      es-module-lexer: 2.1.0
      expect-type: 1.3.0
      magic-string: 0.30.21
@@ -31,7 +31,8 @@ export class PlatformBackend implements Backend {
 		this.headers = {
 			Authorization: `Token ${config.apiKey}`,
 			"Content-Type": "application/json",
-			"X-Mem0-Source": "cli",
+			"X-Mem0-Source": "CLI",
+			"X-Mem0-Client": `mem0-cli-node/${CLI_VERSION}`,
 			"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.12"
+version = "0.2.13"
 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.12"
+__version__ = "0.2.13"
@@ -27,7 +27,8 @@ class PlatformBackend(Backend):
            headers={
                "Authorization": f"Token {config.api_key}",
                "Content-Type": "application/json",
-                "X-Mem0-Source": "cli",
+                "X-Mem0-Source": "CLI",
+                "X-Mem0-Client": f"mem0-cli-python/{__version__}",
                "X-Mem0-Client-Language": "python",
                "X-Mem0-Client-Version": __version__,
            },
@@ -1,5 +1,6 @@
 ---
-title: "Overview"
+title: "API Reference Overview"
+sidebarTitle: "Overview"
 icon: "terminal"
 iconType: "solid"
 description: "REST APIs for memory management, search, and entity operations"
@@ -10,7 +11,7 @@ description: "REST APIs for memory management, search, and entity operations"
 Mem0 provides a comprehensive REST API for integrating advanced memory capabilities into your applications. Create, search, update, and manage memories across users, agents, and custom entities with simple HTTP requests.

 <Info>
-**Quick start:** Get your API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=api-reference" rel="nofollow">Mem0 Dashboard</a> and make your first memory operation in minutes.
+**Quick start:** Get your API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=api-reference">Mem0 Dashboard</a> and make your first memory operation in minutes.
 </Info>

 ---
@@ -87,7 +88,7 @@ All API requests require authentication using Token-based authentication. Includ
 Authorization: Token <your-api-key>
 ```

-Get your API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=api-reference" rel="nofollow">Mem0 Dashboard</a>.
+Get your API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=api-reference">Mem0 Dashboard</a>.

 <Warning>
 **Keep your API key secure.** Never expose it in client-side code or public repositories. Use environment variables and server-side requests only.
@@ -1,5 +1,6 @@
 ---
-title: 'Delete Memory'
+title: "Delete Memory API Endpoint"
+sidebarTitle: "Delete Memory"
 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,5 +1,6 @@
 ---
-title: 'Update Memory'
+title: "Update Memory API Endpoint"
+sidebarTitle: "Update Memory"
 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,5 +1,6 @@
 ---
-title: 'Add Member'
+title: "Add Organization Member API Endpoint"
+sidebarTitle: "Add Member"
 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,5 +1,6 @@
 ---
-title: 'Get Members'
+title: "Get Organization Members API Endpoint"
+sidebarTitle: "Get Members"
 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/
 ---
@@ -0,0 +1,5 @@
+---
+title: 'Generate Profiles'
+description: "Start one generation: sample a few entities, or build one for a single entity."
+openapi: post /v2/profiles/jobs/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Get Generation Job'
+description: "Read the progress of a generation, and whether it finished."
+openapi: get /v2/profiles/jobs/{job_id}/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Get Profile Settings'
+description: "Retrieve the profile schema, custom instructions, and enabled flag for the current project."
+openapi: get /v2/profiles/settings/
+---
@@ -0,0 +1,5 @@
+---
+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/
+---
@@ -0,0 +1,5 @@
+---
+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,5 +1,6 @@
 ---
-title: 'Add Member'
+title: "Add Project Member API Endpoint"
+sidebarTitle: "Add Member"
 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,5 +1,6 @@
 ---
-title: 'Get Members'
+title: "Get Project Members API Endpoint"
+sidebarTitle: "Get Members"
 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,6 +7,36 @@ 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:**
@@ -174,7 +204,7 @@ mode: "wide"
 <Update label="2026-06-24" description="v2.0.8">

 **New Features:**
- **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))
+- **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))

 **Bug Fixes:**
 - **Core:** Guard against malformed `image_url` entries in `parse_vision_messages` to prevent crashes ([#5631](https://github.com/mem0ai/mem0/pull/5631))
@@ -964,7 +994,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 Opsearch Serverless
+- **AWS:** Added support for OpenSearch Serverless
 - **Examples:** Added ElizaOS Example

 **Improvements:**
@@ -1227,6 +1257,31 @@ 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:**
@@ -1543,7 +1598,7 @@ The largest provider release for the TypeScript OSS SDK so far: 17 new vector st
 **Improvements:**
 - **Telemetry:** Sample OSS hot-path events at 10% to reduce PostHog event volume ([#4771](https://github.com/mem0ai/mem0/pull/4771))

-See the [TypeScript SDK migration guide](https://docs.mem0.ai/migration/ts-v2-to-v3) for upgrade instructions.
+See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-v3) for upgrade instructions.

 </Update>

@@ -1864,6 +1919,13 @@ See the [TypeScript SDK migration guide](https://docs.mem0.ai/migration/ts-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:**
@@ -2060,6 +2122,29 @@ 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:**
@@ -2346,8 +2431,163 @@ 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:**
@@ -2428,6 +2668,43 @@ 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:**
@@ -2504,6 +2781,45 @@ 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))
@@ -2520,6 +2836,39 @@ 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:**
@@ -2790,6 +3139,40 @@ 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:**
@@ -2885,6 +3268,38 @@ 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:**
@@ -2912,6 +3327,13 @@ 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,5 +1,6 @@
 ---
-title: Configurations
+title: "Embedder Configuration Reference"
+sidebarTitle: "Configurations"
 description: "Reference for embedder configuration options in Mem0, including provider selection and model settings."
 ---

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

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

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

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

@@ -1,5 +1,6 @@
 ---
-title: "LM Studio"
+title: "LM Studio as Embedding Provider"
+sidebarTitle: "LM Studio"
 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,5 +1,6 @@
 ---
-title: "Ollama"
+title: "Ollama as Embedding Provider"
+sidebarTitle: "Ollama"
 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,5 +1,6 @@
 ---
-title: OpenAI
+title: "OpenAI as Embedding Provider"
+sidebarTitle: "OpenAI"
 description: "Configure OpenAI as an embedding provider in Mem0 using models like text-embedding-3-large for vector generation."
 ---

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

@@ -10,7 +11,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,5 +1,6 @@
 ---
-title: Overview
+title: "Embedding Providers Overview"
+sidebarTitle: Overview
 description: "Overview of all supported embedding model providers in Mem0, including OpenAI, Azure, Ollama, and more."
 ---

@@ -15,15 +16,15 @@ See the list of supported embedders below.

 <CardGroup cols={4}>
  <Card title="OpenAI" icon="/images/provider-icons/openai.svg" href="/components/embedders/models/openai"></Card>
-  <Card title="Azure OpenAI" icon="/images/provider-icons/azure-color.svg" href="/components/embedders/models/azure_openai"></Card>
+  <Card title="Azure OpenAI" icon="/images/provider-icons/azure-color.svg" href="/components/embedders/models/azure-openai"></Card>
  <Card title="Ollama" icon="/images/provider-icons/ollama.svg" href="/components/embedders/models/ollama"></Card>
  <Card title="Hugging Face" icon="/images/provider-icons/huggingface.svg" href="/components/embedders/models/huggingface"></Card>
-  <Card title="Google AI" icon="/images/provider-icons/google-color.svg" href="/components/embedders/models/google_AI"></Card>
+  <Card title="Google AI" icon="/images/provider-icons/google-color.svg" href="/components/embedders/models/google-ai"></Card>
  <Card title="Vertex AI" icon="/images/provider-icons/vertexai.svg" href="/components/embedders/models/vertexai"></Card>
  <Card title="Together" icon="/images/provider-icons/together-color.svg" href="/components/embedders/models/together"></Card>
  <Card title="LM Studio" icon="/images/provider-icons/lmstudio.svg" href="/components/embedders/models/lmstudio"></Card>
  <Card title="Langchain" icon="/images/provider-icons/langchain-color.svg" href="/components/embedders/models/langchain"></Card>
-  <Card title="AWS Bedrock" icon="/images/provider-icons/bedrock-color.svg" href="/components/embedders/models/aws_bedrock"></Card>
+  <Card title="AWS Bedrock" icon="/images/provider-icons/bedrock-color.svg" href="/components/embedders/models/aws-bedrock"></Card>
  <Card title="FastEmbed" icon="/images/provider-icons/qdrant.svg" href="/components/embedders/models/fastembed"></Card>
 </CardGroup>

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

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

@@ -1,5 +1,6 @@
 ---
-title: Azure OpenAI
+title: "Azure OpenAI as LLM Provider"
+sidebarTitle: "Azure OpenAI"
 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,5 +1,6 @@
 ---
-title: Google AI
+title: "Google AI as LLM Provider"
+sidebarTitle: "Google AI"
 description: "Configure Google Gemini as an LLM provider in Mem0 using the google.genai SDK and GOOGLE_API_KEY variable."
 ---

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

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

@@ -76,7 +77,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,5 +1,6 @@
 ---
-title: Ollama
+title: "Ollama as LLM Provider"
+sidebarTitle: "Ollama"
 description: "Configure Ollama as an LLM provider in Mem0 for running local language models with tool-calling support."
 ---

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

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

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

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

@@ -22,14 +23,14 @@ See the list of supported LLMs below.
 <CardGroup cols={4}>
  <Card title="OpenAI" icon="/images/provider-icons/openai.svg" href="/components/llms/models/openai" />
  <Card title="Ollama" icon="/images/provider-icons/ollama.svg" href="/components/llms/models/ollama" />
-  <Card title="Azure OpenAI" icon="/images/provider-icons/azure-color.svg" href="/components/llms/models/azure_openai" />
+  <Card title="Azure OpenAI" icon="/images/provider-icons/azure-color.svg" href="/components/llms/models/azure-openai" />
  <Card title="Anthropic" icon="/images/provider-icons/anthropic.svg" href="/components/llms/models/anthropic" />
  <Card title="Together" icon="/images/provider-icons/together-color.svg" href="/components/llms/models/together" />
  <Card title="Groq" icon="/images/provider-icons/groq.svg" href="/components/llms/models/groq" />
  <Card title="Litellm" icon="shuffle" href="/components/llms/models/litellm" />
-  <Card title="Mistral AI" icon="/images/provider-icons/mistral-color.svg" href="/components/llms/models/mistral_AI" />
-  <Card title="Google AI" icon="/images/provider-icons/google-color.svg" href="/components/llms/models/google_AI" />
-  <Card title="AWS bedrock" icon="/images/provider-icons/bedrock-color.svg" href="/components/llms/models/aws_bedrock" />
+  <Card title="Mistral AI" icon="/images/provider-icons/mistral-color.svg" href="/components/llms/models/mistral-ai" />
+  <Card title="Google AI" icon="/images/provider-icons/google-color.svg" href="/components/llms/models/google-ai" />
+  <Card title="AWS bedrock" icon="/images/provider-icons/bedrock-color.svg" href="/components/llms/models/aws-bedrock" />
  <Card title="DeepSeek" icon="/images/provider-icons/deepseek-color.svg" href="/components/llms/models/deepseek" />
  <Card title="MiniMax" icon="/images/provider-icons/minimax-color.svg" href="/components/llms/models/minimax" />
  <Card title="xAI" icon="/images/provider-icons/xai.svg" href="/components/llms/models/xAI" />
@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Reranker Providers Overview"
+sidebarTitle: "Overview"
 description: 'Pick the right reranker path to boost Mem0 search relevance.'
 ---

@@ -13,10 +14,10 @@ Reranking trades extra latency for better precision. Start once you have baselin

 <CardGroup cols={3}>
  <Card title="Cohere" icon="/images/provider-icons/cohere.svg" href="/components/rerankers/models/cohere" />
-  <Card title="Sentence Transformers" icon="vector-square" href="/components/rerankers/models/sentence_transformer" />
+  <Card title="Sentence Transformers" icon="vector-square" href="/components/rerankers/models/sentence-transformer" />
  <Card title="Hugging Face" icon="/images/provider-icons/huggingface.svg" href="/components/rerankers/models/huggingface" />
-  <Card title="LLM Reranker" icon="wand-magic-sparkles" href="/components/rerankers/models/llm_reranker" />
-  <Card title="Zero Entropy" icon="/images/provider-icons/zeroentropy.svg" href="/components/rerankers/models/zero_entropy" />
+  <Card title="LLM Reranker" icon="wand-magic-sparkles" href="/components/rerankers/models/llm-reranker" />
+  <Card title="Zero Entropy" icon="/images/provider-icons/zeroentropy.svg" href="/components/rerankers/models/zero-entropy" />
 </CardGroup>

 <Note>
@@ -54,13 +55,13 @@ All five rerankers are available in both the Python and the [TypeScript](/open-s
    title="Zero Entropy Guide"
    description="Adopt the managed neural reranker for production workloads."
    icon="sparkles"
-    href="/components/rerankers/models/zero_entropy"
+    href="/components/rerankers/models/zero-entropy"
  />
  <Card
    title="Sentence Transformers"
    description="Keep reranking on-device with cross-encoder models."
    icon="microchip"
-    href="/components/rerankers/models/sentence_transformer"
+    href="/components/rerankers/models/sentence-transformer"
  />
 </CardGroup>

@@ -1,5 +1,6 @@
 ---
-title: Configurations
+title: "Vector Store Configuration Reference"
+sidebarTitle: "Configurations"
 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 is provided, it will be used for authentication over an Azure Identity </Note>
+<Note> If an API key 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,5 +1,6 @@
 ---
-title: LangChain
+title: "LangChain as Vector Store Provider"
+sidebarTitle: "LangChain"
 description: "Use LangChain as a unified vector store provider in Mem0 to access multiple vector databases through one interface."
 ---

@@ -5,6 +5,12 @@ 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,6 +94,7 @@ 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         | `""`          |
+| `collection_name`   | The default namespace used         | `"mem0"`      |
 | `enable_embeddings` | Whether to use Upstash embeddings  | `False`       |

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

@@ -28,12 +29,12 @@ See the list of supported vector databases below.
  <Card title="Elasticsearch" icon="/images/provider-icons/elasticsearch.svg" href="/components/vectordbs/dbs/elasticsearch"></Card>
  <Card title="OpenSearch" icon="/images/provider-icons/opensearch.svg" href="/components/vectordbs/dbs/opensearch"></Card>
  <Card title="Supabase" icon="/images/provider-icons/supabase.svg" href="/components/vectordbs/dbs/supabase"></Card>
-  <Card title="Vertex AI" icon="/images/provider-icons/vertexai.svg" href="/components/vectordbs/dbs/vertex_ai"></Card>
+  <Card title="Vertex AI" icon="/images/provider-icons/vertexai.svg" href="/components/vectordbs/dbs/vertex-ai"></Card>
  <Card title="Weaviate" icon="circle-nodes" href="/components/vectordbs/dbs/weaviate"></Card>
  <Card title="FAISS" icon="layer-group" href="/components/vectordbs/dbs/faiss"></Card>
  <Card title="LangChain" icon="/images/provider-icons/langchain-color.svg" href="/components/vectordbs/dbs/langchain"></Card>
-  <Card title="Amazon S3 Vectors" icon="/images/provider-icons/aws-color.svg" href="/components/vectordbs/dbs/s3_vectors"></Card>
-  <Card title="Neptune Analytics" icon="/images/provider-icons/aws-color.svg" href="/components/vectordbs/dbs/neptune_analytics"></Card>
+  <Card title="Amazon S3 Vectors" icon="/images/provider-icons/aws-color.svg" href="/components/vectordbs/dbs/s3-vectors"></Card>
+  <Card title="Neptune Analytics" icon="/images/provider-icons/aws-color.svg" href="/components/vectordbs/dbs/neptune-analytics"></Card>
  <Card title="Databricks" icon="/images/provider-icons/databricks.svg" href="/components/vectordbs/dbs/databricks"></Card>
  <Card title="Turbopuffer" icon="/images/provider-icons/turbopuffer.svg" href="/components/vectordbs/dbs/turbopuffer"></Card>
 </CardGroup>
@@ -38,7 +38,7 @@ Navigate to the `docs/` directory (where `docs.json` is located) and start the d
 mintlify dev
 ```

-The documentation website will be available at: [http://localhost:3000](http://localhost:3000).
+The documentation website will be available at: `http://localhost:3000`.

 ---

@@ -48,7 +48,7 @@ Before you begin, follow these steps to set up the demo application:
   OPENAI_API_KEY=your_openai_api_key
   MEM0_API_KEY=your_mem0_api_key
   ```
-   You can obtain your `MEM0_API_KEY` by signing up at <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-companions-quickstart" rel="nofollow">Mem0 API Dashboard</a>.
+   You can obtain your `MEM0_API_KEY` by signing up at <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-companions-quickstart">Mem0 API Dashboard</a>.

 5. Start the development server:
   ```bash
@@ -21,7 +21,7 @@ from mem0 import MemoryClient
 client = MemoryClient(api_key="m0-...")
 ```

-Grab an API key from the <a href="https://app.mem0.ai/?utm_source=oss&utm_medium=cookbook-entity-partitioning" rel="nofollow">Mem0 dashboard</a> to get started.
+Grab an API key from the <a href="https://app.mem0.ai/?utm_source=oss&utm_medium=cookbook-entity-partitioning">Mem0 dashboard</a> to get started.

 ## Store and Retrieve Scoped Memories

@@ -23,7 +23,7 @@ client = MemoryClient(api_key="your-api-key")
 ```

 <Note>
-Your API key needs export permissions to download memory data. Check your project settings on the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-exporting-memories" rel="nofollow">dashboard</a> if export operations fail with authentication errors.
+Your API key needs export permissions to download memory data. Check your project settings on the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-exporting-memories">dashboard</a> if export operations fail with authentication errors.
 </Note>

 Let's add some sample memories to work with:
@@ -59,7 +59,7 @@ GEMINI_API_KEY=your-gemini-api-key-here
 ```

 <Note>
-Ensure you have your Mem0 API key from the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-gemini-3" rel="nofollow">Mem0 Dashboard</a> and your Gemini API key from the [Google AI Studio](https://ai.studio/app/api-keys).
+Ensure you have your Mem0 API key from the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-gemini-3">Mem0 Dashboard</a> and your Gemini API key from the [Google AI Studio](https://ai.studio/app/api-keys).
 </Note>

 ## Gemini Memory Agent
@@ -44,7 +44,7 @@ Set up your environment variables:
 - `MEM0_API_KEY`: Your Mem0 Platform API key
 - `OPENAI_API_KEY`: Your OpenAI API key

-You can obtain your Mem0 Platform API key from the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-llamaindex-multiagent" rel="nofollow">Mem0 Platform</a>.
+You can obtain your Mem0 Platform API key from the <a href="https://app.mem0.ai?utm_source=oss&utm_medium=cookbook-llamaindex-multiagent">Mem0 Platform</a>.

 ## Complete Implementation

@@ -360,7 +360,7 @@ Based on our previous session, I remember we covered Vision Language Models and
 ## Help & Resources

 - [LlamaIndex Agent Workflows](https://docs.llamaindex.ai/en/stable/use_cases/agents/)
- <a href="https://app.mem0.ai/?utm_source=oss&utm_medium=cookbook-llamaindex-multiagent" rel="nofollow">Mem0 Platform</a>
+- <a href="https://app.mem0.ai/?utm_source=oss&utm_medium=cookbook-llamaindex-multiagent">Mem0 Platform</a>

 ---

@@ -28,7 +28,7 @@ os.environ["OPENAI_API_KEY"] = "<your-openai-api-key>"
 llm = OpenAI(model="gpt-5-mini")
 ```

-Initialize the Mem0 client. You can find your API key <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-llamaindex-react" rel="nofollow">here</a>. Read about Mem0 [Open Source](https://docs.mem0.ai/open-source/overview).
+Initialize the Mem0 client. You can find your API key <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-llamaindex-react">here</a>. Read about Mem0 [Open Source](https://docs.mem0.ai/open-source/overview).
 ```python
 os.environ["MEM0_API_KEY"] = "<your-mem0-api-key>"

@@ -226,7 +226,7 @@ context = Mem0Context(user_id="user123")
 ## Resources

 - [Mem0 Documentation](https://docs.mem0.ai/introduction)
- <a href="https://app.mem0.ai/dashboard?utm_source=oss&utm_medium=cookbook-agents-sdk-tool" rel="nofollow">Mem0 Dashboard</a>
+- <a href="https://app.mem0.ai/dashboard?utm_source=oss&utm_medium=cookbook-agents-sdk-tool">Mem0 Dashboard</a>
 - [API Reference](https://docs.mem0.ai/api-reference)

 ---
@@ -38,8 +38,8 @@ print(os.environ['AWS_SECRET_ACCESS_KEY'])
 ## Configuration and Usage

 This sets up Mem0 with:
- [AWS Bedrock for LLM](https://docs.mem0.ai/components/llms/models/aws_bedrock)
- [AWS Bedrock for embeddings](https://docs.mem0.ai/components/embedders/models/aws_bedrock#aws-bedrock)
+- [AWS Bedrock for LLM](https://docs.mem0.ai/components/llms/models/aws-bedrock)
+- [AWS Bedrock for embeddings](https://docs.mem0.ai/components/embedders/models/aws-bedrock#aws-bedrock)
 - [OpenSearch as the vector store](https://docs.mem0.ai/components/vectordbs/dbs/opensearch)

 ```python
@@ -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
@@ -26,7 +26,7 @@ MEM0_API_KEY=your_mem0_api_key
 OPENAI_API_KEY=your_openai_api_key
 ```

-Get your Mem0 API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-openai-tool-calls" rel="nofollow">Mem0 Dashboard</a>.
+Get your Mem0 API key from the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=cookbook-openai-tool-calls">Mem0 Dashboard</a>.

 ### Configuration

@@ -283,7 +283,7 @@ run().catch(console.error);
 ## Resources

 - [Mem0 Documentation](https://docs.mem0.ai/introduction)
- <a href="https://app.mem0.ai/dashboard?utm_source=oss&utm_medium=cookbook-openai-tool-calls" rel="nofollow">Mem0 Dashboard</a>
+- <a href="https://app.mem0.ai/dashboard?utm_source=oss&utm_medium=cookbook-openai-tool-calls">Mem0 Dashboard</a>
 - [API Reference](https://docs.mem0.ai/api-reference)
 - [OpenAI Documentation](https://platform.openai.com/docs)

@@ -0,0 +1,388 @@
+---
+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,5 +1,6 @@
 ---
-title: Overview
+title: "Cookbooks and Tutorials"
+sidebarTitle: "Overview"
 description: "Browse cookbook examples and tutorials for building AI applications with Mem0, from companion chatbots to AI agents."
 ---

@@ -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="Memory types" icon="brain" href="/core-concepts/memory-types">
-    Choose the right scope for user, agent, run, and session memory.
+  <Card title="Entity scoping" icon="brain" href="/platform/features/entity-scoped-memory">
+    Organize Platform memories by user, agent, app, and run.
  </Card>
  <Card title="Memory operations" icon="database" href="/core-concepts/memory-operations/add">
    Add, search, update, and delete memories from your app.
@@ -66,7 +66,7 @@ The combined score outperformed every individual signal across every category te

 ### LoCoMo

-[LoCoMo](https://github.com/snap-stanford/locomo) tests single-hop, multi-hop, open-domain, and temporal memory recall across conversational sessions.
+[LoCoMo](https://github.com/snap-research/locomo) tests single-hop, multi-hop, open-domain, and temporal memory recall across conversational sessions.

 | Category | Score |
 |---|---|
@@ -1,5 +1,6 @@
 ---
-title: Delete Memory
+title: "Delete Memory Operation"
+sidebarTitle: "Delete Memory"
 description: Remove memories from Mem0 either individually, in bulk, or via filters.
 icon: "trash"
 iconType: "solid"
@@ -1,5 +1,6 @@
 ---
-title: Update Memory
+title: "Update Memory Operation"
+sidebarTitle: "Update Memory"
 description: Modify an existing memory by updating its content or metadata.
 icon: "pen-to-square"
 iconType: "solid"
@@ -1,118 +0,0 @@
---
-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,6 +41,7 @@
                    "pages": [
                      "platform/quickstart",
                      "platform/overview",
+                      "platform/copilot",
                      "platform/agent-signup",
                      "vibecoding",
                      "platform/cli",
@@ -53,7 +54,6 @@
                    "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,6 +71,7 @@
                        "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",
@@ -152,7 +153,7 @@
                      "open-source/features/multimodal-support",
                      "open-source/features/custom-instructions",
                      "open-source/features/rest-api",
-                      "open-source/features/openai_compatibility",
+                      "open-source/features/openai-compatibility",
                      "platform/features/memory-expiration"
                    ]
                  },
@@ -173,14 +174,14 @@
                            "pages": [
                              "components/llms/models/openai",
                              "components/llms/models/anthropic",
-                              "components/llms/models/azure_openai",
+                              "components/llms/models/azure-openai",
                              "components/llms/models/ollama",
                              "components/llms/models/together",
                              "components/llms/models/groq",
                              "components/llms/models/litellm",
-                              "components/llms/models/mistral_AI",
-                              "components/llms/models/google_AI",
-                              "components/llms/models/aws_bedrock",
+                              "components/llms/models/mistral-ai",
+                              "components/llms/models/google-ai",
+                              "components/llms/models/aws-bedrock",
                              "components/llms/models/deepseek",
                              "components/llms/models/minimax",
                              "components/llms/models/xAI",
@@ -210,7 +211,7 @@
                              "components/vectordbs/dbs/mongodb",
                              "components/vectordbs/dbs/oracledb",
                              "components/vectordbs/dbs/azure",
-                              "components/vectordbs/dbs/azure_mysql",
+                              "components/vectordbs/dbs/azure-mysql",
                              "components/vectordbs/dbs/redis",
                              "components/vectordbs/dbs/valkey",
                              "components/vectordbs/dbs/elasticsearch",
@@ -218,16 +219,16 @@
                              "components/vectordbs/dbs/supabase",
                              "components/vectordbs/dbs/upstash-vector",
                              "components/vectordbs/dbs/vectorize",
-                              "components/vectordbs/dbs/vertex_ai",
+                              "components/vectordbs/dbs/vertex-ai",
                              "components/vectordbs/dbs/weaviate",
                              "components/vectordbs/dbs/faiss",
                              "components/vectordbs/dbs/langchain",
                              "components/vectordbs/dbs/baidu",
                              "components/vectordbs/dbs/cassandra",
-                              "components/vectordbs/dbs/s3_vectors",
+                              "components/vectordbs/dbs/s3-vectors",
                              "components/vectordbs/dbs/databricks",
                              "components/vectordbs/dbs/neon",
-                              "components/vectordbs/dbs/neptune_analytics",
+                              "components/vectordbs/dbs/neptune-analytics",
                              "components/vectordbs/dbs/turbopuffer"
                            ]
                          }
@@ -244,15 +245,15 @@
                            "icon": "list",
                            "pages": [
                              "components/embedders/models/openai",
-                              "components/embedders/models/azure_openai",
+                              "components/embedders/models/azure-openai",
                              "components/embedders/models/ollama",
                              "components/embedders/models/huggingface",
                              "components/embedders/models/vertexai",
-                              "components/embedders/models/google_AI",
+                              "components/embedders/models/google-ai",
                              "components/embedders/models/lmstudio",
                              "components/embedders/models/together",
                              "components/embedders/models/langchain",
-                              "components/embedders/models/aws_bedrock",
+                              "components/embedders/models/aws-bedrock",
                              "components/embedders/models/fastembed"
                            ]
                          }
@@ -271,10 +272,10 @@
                            "icon": "list",
                            "pages": [
                              "components/rerankers/models/cohere",
-                              "components/rerankers/models/sentence_transformer",
+                              "components/rerankers/models/sentence-transformer",
                              "components/rerankers/models/huggingface",
-                              "components/rerankers/models/llm_reranker",
-                              "components/rerankers/models/zero_entropy"
+                              "components/rerankers/models/llm-reranker",
+                              "components/rerankers/models/zero-entropy"
                            ]
                          }
                        ]
@@ -373,6 +374,7 @@
                      "integrations/claude-ai",
                      "integrations/cursor",
                      "integrations/codex",
+                      "integrations/kimi",
                      "integrations/opencode",
                      "integrations/antigravity"
                    ]
@@ -442,7 +444,8 @@
                      "cookbooks/integrations/mastra-agent",
                      "cookbooks/integrations/healthcare-google-adk",
                      "cookbooks/integrations/aws-bedrock",
-                      "cookbooks/integrations/tavily-search"
+                      "cookbooks/integrations/tavily-search",
+                      "cookbooks/integrations/supabase"
                    ]
                  },
                  {
@@ -510,6 +513,17 @@
                      "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",
@@ -642,7 +656,7 @@
    },
    {
      "source": "/components/rerankers/models/llm",
-      "destination": "/components/rerankers/models/llm_reranker"
+      "destination": "/components/rerankers/models/llm-reranker"
    },
    {
      "source": "/migration/breaking-changes",
@@ -818,7 +832,7 @@
    },
    {
      "source": "/components/llms/models/azure_openai_structured",
-      "destination": "/components/llms/models/azure_openai"
+      "destination": "/components/llms/models/azure-openai"
    },
    {
      "source": "/components/llms/models/openai_structured",
@@ -834,7 +848,7 @@
    },
    {
      "source": "/components/vectordbs/dbs/vertex_ai_vector_search",
-      "destination": "/components/vectordbs/dbs/vertex_ai"
+      "destination": "/components/vectordbs/dbs/vertex-ai"
    },
    {
      "source": "/platform/features/selective-memory",
@@ -1018,7 +1032,11 @@
    },
    {
      "source": "/concepts/memory-scoring",
-      "destination": "/core-concepts/memory-types"
+      "destination": "/core-concepts/how-it-works"
+    },
+    {
+      "source": "/core-concepts/memory-types",
+      "destination": "/core-concepts/how-it-works"
    },
    {
      "source": "/cookbooks/research-copilot",
@@ -1082,7 +1100,7 @@
    },
    {
      "source": "/components/embedders/models/google_ai",
-      "destination": "/components/embedders/models/google_AI"
+      "destination": "/components/embedders/models/google-ai"
    },
    {
      "source": "/components/embedders/models/lm_studio",
@@ -1094,24 +1112,16 @@
    },
    {
      "source": "/components/llms/models/google_ai",
-      "destination": "/components/llms/models/google_AI"
+      "destination": "/components/llms/models/google-ai"
    },
    {
      "source": "/components/llms/models/mistral_ai",
-      "destination": "/components/llms/models/mistral_AI"
+      "destination": "/components/llms/models/mistral-ai"
    },
    {
      "source": "/components/llms/models/lm_studio",
      "destination": "/components/llms/models/lmstudio"
    },
-    {
-      "source": "/components/vectordbs/dbs/neptune-analytics",
-      "destination": "/components/vectordbs/dbs/neptune_analytics"
-    },
-    {
-      "source": "/components/vectordbs/dbs/s3-vectors",
-      "destination": "/components/vectordbs/dbs/s3_vectors"
-    },
    {
      "source": "/open-source/python_quickstart",
      "destination": "/open-source/python-quickstart"
@@ -1511,6 +1521,66 @@
    {
      "source": "/openmemory/mcp/introduction",
      "destination": "https://mem0.ai/blog/introducing-openmemory-mcp"
+    },
+    {
+      "source": "/components/embedders/models/aws_bedrock",
+      "destination": "/components/embedders/models/aws-bedrock"
+    },
+    {
+      "source": "/components/embedders/models/azure_openai",
+      "destination": "/components/embedders/models/azure-openai"
+    },
+    {
+      "source": "/components/embedders/models/google_AI",
+      "destination": "/components/embedders/models/google-ai"
+    },
+    {
+      "source": "/components/llms/models/aws_bedrock",
+      "destination": "/components/llms/models/aws-bedrock"
+    },
+    {
+      "source": "/components/llms/models/azure_openai",
+      "destination": "/components/llms/models/azure-openai"
+    },
+    {
+      "source": "/components/llms/models/google_AI",
+      "destination": "/components/llms/models/google-ai"
+    },
+    {
+      "source": "/components/llms/models/mistral_AI",
+      "destination": "/components/llms/models/mistral-ai"
+    },
+    {
+      "source": "/components/rerankers/models/llm_reranker",
+      "destination": "/components/rerankers/models/llm-reranker"
+    },
+    {
+      "source": "/components/rerankers/models/sentence_transformer",
+      "destination": "/components/rerankers/models/sentence-transformer"
+    },
+    {
+      "source": "/components/rerankers/models/zero_entropy",
+      "destination": "/components/rerankers/models/zero-entropy"
+    },
+    {
+      "source": "/components/vectordbs/dbs/azure_mysql",
+      "destination": "/components/vectordbs/dbs/azure-mysql"
+    },
+    {
+      "source": "/components/vectordbs/dbs/neptune_analytics",
+      "destination": "/components/vectordbs/dbs/neptune-analytics"
+    },
+    {
+      "source": "/components/vectordbs/dbs/s3_vectors",
+      "destination": "/components/vectordbs/dbs/s3-vectors"
+    },
+    {
+      "source": "/components/vectordbs/dbs/vertex_ai",
+      "destination": "/components/vectordbs/dbs/vertex-ai"
+    },
+    {
+      "source": "/open-source/features/openai_compatibility",
+      "destination": "/open-source/features/openai-compatibility"
    }
  ]
 }
@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Integrations Overview"
+sidebarTitle: "Overview"
 description: "Overview of Mem0 integrations with popular AI frameworks and tools for persistent memory and context management."
 ---

@@ -15,6 +16,8 @@ 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
@@ -22,9 +22,9 @@ pip install mem0ai agentops python-dotenv
 ```

 2. Valid API keys:
-   - [AgentOps API Key](https://app.agentops.ai/dashboard/api-keys)
+   - [AgentOps API Key](https://app.agentops.ai/projects)
   - OpenAI API Key (for LLM operations)
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-agentops" rel="nofollow">Mem0 API Key</a> (optional, for cloud operations)
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-agentops">Mem0 API Key</a> (optional, for cloud operations)

 ## Basic Integration Example

@@ -23,7 +23,7 @@ pip install agno mem0ai python-dotenv
 ```

 2. Valid API keys:
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-agno" rel="nofollow">Mem0 API Key</a>
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-agno">Mem0 API Key</a>
   - OpenAI API Key (for the agent model)

 ## Quick Integration (Using `Mem0Tools`)
@@ -1,16 +1,22 @@
 ---
 title: Antigravity
-description: "Add persistent memory to Google Antigravity with the Mem0 plugin: MCP server, lifecycle hooks, and slash commands."
+description: "Add persistent memory to Google Antigravity with the Mem0 plugin: a search tool, lifecycle hooks, and memory skills."
 ---

-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.
+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).

 ## 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" rel="nofollow">Get your API key</a> (free sign-up at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-antigravity" rel="nofollow">app.mem0.ai</a>)
+   - <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. Add it to your shell profile so it persists across sessions:
+2. Python 3.10 or newer available as `python3`
+
+3. Add the key to your shell profile so it persists across sessions:

 <CodeGroup>
 ```bash zsh
@@ -26,22 +32,32 @@ 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/mem0-plugin ~/.gemini/config/plugins/mem0
+npx degit mem0ai/mem0/integrations/antigravity-plugin ~/.gemini/config/plugins/mem0
 ```

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

 ## What's Included

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

-## Available MCP Tools
+## 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

 | Tool | Description |
 |------|-------------|
@@ -57,23 +73,52 @@ This installs the MCP server, lifecycle hooks, and shared scripts.

 ## Lifecycle Hooks

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

 | Hook | Event | What it does |
 |------|-------|-------------|
-| **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) |
+| **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 |

-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.
+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.

 ## Troubleshooting

 - **No tools appearing**: Restart your Antigravity session after installation
- **"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`
+- **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`

 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Kartik	b7ad69afda	docs(skills): refresh mem0 skills against SDK 2.2.1 / TS 3.3.1 (#7548 )	2026-10-07 18:36:15 +05:30
rupak	d62ce07fac	fix(vector-store): stop writing service account private key to DEBUG logs in GoogleMatchingEngine (#7506 ) Co-authored-by: rupak-eng <rupak-eng@users.noreply.github.com>	2026-10-07 16:20:38 +05:30
Shashidhar Kundur	0516f19f72	fix(ts-oss): stop add() from mutating the caller's filters object (#6797 )	2026-10-07 15:53:25 +05:30
Harsh Vardhan Gupta	c93420c49a	fix(security): resolve 13 Vanta HIGH Dependabot vulnerabilities (#7528 ) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 20:52:59 +05:30
Harsh Vardhan Gupta	abb81c88e1	fix(security): resolve 7 Vanta MEDIUM Dependabot vulnerabilities (undici, ip-address, adm-zip) (#7510 ) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-01 21:46:18 +05:30
Kartik	94c3fe9f23	chore(release): bump Python SDK to 2.2.1 and TypeScript SDK to 3.3.1 (#7456 )	2026-09-25 23:04:12 +05:30
Kartik	947ac79818	fix(ts-sdk): stop forcing pg on installs (optional ranged pg peer, optional natural) (#7450 )	2026-09-25 20:46:24 +05:30
Yash Singh	8127e8bd47	fix(vector_stores/turbopuffer): make search score respect distance_metric (#6559 )	2026-09-25 17:08:20 +05:30
Abhay Singh	5fd01d284a	fix(ts-oss/turbopuffer): bound euclidean_squared distance to a similarity score (#6580 )	2026-09-25 17:07:11 +05:30
Ratish jain	70c676c8c4	fix: wire dev tooling (ruff/isort/pre-commit) into hatch dev environments (#6684 )	2026-09-25 17:04:47 +05:30
Yash Singh	a2d8a8a849	fix(vector_stores/s3_vectors): make search score metric-aware (#6547 )	2026-09-25 16:21:16 +05:30
Ayaan Gazali	fb6d5e1917	fix(llms/aws_bedrock): iterate Converse content blocks for Anthropic text (#6369 )	2026-09-25 16:20:09 +05:30
Yash Singh	ccd216cff0	fix(vector_stores/turbopuffer): apply all filter operators instead of dropping them (#6564 )	2026-09-25 15:53:35 +05:30
Abhay Singh	545306db5a	fix(ts-oss/turbopuffer): apply all filter operators, not just gte/lte (#6578 )	2026-09-25 15:30:31 +05:30
mintlify[bot]	8d6c001966	Fix grammar & typos: correct OpenSearch spelling in changelog (#7442 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-25 09:58:06 +05:30
Varun S G	989c7da0fc	fix(oss): stop ConfigManager from injecting OpenAI's baseURL and model into other providers (#7350 )	2026-09-24 22:14:28 +05:30
Mohd Quamar Tyagi	d675cf68ad	fix(memory): restore Memory and AsyncMemory context-manager protocol (#7354 )	2026-09-24 22:04:57 +05:30
Diwakar Ray Yadav	2c6ff619d1	fix(memory): exclude vector-store-rejected records from ADD results (#7066 )	2026-09-24 22:01:31 +05:30
Kartik	f4acc89a29	docs: remove memory types page and preserve redirects (#7437 )	2026-09-24 18:00:54 +05:30
Kartik	43849c6e9d	feat(integrations): migrate and validate standalone Hermes Mem0 plugin (#7372 )	2026-09-24 17:53:29 +05:30
Kartik	47a69e1e72	docs(changelog): add v2.2.1 entry for Valkey None-timestamps fix (#7425 )	2026-09-24 00:30:19 +05:30
Karthik	ea9bbcabed	feat(profiles): User Profiles v1 — SDK methods + docs (#7340 ) Co-authored-by: Pratik <10096516+pratikgajjar@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-24 00:11:22 +05:30
Brennan	0cddc36d52	Protect against None timestamps in Valkey layer (#6993 ) Signed-off-by: Brennan Cathcart <brennancathcart@gmail.com>	2026-09-23 22:32:04 +05:30
mintlify[bot]	83b07b1537	Fix grammar & typos: minor fixes across docs (#7423 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-23 19:53:11 +05:30
Kartik	8c02c425a5	fix(agent-plugins): match memo prompts and tool descriptions, release 0.3.3 (#7420 ) Co-authored-by: Claude <noreply@anthropic.com>	2026-09-23 19:35:25 +05:30
mintlify[bot]	f8082a7345	Fix grammar & typos: API casing in template heading (#7410 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-22 20:06:21 +05:30
Deshraj Yadav	5d38e3703a	chore: remove CLI_SPECIFICATION.md (#4578 ) Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: kartik-mem0 <kartik.labhshetwar@mem0.ai>	2026-09-22 19:52:54 +05:30
88lin	fd8fd087ea	docs(vectordbs/pinecone): document extra_params on the Python config table (#7222 )	2026-09-22 19:25:51 +05:30
Shahil kadia	a214ec37bc	fix(examples): migrate OSS Memory search/get_all calls to v3 filters API (#7300 ) Co-authored-by: Shahil Kadia <nexiouscaliver@users.noreply.github.com>	2026-09-22 19:01:33 +05:30
mintlify[bot]	8b38da9ab8	Fix grammar & typos: SDK changelog v2.0.8 entry (#6716 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-22 18:51:03 +05:30
mintlify[bot]	17852dc648	SEO & metadata audit: shorten supabase cookbook description (#7380 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-22 18:50:39 +05:30
Himanshu	a39a802bbc	docs(cookbooks): Company Brain with Mem0 Platform + Supabase (#7309 )	2026-09-18 23:19:15 +05:30
Saket Aryan	19f7134082	chore(release): bump every package the telemetry attribution work changed (#7373 ) Co-authored-by: kartik-mem0 <kartik.labhshetwar@mem0.ai>	2026-09-18 16:28:55 +05:30
Saket Aryan	a8d3634312	fix(plugins): stop the TypeScript telemetry losing events and misattributing accounts (#7358 )	2026-09-18 14:13:22 +05:30
Saket Aryan	1a5c7ad28c	feat(integrations): declare which surface each client is, and its version (#7326 )	2026-09-18 14:13:11 +05:30
Saket Aryan	4e38b057fd	fix(plugins): count installs once, and re-resolve the email when the key changes (#7325 )	2026-09-18 13:46:25 +05:30
Saket Aryan	3362999095	fix(plugins): stop delivering telemetry events twice, and stop losing parked ones (#7324 )	2026-09-18 13:43:33 +05:30
Saket Aryan	012cd32c3a	fix(plugins): report the plugin that produced the event, not the one that sent it (#7323 )	2026-09-18 13:42:34 +05:30
Saket Aryan	e4e0307ae6	fix(plugins): say what telemetry actually sends, and salt the hashes (#7322 )	2026-09-18 13:23:05 +05:30
Kartik	84bf468176	docs: add practical Mem0 Copilot guide (MEM-6344) (#7337 )	2026-09-18 06:54:04 +05:30
mintlify[bot]	f135cb9949	SEO & metadata audit: shorten hermes description (#7359 ) Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>	2026-09-17 19:32:03 +05:30
ANIRUDDHA ADAK	f5220ff8d4	fix(security): bump next to 15.5.24, patches GHSA-p293-qw3h-jr36 (#7320 )	2026-09-17 19:23:45 +05:30
Paurush Mittal	0df3e4b87d	fix(docs): correct rendered titles and remaining SEO links (#7344 )	2026-09-16 17:14:33 +05:30
PowderXu	b51f7692f0	docs(upstash): correct the default collection namespace (#7287 )	2026-09-15 19:41:46 +05:30
jianyx1	dc7f88363f	docs: fix Hermes integration page to match the current plugin (#7244 )	2026-09-15 19:23:17 +05:30
Harsh Vardhan Gupta	c7ee362aff	fix(security): resolve 12 Vanta/Dependabot vulnerabilities across 6 pnpm workspaces + poetry.lock (#7280 ) Co-authored-by: kartik-mem0 <kartik.labhshetwar@mem0.ai>	2026-09-11 16:07:57 +05:30
Kartik	d873892dad	feat(plugins)!: make Sidekick exclusive to Claude Code (#7278 )	2026-09-10 20:51:50 +05:30
Kartik	02f7a9b2c4	docs: align agent plugin guides with shared runtime behavior (#7269 )	2026-09-09 01:03:26 +05:30
Kartik	73e7b8763a	refactor(integrations): shared agent plugin runtimes and native adapters (#7203 )	2026-09-08 23:32:25 +05:30
Kartik	dae67f74f5	fix(docs): SEO improvements for page titles, internal links, and URL structure (#7224 )	2026-09-04 20:32:23 +05:30