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
606 changed files with 47336 additions and 30445 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,15 +18,14 @@ 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 |
 | Zapier App | `zapier-mem0-checks.yml` | Push to main (`integrations/zapier-mem0/`), manual | tsc + `zapier validate` + offline unit tests on Node 22 |
 | mem0-strands | `mem0-strands-checks.yml` | Push to main (`integrations/mem0-strands/`), manual | Ruff + mypy + pytest + hatch build on Python 3.10, 3.11, 3.12 |
-| Eve | `eve-checks.yml` | Push to main (`integrations/eve/`), manual | tsc + vitest + tsup on Node 24 |
 | docs llms.txt | `docs-llms-txt-check.yml` | Manual | `docs/llms.txt` coverage |
 | GitHub Scripts | inline in `ci-gate.yml` | none | `node` over every `.github/scripts/*.test.js` |

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

 - Package CD workflows are `workflow_dispatch`-only, with `tag` and `prerelease` inputs. They check out and build the given tag.
 - All publishing uses **OIDC trusted publishing**. No tokens, no secrets.
@@ -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,15 +38,14 @@ 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 }}
      n8n_nodes_mem0: ${{ steps.filter.outputs.n8n_nodes_mem0 }}
      zapier_mem0: ${{ steps.filter.outputs.zapier_mem0 }}
      mem0_strands: ${{ steps.filter.outputs.mem0_strands }}
-      eve: ${{ steps.filter.outputs.eve }}
      docs_llms_txt: ${{ steps.filter.outputs.docs_llms_txt }}
      github_scripts: ${{ steps.filter.outputs.github_scripts }}
    steps:
@@ -77,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:
@@ -111,10 +126,6 @@ jobs:
              - 'integrations/mem0-strands/**'
              - '.github/workflows/mem0-strands-checks.yml'
              - '.github/workflows/ci-gate.yml'
-            eve:
-              - 'integrations/eve/**'
-              - '.github/workflows/eve-checks.yml'
-              - '.github/workflows/ci-gate.yml'
            docs_llms_txt:
              - 'docs/**/*.mdx'
              - 'docs/llms.txt'
@@ -165,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:
@@ -219,13 +229,6 @@ jobs:
    uses: ./.github/workflows/mem0-strands-checks.yml
    secrets: inherit

-  eve:
-    name: Eve
-    needs: changes
-    if: needs.changes.outputs.eve == 'true'
-    uses: ./.github/workflows/eve-checks.yml
-    secrets: inherit
-
  docs-llms-txt:
    name: docs llms.txt
    needs: changes
@@ -260,15 +263,14 @@ jobs:
      - cli-python
      - cli-node
      - openclaw
-      - mem0-plugin
-      - claude-code-plugin
+      - agent-plugins-python
+      - agent-plugins-typescript
      - opencode-plugin
      - pi-agent-plugin
      - deepseek-plugin
      - n8n-nodes-mem0
      - zapier-mem0
      - mem0-strands
-      - eve
      - docs-llms-txt
      - github-scripts
    if: always()
@@ -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,57 +0,0 @@
-name: Publish @mem0/eve 📦 to npm
-
-on:
-  workflow_dispatch:
-    inputs:
-      tag:
-        description: 'Release tag to build and publish (e.g. eve-v0.1.0)'
-        required: true
-        type: string
-      prerelease:
-        description: 'Publish under the version preid dist-tag instead of latest'
-        required: false
-        type: boolean
-        default: false
-
-jobs:
-  build-n-publish:
-    name: Build and publish @mem0/eve 📦 to npm
-    if: startsWith(inputs.tag, 'eve-v')
-    runs-on: ubuntu-latest
-    permissions:
-      id-token: write
-    defaults:
-      run:
-        working-directory: integrations/eve
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ inputs.tag }}
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-          registry-url: 'https://registry.npmjs.org'
-          cache: 'pnpm'
-          cache-dependency-path: integrations/eve/pnpm-lock.yaml
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build
-        run: pnpm build
-
-      - name: Publish to npm
-        run: |
-          if [ "${{ inputs.prerelease }}" = "true" ]; then
-            PREID=$(node -p "require('./package.json').version.split('-')[1].split('.')[0]")
-            npx npm@latest publish --provenance --access public --tag "$PREID"
-          else
-            npx npm@latest publish --provenance --access public
-          fi
@@ -1,85 +0,0 @@
-name: eve checks
-
-on:
-  workflow_dispatch:
-  push:
-    branches: [main]
-    paths:
-      - 'integrations/eve/**'
-      - '.github/workflows/eve-checks.yml'
-  workflow_call:
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: 'pnpm'
-          cache-dependency-path: integrations/eve/pnpm-lock.yaml
-
-      - name: Install dependencies
-        run: cd integrations/eve && pnpm install --frozen-lockfile
-
-      - name: Type check
-        run: cd integrations/eve && pnpm typecheck
-
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: 'pnpm'
-          cache-dependency-path: integrations/eve/pnpm-lock.yaml
-
-      - name: Install dependencies
-        run: cd integrations/eve && pnpm install --frozen-lockfile
-
-      - name: Run tests
-        run: cd integrations/eve && pnpm test
-
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: 'pnpm'
-          cache-dependency-path: integrations/eve/pnpm-lock.yaml
-
-      - name: Install dependencies
-        run: cd integrations/eve && pnpm install --frozen-lockfile
-
-      - name: Build
-        run: cd integrations/eve && pnpm build
-
-      - name: Verify dist output exists
-        run: |
-          test -f integrations/eve/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
-          test -f integrations/eve/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
@@ -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
@@ -48,7 +48,6 @@ jobs:
            deepseek-plugin-v*)  workflow="deepseek-plugin-cd.yml" ;;
            n8n-nodes-mem0-v*) workflow="n8n-nodes-mem0-cd.yml" ;;
            mem0-strands-v*)   workflow="mem0-strands-cd.yml" ;;
-            eve-v*)            workflow="eve-cd.yml" ;;
            v*)           workflow="cd.yml" ;;
            *)
              echo "::error::Release tag '$TAG' does not match any known package prefix — nothing will be published. See the tag prefix table in AGENTS.md."
@@ -14,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,7 +1,6 @@
 ---
-title: "Overview"
-seo:
-  title: "API Reference Overview - Mem0"
+title: "API Reference Overview"
+sidebarTitle: "Overview"
 icon: "terminal"
 iconType: "solid"
 description: "REST APIs for memory management, search, and entity operations"
@@ -1,7 +1,6 @@
 ---
-title: 'Delete Memory'
-seo:
-  title: "Delete Memory API Endpoint - Mem0"
+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,7 +1,6 @@
 ---
-title: 'Update Memory'
-seo:
-  title: "Update Memory API Endpoint - Mem0"
+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,7 +1,6 @@
 ---
-title: 'Add Member'
-seo:
-  title: "Add Organization Member API Endpoint - Mem0"
+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,7 +1,6 @@
 ---
-title: 'Get Members'
-seo:
-  title: "Get Organization Members API Endpoint - Mem0"
+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,7 +1,6 @@
 ---
-title: 'Add Member'
-seo:
-  title: "Add Project Member API Endpoint - Mem0"
+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,7 +1,6 @@
 ---
-title: 'Get Members'
-seo:
-  title: "Get Project Members API Endpoint - Mem0"
+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:**
@@ -1864,6 +1919,13 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-

 <Tab title="CLI">

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

 **New Features:**
@@ -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,7 +1,6 @@
 ---
-title: Configurations
-seo:
-  title: "Embedder Configuration Reference - Mem0"
+title: "Embedder Configuration Reference"
+sidebarTitle: "Configurations"
 description: "Reference for embedder configuration options in Mem0, including provider selection and model settings."
 ---

@@ -1,7 +1,6 @@
 ---
-title: AWS Bedrock
-seo:
-  title: "AWS Bedrock as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Azure OpenAI
-seo:
-  title: "Azure OpenAI as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Google AI
-seo:
-  title: "Google AI as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: LangChain
-seo:
-  title: "LangChain as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: "LM Studio"
-seo:
-  title: "LM Studio as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: "Ollama"
-seo:
-  title: "Ollama as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: OpenAI
-seo:
-  title: "OpenAI as Embedding Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Together
-seo:
-  title: "Together AI as Embedding Provider - Mem0"
+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."
 ---

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

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

@@ -1,7 +1,6 @@
 ---
-title: AWS Bedrock
-seo:
-  title: "AWS Bedrock as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Azure OpenAI
-seo:
-  title: "Azure OpenAI as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Google AI
-seo:
-  title: "Google AI as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: LangChain
-seo:
-  title: "LangChain as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: LM Studio
-seo:
-  title: "LM Studio as LLM Provider - Mem0"
+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."
 ---

@@ -78,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,7 +1,6 @@
 ---
-title: Ollama
-seo:
-  title: "Ollama as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: OpenAI
-seo:
-  title: "OpenAI as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Together
-seo:
-  title: "Together AI as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: xAI
-seo:
-  title: "xAI Grok as LLM Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Overview
-seo:
-  title: "LLM Providers Overview - Mem0"
+title: "LLM Providers Overview"
+sidebarTitle: Overview
 description: "Overview of all supported LLM providers in Mem0, including OpenAI, Anthropic, Groq, Ollama, and more."
 ---

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

@@ -1,7 +1,6 @@
 ---
-title: Configurations
-seo:
-  title: "Vector Store Configuration Reference - Mem0"
+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,7 +1,6 @@
 ---
-title: LangChain
-seo:
-  title: "LangChain as Vector Store Provider - Mem0"
+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,7 +1,6 @@
 ---
-title: Overview
-seo:
-  title: "Vector Store Providers Overview - Mem0"
+title: "Vector Store Providers Overview"
+sidebarTitle: "Overview"
 description: "Overview of all supported vector databases in Mem0, including Qdrant, Chroma, PGVector, Pinecone, Oracle, and more."
 ---

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

 ## Code Breakdown

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

 ```python
 # Import dependencies
@@ -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,7 +1,6 @@
 ---
-title: Overview
-seo:
-  title: "Cookbooks and Tutorials - Mem0"
+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.
@@ -1,7 +1,6 @@
 ---
-title: Delete Memory
-seo:
-  title: "Delete Memory Operation - Mem0"
+title: "Delete Memory Operation"
+sidebarTitle: "Delete Memory"
 description: Remove memories from Mem0 either individually, in bulk, or via filters.
 icon: "trash"
 iconType: "solid"
@@ -1,7 +1,6 @@
 ---
-title: Update Memory
-seo:
-  title: "Update Memory Operation - Mem0"
+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",
@@ -325,7 +326,6 @@
                      "integrations/google-ai-adk",
                      "integrations/mastra",
                      "integrations/vercel-ai-sdk",
-                      "integrations/eve",
                      "integrations/vercel",
                      "integrations/chatdev",
                      "integrations/strands"
@@ -374,6 +374,7 @@
                      "integrations/claude-ai",
                      "integrations/cursor",
                      "integrations/codex",
+                      "integrations/kimi",
                      "integrations/opencode",
                      "integrations/antigravity"
                    ]
@@ -443,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"
                    ]
                  },
                  {
@@ -511,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",
@@ -1019,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",
@@ -1,7 +1,6 @@
 ---
-title: Overview
-seo:
-  title: "Integrations Overview - Mem0"
+title: "Integrations Overview"
+sidebarTitle: "Overview"
 description: "Overview of Mem0 integrations with popular AI frameworks and tools for persistent memory and context management."
 ---

@@ -17,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
@@ -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">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">
@@ -1,7 +1,6 @@
 ---
-title: AWS Bedrock
-seo:
-  title: "AWS Bedrock Integration with Mem0"
+title: "AWS Bedrock Integration"
+sidebarTitle: "AWS Bedrock"
 description: "Use Mem0 with AWS Bedrock and OpenSearch Service for cloud-native persistent semantic memory storage."
 ---

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

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

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

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

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

 Once installed, memory works without any action from you:

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

 ### Commands

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

 ### Search tool

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

 ### Sidekick agent

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

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

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

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

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

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

 **Step by step:**

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

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

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

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

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

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

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

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

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

 ## Settings

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

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

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

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

 ## Prerequisites

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

 2. OpenAI Codex access

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

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

 ### Option A: Plugin Marketplace (Recommended)

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

 1. Add the Mem0 marketplace:

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

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

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

 ### Managing the Plugin

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

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

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

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

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

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

 | Tool | Description |
 |------|-------------|
@@ -126,46 +135,33 @@ Once installed, the following tools are available in every Codex session:
 | `delete_entities` | Delete a user/agent/app/run entity and its memories |
 | `list_entities` | List users/agents/apps/runs stored in Mem0 |

-## Lifecycle Hooks
+## Lifecycle hooks

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

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

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

 ## Example Workflow

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

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

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

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

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

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

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

 ## Prerequisites

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

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

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

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

 ## Installation

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

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

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

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

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

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

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

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


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

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

 | Tool | Description |
 |------|-------------|
@@ -89,11 +117,29 @@ Once installed, the following tools are available in every Cursor session:
 | `delete_entities` | Delete a user/agent/app/run entity and its memories |
 | `list_entities` | List users/agents/apps/runs stored in Mem0 |

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

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

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

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

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

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

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

 ## Overview

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

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

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

 ## How it works

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

 ## Prerequisites

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

 ## Try it locally

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

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

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

 The `cordis.yml` entry looks like this:

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

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

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

 ## Telemetry

-Writes are tagged `source="DEEPSEEK_HARNESS"` so Mem0's backend can attribute usage to this integration.
+Writes are tagged `source="DEEPSEEK_HARNESS"` so Mem0 can attribute usage to this integration. Usage events include operation names, durations, result counts, and coarse failure kinds. They are **not anonymous**: when an API key is configured they are sent under your Mem0 account email, the same way the SDK attributes its own. Queries, memory text, entity IDs, and API keys are never included. Set `MEM0_TELEMETRY=false` to opt out.
+
+<Note>
+  This plugin is a developer preview and tracks the evolving DeepSeek Harness plugin API.
+</Note>
+
+## Troubleshooting
+
+- **`MISSING_CREDENTIAL` for `deepseek-official`**: Configure `DEEPSEEK_API_KEY` through Harness's Models page or export it in the shell that launches Harness.
+- **`EMFILE: too many open files, watch` on macOS**: Launch Harness with `CHOKIDAR_USEPOLLING=1`.
+- **Mem0 tools do not appear**: Run Harness with `--dump-config` and confirm the final composition contains the `mem0` row and the installed `dist/index.js` path.
+
+Per-call `userId` overrides are rejected unless the operator enables `allowUserOverride: true`. Automatic recall and capture always use the configured user.
@@ -1,64 +0,0 @@
---
-title: Eve
-description: "Use Mem0 as a first-class memory provider for Vercel Eve agents."
---
-
-[Eve](https://eve.dev/docs/memory) is Vercel's agent framework. A memory provider sits in the agent loop: Eve recalls context before each turn, captures completed turns, and exposes provider tools. `@mem0/eve` is Mem0's implementation of that contract.
-
-This is not the Mem0 MCP connection. MCP gives the model tools it may or may not call. The memory provider runs automatically. The live MCP install is `eve add connection/mem0`.
-
-## Install
-
-```bash
-npm install @mem0/eve
-```
-
-`eve` is a peer dependency. Get an API key from the [Mem0 dashboard](https://app.mem0.ai/dashboard/api-keys).
-
-Create `agent/memory/mem0.ts`:
-
-```ts
-import { defineMemory } from "eve/memory";
-import { byPrincipal } from "eve/memory/scope";
-import { mem0Provider } from "@mem0/eve";
-
-export default defineMemory({
-  description: "Recall and manage durable context for the current user.",
-  provider: mem0Provider({
-    apiKey: process.env.MEM0_API_KEY!,
-  }),
-  scope: byPrincipal,
-});
-```
-
-`eve add memory/mem0` is not in Eve's catalog yet. After Mem0 is listed in the official registry, that command will create the same slot file.
-
-## How it works
-
-1. **Recall.** Before each turn and after compaction, Mem0 searches memories for the locked Eve scope and returns `{ id, content }` messages. Eve injects those as user-role messages attributed to the slot.
-2. **Capture.** After a successful turn, Mem0 adds the user messages from that turn and, when present, that turn's assistant reply. By default (`infer: true`) Mem0 extracts durable facts. Capture is deduplicated per `operationId` on a best-effort basis (an in-process gate plus a durable `metadata.operation_id` lookup); because that check and the write are not atomic and platform writes are asynchronous, a restart or concurrent worker can occasionally capture a turn twice.
-3. **Tools.** The model can call `search`, `remember`, and `forget`. Eve qualifies them as `mem0__search`, `mem0__remember`, and `mem0__forget` when the slot file is `mem0.ts`. `remember` returns `{ status: "saved" }` on a resolved write or `{ status: "queued" }` when the platform accepts it for asynchronous extraction.
-
-Eve owns namespace, scope, and when recall/capture run. Mem0 owns storage, ranking, and extraction. Search, capture, remember, and forget are partitioned by `memory.scope.key`. Forget deletes by id only after confirming the memory belongs to that key.
-
-## Options
-
-```ts
-mem0Provider({
-  apiKey: process.env.MEM0_API_KEY!,
-  topK: 5,
-  threshold: 0.1,
-  rerank: false,
-  infer: true,
-  autoSearch: { enabled: true },
-  capture: { enabled: true },
-});
-```
-
-See the [`@mem0/eve` README](https://github.com/mem0ai/mem0/tree/main/integrations/eve) for the full option list.
-
-## Related
-
- [Eve memory docs](https://eve.dev/docs/memory)
- [Build a memory provider](https://eve.dev/docs/memory/custom-provider)
- [Vercel AI SDK](/integrations/vercel-ai-sdk) for `generateText` / `streamText` apps that are not Eve agents
@@ -23,7 +23,7 @@ npm install -g flowise
 npx flowise start
 ```

-2. Access to the Flowise UI at http://localhost:3000
+2. Access to the Flowise UI at `http://localhost:3000`
 3. Basic familiarity with [Flowise's LLM orchestration](https://flowiseai.com/#features) concepts

 ## Setup and Configuration
@@ -1,53 +1,65 @@
 ---
 title: Hermes Agent
-description: "Add long-term memory to Hermes agents with Mem0, on managed Mem0 Cloud or fully self-hosted (OSS), with automatic background sync and zero-latency prefetch."
+description: "Add persistent memory to Hermes Agent with Mem0 Cloud, a self-hosted server, or the in-process OSS SDK."
 ---

-Add long-term memory to [Hermes Agent](https://github.com/NousResearch/hermes-agent), a self-improving AI agent CLI by Nous Research. Hermes has a pluggable memory system, and Mem0 is one of the supported providers. Once enabled, Mem0 learns facts from your conversations and surfaces relevant ones before each turn, without slowing down the chat.
+Add long-term memory to [Hermes Agent](https://github.com/NousResearch/hermes-agent), a self-improving AI agent CLI by Nous Research. The [standalone Mem0 plugin](https://github.com/mem0ai/mem0/tree/main/integrations/hermes-plugin-mem0) learns facts from conversations and recalls relevant memories for the current question.

-You can run Mem0 in two ways:
+You can run Mem0 in three ways:

 - **Platform mode** (default): managed Mem0 Cloud. Add your API key and you are ready.
- **OSS mode**: fully self-hosted with your own LLM, embedder, and vector store. No data leaves your machine.
+- **Self-hosted server mode**: point the plugin at a Mem0 server you run yourself (the Docker-shipped server). The plugin only talks HTTP to your server.
+- **OSS mode**: run Mem0 in-process with your own LLM, embedder, and vector store. No Mem0 server required.

 ## How It Works

-Hermes runs a built-in memory system (file-based `MEMORY.md` and `USER.md`) alongside one external provider. When Mem0 is active, it works additively with the built-in system at three points in every conversation turn.
+Hermes runs a built-in memory system (file-based `MEMORY.md` and `USER.md`) alongside one external provider. When Mem0 is active, it works additively with the built-in system at two points in every conversation turn.

-### 1. Before the agent responds (prefetch)
+### 1. Current-turn recall (bounded wait)

-When you send a message, Hermes checks for cached Mem0 search results from the previous turn. If they exist, those memories are injected into the system prompt so the model can see them. This is zero-latency, with no waiting on an API call.
+When you send a message, Hermes searches your stored memories for the current question and waits up to 3 seconds for results. If they arrive in time, they are injected into the system prompt so the model can see them. If the backend is slower, Hermes skips the injection and the model can still call `mem0_search` itself after the bounded recall wait.

-### 2. After the agent responds (sync)
+### 2. Background fact extraction (sync)

-Once the model finishes, Hermes sends the `(user message, assistant response)` pair to Mem0 in a background thread. Mem0 extracts facts automatically (for example, "user prefers Python" or "user works at Acme Corp"), so you never have to tell it what to remember. Each write is tagged with the gateway channel it came from.
+Once the model finishes, the plugin sends the user message and assistant response to Mem0 in a background thread for fact extraction. Each write includes the agent identifier and gateway channel.

-### 3. Background prefetch for the next turn
-
-At the same time, Hermes runs a background search to pre-load relevant memories for your next message. By the time you type, the results are already cached.
+<Note>
+  Automatic capture truncates each message to **450 characters by default in every mode**, preferring a sentence boundary. Adjust `sync_max_chars` for your model's context limit. Capture is best effort: if the previous sync is still running after a five-second wait, the next turn is skipped. Use `mem0_add` to store specific text verbatim.
+</Note>

 ## Agent Tools

-When Mem0 is active, the model gets five tools it can call during a conversation:
+When Mem0 is active, the model gets four tools it can call during a conversation:

 | Tool | Description | Parameters |
 |------|-------------|------------|
-| `mem0_list` | List all stored memories, for a full overview | `page`, `page_size` (default 100, max 200) |
-| `mem0_search` | Semantic search by meaning, ranked by relevance | `query` (required), `top_k` (default 10, max 50), `rerank` (default `true`, Platform mode only) |
+| `mem0_search` | Semantic search by meaning, ranked by relevance | `query` (required), `top_k` (default 10, max 50), `rerank` (uses the configured default, Platform mode only) |
 | `mem0_add` | Store a fact verbatim, with no LLM extraction | `content` (required) |
 | `mem0_update` | Update a memory's text by ID | `memory_id`, `text` (both required) |
 | `mem0_delete` | Delete a memory by ID | `memory_id` (required) |

 ## Installation

-Install Hermes Agent:
+Install [Hermes Agent](https://github.com/NousResearch/hermes-agent) with memory-provider plugin support and Python 3.11 or later. Once the plugin directory is available on Mem0's main branch, install it from the repository subdirectory:

 ```bash
-curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
-source ~/.bashrc
+hermes plugins install mem0ai/mem0/integrations/hermes-plugin-mem0
+hermes plugins enable mem0
+hermes memory setup
+hermes memory status
 ```

-The `mem0ai` package is installed automatically when you enable the Mem0 provider, so there is no manual pip step. OSS providers may need extra packages (for example `qdrant-client`, `psycopg2-binary`, or `ollama`), which the setup flow installs for you when you pick them.
+Select **mem0** in setup and choose one of the modes below. Start a fresh Hermes conversation after setup.
+
+Hermes installers with plugin dependency support install `mem0ai>=2.0.10,<3` and `httpx>=0.27,<1` from the plugin's `pyproject.toml`. Older hosts such as Hermes v0.21.3 require those packages to be installed explicitly into the Hermes Python environment. The OSS setup flow installs additional provider packages as needed.
+
+<Note>
+  Hermes versions that still bundle Mem0 prefer the bundled provider. Use a Hermes release that has completed the standalone-provider migration; installing this plugin alone does not replace the bundled implementation. Existing users should keep their current configuration; see [Migration for existing users](#migration-for-existing-users).
+</Note>
+
+<Note>
+  Run the setup wizard in an interactive terminal. On Hermes hosts whose `hermes memory setup --help` lists only a provider argument, options such as `--mode`, `--host`, and `--oss-llm` are rejected by Hermes before the plugin runs. Use `hermes memory setup mem0` or the manual configuration below. Redirected input cannot select the mode picker and falls back to Platform.
+</Note>

 ## Platform Setup

@@ -56,10 +68,10 @@ Platform mode uses managed Mem0 Cloud and is the fastest way to start.
 ### Option 1: Interactive wizard (recommended)

 ```bash
-hermes memory setup
+hermes memory setup mem0
 ```

-Select **mem0**, choose **Platform**, and paste your API key when prompted. The wizard writes the non-secret settings to `~/.hermes/mem0.json` and keeps the key in `~/.hermes/.env`.
+Choose **Platform** and paste your API key when prompted. The wizard writes settings to `$HERMES_HOME/mem0.json` and keeps the key in that profile's `.env`. The default Hermes home is `~/.hermes`; named profiles use their own home directory.

 <Note>Get your API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-hermes">app.mem0.ai</a>.</Note>

@@ -67,37 +79,74 @@ Select **mem0**, choose **Platform**, and paste your API key when prompted. The

 ```bash
 hermes config set memory.provider mem0
-echo "MEM0_API_KEY=your-api-key" >> ~/.hermes/.env
 ```

-Then in your `config.yaml`:
+Add your key to the active Hermes profile's `.env`:

-```yaml
-memory:
-  provider: mem0
+```dotenv
+MEM0_API_KEY=your-api-key
 ```

-That's it. Mem0 runs automatically from here.
+Set these values in the active profile's `mem0.json`, choosing a stable user identity:

-## OSS (Self-Hosted) Setup
+```json
+{
+  "mode": "platform",
+  "host": "",
+  "user_id": "my-hermes-user"
+}
+```

-OSS mode runs Mem0 entirely on your own infrastructure: your LLM, your embedder, and your vector store. No data is sent to Mem0 Cloud, and no Mem0 API key is required.
+Remove any stale `MEM0_HOST` from the environment and profile `.env`, and remove an old inline `api_key` from `mem0.json` so the new `.env` key is used. The config command sets `memory.provider: mem0` in that profile's `config.yaml`. Restart Hermes and check `hermes memory status`.
+
+## Self-Hosted Server Setup
+
+Run the [Mem0 server](https://github.com/mem0ai/mem0/tree/main/server) (FastAPI + pgvector) from its Docker image and point the plugin at it. Unlike OSS mode, the plugin just talks HTTP to your server.

 ### Interactive

 ```bash
-hermes memory setup
-# Select "mem0", then "Open Source (self-hosted)"
+hermes memory setup mem0
+# Choose "Self-hosted server", then enter the server URL and API key
+```
+
+### Manual configuration
+
+Select `mem0` with `hermes config set memory.provider mem0`. Set these values in the active profile's `mem0.json`:
+
+```json
+{
+  "mode": "platform",
+  "host": "http://localhost:8888",
+  "user_id": "my-hermes-user"
+}
+```
+
+Add the server key to that profile's `.env`:
+
+```dotenv
+MEM0_API_KEY=your-admin-api-key
+```
+
+Remove an old inline `api_key` from `mem0.json` so the `.env` key is used. `MEM0_HOST` can also supply the server URL, but a non-empty `host` in `mem0.json` overrides it. Keep `mode` set to `platform` for the HTTP server backend.
+
+Then start a fresh Hermes session and call `mem0_search` — it connects to your server. The plugin authenticates with `X-API-Key` and uses the server's `/search` and `/memories` routes. The API key is optional only for servers running with `AUTH_DISABLED`.
+
+<Note>Setting `host` routes to the self-hosted server automatically. Don't combine it with `mode: oss` — OSS takes precedence and ignores `host`.</Note>
+
+## OSS (Self-Hosted) Setup
+
+OSS mode runs the Mem0 SDK in the Hermes process with your chosen LLM, embedder, and vector store. It does not use Mem0 Cloud or require a Mem0 API key. Data goes to the model services you configure; use local Ollama models and local storage for a fully local setup.
+
+### Interactive
+
+```bash
+hermes memory setup mem0
+# Choose "Open Source"
 # Follow the prompts for LLM, embedder, and vector store
 ```

-### With flags
-
-```bash
-hermes memory setup mem0 --mode oss \
-  --oss-llm openai --oss-llm-key sk-... \
-  --oss-vector qdrant
-```
+The wizard uses the listed default OpenAI models and local Qdrant storage. For custom OpenAI-compatible endpoints, deployment names, or a Qdrant server, use manual configuration below.

 ### Supported providers

@@ -107,79 +156,91 @@ hermes memory setup mem0 --mode oss \
 | Embedder | `openai` (default `text-embedding-3-small`), `ollama` (local, default `nomic-embed-text`) |
 | Vector store | `qdrant` (local path or server), `pgvector` |

-### Flag reference
-
-| Flag | Description |
-|------|-------------|
-| `--mode` | `platform` or `oss` |
-| `--oss-llm` | LLM provider (`openai` or `ollama`, default `openai`) |
-| `--oss-llm-key` | LLM API key (for `openai`) |
-| `--oss-llm-model` | Override the LLM model |
-| `--oss-llm-url` | LLM base URL (for `ollama` or a custom endpoint) |
-| `--oss-embedder` | Embedder provider (default `openai`) |
-| `--oss-embedder-key` | Embedder API key |
-| `--oss-vector` | Vector store (`qdrant` or `pgvector`, default `qdrant`) |
-| `--oss-vector-path` | Local Qdrant storage path |
-| `--oss-vector-host`, `--oss-vector-port` | PGVector or remote Qdrant host and port |
-| `--oss-vector-user`, `--oss-vector-password`, `--oss-vector-dbname` | PGVector connection details |
-| `--user-id` | Canonical user identifier |
-| `--dry-run` | Preview the resolved config without writing it |
-
-## Switching Modes
-
-You can move between Platform and OSS at any time. Run the setup command again, or edit `~/.hermes/mem0.json` directly.
+### Manual configuration

 ```bash
-# Platform to OSS
-hermes memory setup mem0 --mode oss --oss-llm-key sk-...
-
-# OSS to Platform
-hermes memory setup mem0 --mode platform --api-key sk-...
-
-# Preview without writing anything
-hermes memory setup mem0 --mode oss --oss-llm-key sk-... --dry-run
+hermes config set memory.provider mem0
 ```

-A self-hosted `~/.hermes/mem0.json` looks like this:
+Add the model key to the active profile's `.env`:
+
+```dotenv
+OPENAI_API_KEY=your-model-api-key
+```
+
+Set the following in that profile's `mem0.json`. Use your existing storage path when migrating; for a new named profile, choose a path inside that profile's home.

 ```json
 {
  "mode": "oss",
+  "user_id": "my-hermes-user",
  "oss": {
-    "llm": {"provider": "openai", "config": {"model": "gpt-5-mini"}},
+    "llm": {"provider": "openai", "config": {"model": "gpt-5-mini", "is_reasoning_model": true}},
    "embedder": {"provider": "openai", "config": {"model": "text-embedding-3-small"}},
    "vector_store": {"provider": "qdrant", "config": {"path": "~/.hermes/mem0_qdrant"}}
  }
 }
 ```

+For an OpenAI-compatible service such as Azure's `/openai/v1` endpoint, add `OPENAI_BASE_URL` to the profile's `.env` and set each `model` to its deployed name. Both the LLM and embedder use this endpoint unless their `config.openai_base_url` overrides it. The main Hermes chat model is configured separately; this JSON configures Mem0's extraction and embedding models.
+
+For a Qdrant server, replace `vector_store.config.path` with `url`, for example `"url": "http://localhost:6333"`. Manual setup does not install optional provider dependencies: install `qdrant-client`, `psycopg2-binary`, or `ollama` in the **Hermes Python environment** as needed for your selected providers. Start a fresh session and verify a memory write and search; `hermes memory status` reports configuration availability, not a full backend health check.
+
+Desktop sessions in the same process and profile share local Qdrant storage when their OSS settings match. Operations are serialized, and storage closes after the last session releases it. Conflicting settings are rejected without changing existing memories; close active sessions before changing models or credentials. For concurrent CLI and Desktop processes, use a Qdrant server or the self-hosted Mem0 HTTP API instead of sharing a local directory.
+
+## Switching Modes
+
+Run `hermes memory setup mem0` in an interactive terminal and choose the new mode, or edit the active profile's `mem0.json` using the examples above. Switching backends does not transfer memories between them. Preserve existing OSS storage paths when editing configuration. When returning to Platform, set `mode` to `platform`, clear `host`, and remove any stale `MEM0_HOST` setting from your environment and profile `.env`.
+
 ## Configuration

-Behavioral settings live in `~/.hermes/mem0.json` and are written for you by `hermes memory setup`. Only the secret `MEM0_API_KEY` belongs in `~/.hermes/.env`.
+Settings live in `$HERMES_HOME/mem0.json` and are written by `hermes memory setup`. API keys normally live in that profile's `.env`; distinct OpenAI LLM/embedder keys and database credentials are stored in the OSS configuration. Setup writes these files atomically with owner-only permissions.
+
+When editing these files manually, restrict both `.env` and `mem0.json` to their owner (`chmod 600` on Unix). Keep configuration and secrets in the same active Hermes profile.
+
+`MEM0_MODE`, `MEM0_HOST`, `MEM0_USER_ID`, and `MEM0_AGENT_ID` supply environment defaults. Non-empty values in `mem0.json` take precedence. `MEM0_API_KEY` supplies the Cloud or server key unless `api_key` is set in the file.

 | Key | Default | Description |
 |-----|---------|-------------|
-| `mode` | `platform` | `platform` (Mem0 Cloud) or `oss` (self-hosted) |
-| `api_key` | none | Mem0 Platform API key, required in Platform mode. Stored in `.env` as `MEM0_API_KEY` |
-| `user_id` | `hermes-user` | Identifier that scopes memories. See cross-channel behavior below |
+| `mode` | `platform` | `platform` (Mem0 Cloud) or `oss` (self-managed, in-process). Self-hosted server routing is set via `host` |
+| `host` | none | Self-hosted Mem0 server URL. When set, the plugin talks HTTP to your server instead of the cloud |
+| `api_key` | none | Mem0 Platform API key, or the admin key of a self-hosted server. Stored in `.env` as `MEM0_API_KEY` |
+| `user_id` | gateway user ID, then `hermes-user` | Identifier that scopes memories. See cross-channel behavior below |
 | `agent_id` | `hermes` | Agent identifier attached to writes |
-| `rerank` | `true` | Rerank search results for relevance (Platform mode only) |
+| `rerank` | `false` | Platform reranking for recall and tool searches that omit `rerank` |
+| `sync_max_chars` | `450` | Per-message character cap for automatic fact extraction in every mode |
+| `oss` | `{}` | OSS LLM, embedder, and vector-store configuration |

 ### Cross-channel memories

 Hermes can run from the CLI and from gateways like Telegram, Slack, and Discord. The `user_id` setting controls how memories are scoped across them:

- **Set a `user_id`** and it applies to every gateway, so one person gets a single merged memory store no matter where they talk to the agent.
- **Leave it unset** (or at the default `hermes-user`) and each gateway uses its own native id, keeping per-platform memories separate.
+- **Set a `user_id` other than `hermes-user`** and it applies to every gateway, so one person gets a single merged memory store no matter where they talk to the agent.
+- **Leave it unset** (or at the default `hermes-user`) and each gateway uses its own native ID when available, falling back to `hermes-user`.

-Either way, every write is tagged with `metadata.channel` (for example `telegram` or `cli`), so per-channel views are still possible at query time.
+Every write is tagged with `metadata.channel` (for example `telegram` or `cli`). Plugin searches filter by user identity across sessions; they do not restrict recall to the current channel or session.

+## Migration for Existing Users
+
+Keep `memory.provider: mem0`, `mem0.json`, `MEM0_*` settings, user identity, and OSS database paths unchanged. Moving from the bundled provider to this standalone plugin does not require rerunning setup or moving stored memories.
+
+Automatic migration depends on Hermes rollout as well as this repository:
+
+1. Users need a Hermes build containing [PR #114569](https://github.com/NousResearch/hermes-agent/pull/114569).
+2. Hermes maintainers must approve a catalog entry named `mem0` with `repo: https://github.com/mem0ai/mem0`, `subdir: integrations/hermes-plugin-mem0`, and a reviewed full commit SHA.
+3. The bundled Mem0 provider must be removed so the standalone provider can load.
+
+With these in place, Hermes installs a missing configured provider during `hermes update` across profiles or at agent startup. Startup installation respects `security.allow_lazy_installs`. Offline or disabled installation needs manual action; merging the plugin directory alone does not complete automatic migration.
+
+CLI setup and status are supported. This plugin does not ship a Desktop configuration panel or provider-specific CLI commands.

 ## Reliability

- **Circuit breaker**: if Mem0 fails five times in a row, Hermes pauses calls for two minutes, then retries. The agent keeps working without memory during that window. Expected client errors, like a 404 on a missing memory id, do not count toward tripping the breaker.
- **Non-blocking**: every Mem0 call runs in a background daemon thread, so a slow or failed call never blocks your conversation.
- **Thread-safe**: the client uses lazy initialization with locking, and the background sync and prefetch threads are guarded so concurrent gateway messages cannot produce duplicate memories.
+- **Circuit breaker**: five consecutive backend failures pause calls for two minutes. The agent can continue without memory during that window. Expected update/delete errors such as a missing memory do not trip the breaker.
+- **Bounded waits**: recall waits up to three seconds. Capture runs in the background, but an overlapping turn may wait up to five seconds for the previous sync before being skipped.
+- **Graceful shutdown**: shutdown and Python process exit wait for active recall and capture workers before closing the backend. Backend network timeouts still apply. Self-hosted HTTP capture uses a 120-second read timeout and a 30-second connection timeout; other self-hosted HTTP operations use 30 seconds.
+- **Best-effort capture**: there is no durable queue. Forced termination, including Hermes' 30-second exit watchdog, can interrupt pending writes even while graceful shutdown is waiting.
+- **OSS data protection**: an embedding dimension mismatch fails initialization without deleting the existing collection or table.

 ## Troubleshooting

@@ -188,6 +249,7 @@ Either way, every write is tagged with `metadata.channel` (for example `telegram
 The circuit breaker tripped after five consecutive failures and resets after two minutes.

 - **Platform mode**: check your API key and internet connection.
+- **Self-hosted server mode**: check that the server is running and reachable at the configured `host` URL.
 - **OSS mode**: make sure your vector store (Qdrant or PGVector) is running and reachable.

 ### OSS: vector store connection refused
@@ -213,15 +275,12 @@ curl http://localhost:11434/api/tags

 - `mem0_add` stores text verbatim with no extraction. Ordinary conversation turns are extracted automatically by the background sync.
 - Search is semantic, so try a broader query.
- Confirm `user_id` is the same across sessions (check `~/.hermes/mem0.json`).
+- Confirm `user_id` is the same across sessions (check `$HERMES_HOME/mem0.json`).
+- Check `sync_max_chars`: facts beyond the per-message limit are not sent for extraction.

-## Key Features
+### OSS: embedding dimension mismatch

-1. **Two ways to run**: managed Platform or fully self-hosted OSS, switchable at any time.
-2. **Zero-latency recall**: memories are prefetched in the background and cached before you type.
-3. **Automatic extraction**: Mem0 extracts and deduplicates facts from each exchange for you.
-4. **Non-blocking and fault tolerant**: background threads plus a circuit breaker keep the agent responsive even when Mem0 is unreachable.
-5. **Additive memory**: works alongside Hermes' built-in file memory (`MEMORY.md`, `USER.md`).
+Restore the embedding model and dimensions that created the existing collection, or choose a new collection and migrate data explicitly. The plugin leaves the original collection intact when dimensions differ.

 <CardGroup cols={2}>
  <Card title="OpenClaw Integration" icon="/images/provider-icons/openclaw.svg" href="/integrations/openclaw">
@@ -0,0 +1,117 @@
+---
+title: Kimi Code
+description: "Add persistent project memory to Kimi Code with automatic capture, automatic recall, Mem0 skills, and tools."
+---
+
+Kimi Code forgets project decisions between sessions. The Mem0 plugin captures completed work, recalls relevant context before a response, and gives Kimi explicit memory tools and skills.
+
+<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 Platform account and API key:
+   - [Sign up at app.mem0.ai](https://app.mem0.ai?utm_source=oss&utm_medium=integration-kimi)
+   - [Get your API key](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-kimi) (starts with `m0-`)
+
+2. [Kimi Code](https://www.kimi.com/code) with plugin support.
+
+3. Python 3.10+ and Git on your machine.
+
+## Quick start
+
+Export the key in the shell where you start Kimi Code:
+
+```bash
+export MEM0_API_KEY='your-mem0-api-key'
+kimi
+```
+
+Inside Kimi Code, install the native plugin bundle and reload the session:
+
+```text
+/plugins install https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin
+/reload
+```
+
+Run `/plugins info mem0` to confirm that the plugin, MCP server, skills, and hooks loaded.
+
+## What you get
+
+- **Automatic capture:** Kimi records completed exchanges locally and flushes durable project knowledge to Mem0 in the background.
+- **Automatic recall:** Relevant memories are added before Kimi answers the first prompt in a session, if that prompt has at least 20 characters.
+- **Explicit search:** Kimi can call `search_memories` when it needs a more specific answer.
+- **Six memory skills:** Search, status, remember, forget, pause, and resume use the same memory behavior as the other Mem0 coding-agent plugins.
+- **Project scoping:** Memories stay attached to the repository, with separate personal and shared project lanes.
+
+Credentials are redacted before memory capture. If Mem0 is unavailable, hooks fail open so Kimi can continue its normal work.
+
+## How it works
+
+Kimi's native lifecycle events are translated into the shared Mem0 memory lifecycle:
+
+| Kimi event | What Mem0 does |
+| --- | --- |
+| `SessionStart` | Initializes the project session and recovers pending capture |
+| `UserPromptSubmit` | Records each prompt; searches on the first prompt when it has at least 20 characters |
+| `PostToolUse` / `PostToolUseFailure` | Records useful tool results and failures |
+| `Stop` | Captures the completed exchange |
+| `PreCompact` / `SessionEnd` | Flushes pending capture in the background |
+
+The plugin does not register subagent start or stop hooks or supply parent memories to child agents.
+
+## Verify the plugin
+
+In one session, say:
+
+```text
+Remember exactly: the release codename for this repository is ORCHID-9274.
+```
+
+Start a new Kimi session in the same repository and ask:
+
+```text
+What is the release codename for this repository? Do not infer it from repository files.
+```
+
+Kimi should return `ORCHID-9274` from memory.
+
+## Managing the plugin
+
+```text
+/plugins list
+/plugins info mem0
+/plugins disable mem0
+/plugins enable mem0
+/plugins remove mem0
+```
+
+Run `/reload` or start a new session after enabling, disabling, or reinstalling the plugin.
+
+## 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
+
+| Problem | Fix |
+| --- | --- |
+| Missing API key | Start Kimi from a shell where `MEM0_API_KEY` is exported. |
+| Plugin changes do not appear | Run `/plugins reload`, then `/reload` or `/new`. |
+| MCP server is disabled | Run `/plugins mcp enable mem0 mem0`, then `/reload`. |
+| No memory in a later session | Wait a moment for the background flush, then ask Kimi to search memory explicitly. |
+| Remove the plugin | Run `/plugins remove mem0`. |
+
+<CardGroup cols={2}>
+  <Card title="Cursor" icon="arrow-pointer" href="/integrations/cursor">
+    Add the same persistent project memory to Cursor
+  </Card>
+  <Card title="Claude Code" icon="/images/provider-icons/anthropic.svg" href="/integrations/claude-code">
+    Use Mem0 with Claude Code and its isolated sidekick
+  </Card>
+</CardGroup>
+
+<Snippet file="star-on-github.mdx" />
@@ -1,7 +1,6 @@
 ---
-title: Langchain
-seo:
-  title: "LangChain Integration with Mem0"
+title: "LangChain Integration"
+sidebarTitle: "Langchain"
 description: "Build personalized AI agents using LangChain for conversation flow and Mem0 for long-term memory retention."
 ---

@@ -45,7 +45,7 @@ memory_from_client = Mem0Memory.from_client(
 )
 ```

-Context is used to identify the user, agent or the conversation in the Mem0. It is required to be passed in the at least one of the fields in the `Mem0Memory` constructor. It can be any of the following:
+Context is used to identify the user, agent or the conversation in the Mem0. It is required to be passed in at least one of the fields in the `Mem0Memory` constructor. It can be any of the following:

 ```python
 context = {
@@ -1,7 +1,6 @@
 ---
-title: n8n
-seo:
-  title: "n8n Integration with Mem0"
+title: "n8n Integration"
+sidebarTitle: "n8n"
 description: "Add long-term memory to n8n workflows and AI Agents with the Mem0 community node, no code required."
 ---

@@ -5,6 +5,10 @@ description: "Add long-term memory to OpenClaw agents using the Mem0 plugin with

 Add long-term memory to [OpenClaw](https://github.com/openclaw/openclaw) agents with the `@mem0/openclaw-mem0` plugin. Your agent forgets everything between sessions. This plugin fixes that by automatically watching conversations, extracting what matters, and bringing it back when relevant.

+<Info>Current package version: `1.1.0`.</Info>
+
+Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent). OpenClaw subagents can recall parent memories. Mem0 does not capture their sessions.
+
 ## Overview

 <Frame>
@@ -14,11 +18,12 @@ Add long-term memory to [OpenClaw](https://github.com/openclaw/openclaw) agents
 The plugin provides:
 1. **Triage**: The agent extracts durable facts from conversations using a structured protocol with importance gates and domain overlays
 2. **Recall**: Before each turn, relevant memories are retrieved with reranking and injected into context
-3. **Dream**: Periodic memory consolidation merges duplicates, resolves conflicts, prunes stale entries
-4. **Agent Tools**: Eight tools for explicit memory operations during conversations
+3. **Agent Tools**: Eight tools for explicit memory operations during conversations

 Skills mode, `autoRecall`, and `autoCapture` are all enabled by default during `openclaw mem0 init`.

+Automatic capture preserves the full text of selected user and assistant messages after noise filtering and secret redaction, without a per-message character cutoff. It selects recent messages and earlier work summaries; it does not capture every message in the conversation.
+
 ## Requirements

 Check your OpenClaw version:
@@ -101,7 +106,7 @@ You no longer need manual config editing to get started. Everything happens insi
  </Step>
 </Steps>

-That's it. No API key, no config file editing, no environment variables. The plugin is now active with skills-based memory (triage, recall, and dream) running automatically.
+That's it. No API key, no config file editing, no environment variables. The plugin is now active with skills-based memory (triage and recall) running automatically.

 <Note>The chat flow uses the same underlying config as manual setup: it writes `apiKey`, `userId`, and `skills` config into `openclaw.json` for you. You can still open the file to inspect or override values afterward.</Note>

@@ -142,7 +147,6 @@ That's it. No API key, no config file editing, no environment variables. The plu
                  "keywordSearch": true,
                  "identityAlwaysInclude": true
                },
-                "dream": { "enabled": true },
                "domain": "companion"
              }
            }
@@ -341,8 +345,8 @@ openclaw mem0 status --json
 |-----|------|---------|-------------|
 | `mode` | `"platform"` \| `"open-source"` | `"platform"` | Which backend to use |
 | `userId` | `string` | OS username | Scope memories per user |
-| `autoRecall` | `boolean` | `true` | Inject memories before each turn. Ignored when `skills` is configured. |
-| `autoCapture` | `boolean` | `true` | Store facts after each turn. Ignored when `skills` is configured. |
+| `autoRecall` | `boolean` | `true` | Inject memories before each turn, including when skills mode is configured. |
+| `autoCapture` | `boolean` | `true` | Store facts after each turn, including when skills mode is configured. |
 | `topK` | `number` | `5` | Max memories per recall |
 | `searchThreshold` | `number` | `0.3` | Min similarity (0–1) |

@@ -441,7 +445,7 @@ If `openclaw plugins update` fails:

 ### Auto-Capture and Auto-Recall

-Auto-capture and auto-recall are **enabled by default**. When skills mode is configured (the default after `openclaw mem0 init`), these are ignored in favor of the skills-based triage/recall/dream protocol.
+Auto-capture and auto-recall are **enabled by default**. They also run when skills mode is configured (the default after `openclaw mem0 init`). Set `autoRecall` or `autoCapture` to `false` to disable the corresponding automatic hook while using skills.

 To disable either:

@@ -464,13 +468,12 @@ The agent can always use memory tools (`memory_add`, `memory_search`, etc.) expl

 ### Credential Protection

-The plugin never stores API keys, tokens, or secrets as memories. Five independent layers enforce this:
+The plugin never stores API keys, tokens, or secrets as memories. Four independent layers enforce this:

 1. **Triage gate**: The extraction prompt rejects values matching known credential patterns (`sk-`, `m0-`, `ghp_`, `AKIA`, `Bearer`, `password=`, `token=`, `secret=`)
-2. **Dream cleanup**: Periodic memory consolidation deletes any memories that slipped through containing credential patterns
-3. **Extraction instructions**: Default extraction rules explicitly instruct the model to store only that a credential was configured, never the value
-4. **Configurable patterns**: Add custom credential patterns via `skills.triage.credentialPatterns`
-5. **CLI redaction**: `openclaw mem0 config show` redacts sensitive fields (`apiKey`, `oss.*.config.apiKey`)
+2. **Extraction instructions**: Default extraction rules explicitly instruct the model to store only that a credential was configured, never the value
+3. **Configurable patterns**: Add custom credential patterns via `skills.triage.credentialPatterns`
+4. **CLI redaction**: `openclaw mem0 config show` redacts sensitive fields (`apiKey`, `oss.*.config.apiKey`)

 ### API Key Storage

@@ -478,7 +481,9 @@ Plugin config is stored in `~/.openclaw/openclaw.json` with file permissions `0o

 ### Telemetry

-Anonymous usage telemetry (PostHog) is enabled by default to help improve the plugin. No conversation content or memory values are included, only event counts (recall, capture, tool usage, CLI commands).
+Usage telemetry (PostHog) is enabled by default to help improve the plugin. No conversation content or memory values are included, only event counts (recall, capture, tool usage, CLI commands).
+
+These events are **not anonymous**. OpenClaw does not send your account email the way the SDK does, but it does send an unsalted SHA-256 hash of it, falling back to a hash of the API key and then to a random per-machine id. Mem0 holds the email the hash is derived from, so the hash identifies your account rather than concealing it. The first run that resolves an account also emits a PostHog `$identify`, which permanently merges any earlier random id into that identity.

 To opt out, set the environment variable:

@@ -5,6 +5,10 @@ description: "Add persistent memory to OpenCode with the Mem0 plugin: native SDK

 Add persistent memory to [**OpenCode**](https://opencode.ai) with the Mem0 plugin. Your agent forgets everything between sessions. Mem0 fixes that by storing decisions, preferences, and learnings so they carry over automatically.

+<Info>Current package version: `0.3.0`.</Info>
+
+Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+
 ## Prerequisites

 1. A Mem0 API key (starts with `m0-`):
@@ -33,7 +37,7 @@ opencode plugin @mem0/opencode-plugin
 **Or let your agent do it**: paste this into OpenCode:

 ```
-Install @mem0/opencode-plugin by following https://raw.githubusercontent.com/mem0ai/mem0/main/integrations/mem0-plugin/.opencode-plugin/README.md
+Install @mem0/opencode-plugin by following https://raw.githubusercontent.com/mem0ai/mem0/main/integrations/opencode-plugin/README.md
 ```

 This adds the plugin to your `~/.config/opencode/opencode.json`. Restart OpenCode. You get the native memory tools, lifecycle hooks, and all `/mem0-*` slash commands. The memory tools are registered by the plugin itself via the `mem0ai` SDK. No MCP server to configure.
@@ -61,9 +65,9 @@ If you only need the memory tools without the plugin's hooks or skills, point Op

 | Component | Plugin (A) | Standalone MCP (B) |
 |-----------|:----------:|:------------------:|
-| 9 memory tools | Native (SDK) | Remote MCP server |
+| 10 memory tools | Native (SDK) | 9 remote MCP tools |
 | Lifecycle Hooks | Yes | No |
-| 9 Skills | Yes | No |
+| 7 Skills | Yes | No |

 ## Available Memory Tools

@@ -78,6 +82,7 @@ If you only need the memory tools without the plugin's hooks or skills, point Op
 | `delete_all_memories` | Bulk delete all memories in scope |
 | `delete_entities` | Delete a user/agent/app/run entity and its memories |
 | `list_entities` | List users/agents/apps/runs stored in Mem0 |
+| `get_event_status` | Check the processing status of an asynchronous memory event |

 ## Memory scope

@@ -87,9 +92,9 @@ If you only need the memory tools without the plugin's hooks or skills, point Op
 |-------|-------|--------|
 | `project` *(default)* | this repo (`user_id` + `app_id`) | this repo |
 | `session` | this run only (`+ run_id`) | this run |
-| `global` | **all your projects in the workspace** (`app_id: "*"`) | user-wide |
+| `global` | **all your projects in the workspace** (filtered by your user ID) | user-wide |

-Ask naturally, for example, *"search my memories across all my projects"*. The agent passes `scope: "global"`. For normal questions it stays scoped to the current project automatically.
+Select `/mem0-scope global` before requesting a cross-project tool operation. A tool cannot enable global scope by supplying an argument alone. Switch back with `/mem0-scope project` when finished.

 To change the **default** scope (used when no scope is passed), run the `/mem0-scope` skill:

@@ -110,30 +115,14 @@ The plugin uses the [mem0ai](https://www.npmjs.com/package/mem0ai) TypeScript SD
 | OpenCode Event | Hook | What happens |
 |----------------|------|-------------|
 | `config` | **Config** | Registers the `/mem0-*` slash commands (`config.command`) and adds the plugin's own `opencode-skills/` dir to OpenCode's `skills.paths` for in-place skill discovery (no copying) |
-| `chat.message` | **Chat message** | Searches prior memories on session start, searches relevant memories before each prompt, auto-captures learnings periodically |
+| `chat.message` | **Chat message** | Searches prior memories on session start, searches relevant memories before each prompt, sends every third qualifying user prompt for extraction |
 | `tool.execute.before` | **Pre-tool** | Blocks MEMORY.md writes, steering them to the `add_memory` tool |
 | `tool.execute.after` | **Post-tool** | Scans Bash errors and pre-fetches related error memories |
 | `experimental.chat.messages.transform` | **Messages transform** | Injects memory context (session memories, search results, error lookups) into the prompt |
-| `experimental.session.compacting` | **Compaction** | Stores session state memory, then injects prior memories into compaction context so nothing is lost |
+| `experimental.session.compacting` | **Compaction** | Stores session state memory, then injects prior memories into compaction context |
 | `shell.env` | **Shell env** | Exports `MEM0_USER_ID`, `MEM0_APP_ID`, `MEM0_SESSION_ID`, and `MEM0_BRANCH` to all shell executions |

-## Auto-dream (memory consolidation)
-
-The plugin can automatically consolidate stored memories by merging duplicates, dropping stale/sensitive entries, and rewriting vague ones. This keeps your memory set clean over time. It runs at most once per session, and only when **all** gates pass:
-
- **Time**: at least `minHours` (default 24) since the last consolidation
- **Sessions**: at least `minSessions` (default 5) sessions since then
- **Memories**: at least `minMemories` (default 20) stored for the project
-
-A filesystem lock (`~/.mem0/mem0-dream.lock`) keeps two sessions from consolidating at once. Tune the thresholds with a `dream` block in `~/.mem0/settings.json`, or disable entirely with `MEM0_DREAM=false`:
-
-```json
-{
-  "dream": { "enabled": true, "auto": true, "minHours": 24, "minSessions": 5, "minMemories": 20 }
-}
-```
-
-If auto-dream hasn't run yet, it's almost always because a gate hasn't been met (most often too few memories). Run `/mem0-status` to see the exact gate progress (e.g. `sessions 2/5, memories 3/20`), `/mem0-dream` to consolidate **now** regardless of the gates, or lower the thresholds above.
+Automatic capture sends the selected user prompt with its full redacted text, without a per-message character cutoff. It does not capture every prompt or the full assistant transcript. These automatic writes use user and project scope, with the session ID in `metadata.session_id`; session-scoped tools use top-level `run_id`. A session-scoped search therefore does not include automatic writes that lack `run_id`.

 ## Troubleshooting

@@ -141,7 +130,6 @@ If auto-dream hasn't run yet, it's almost always because a gate hasn't been met
 - **"Connection failed"**: Verify your key is set: `echo $MEM0_API_KEY`
 - **Plugin not loading**: Run `opencode plugin @mem0/opencode-plugin` again, then restart
 - **Hooks not firing**: Hooks require the plugin install (Option A). MCP-only installs don't include hooks.
- **Auto-dream never runs**: It's gated (time + sessions + memories). Run `/mem0-status` to see which gate is blocking, or `/mem0-dream` to consolidate now.
 - **Wrong project name / memories not found**: The project id comes from your git remote; launch OpenCode from inside the repo (not your home directory). Check the resolved id with `/mem0-status`.

 <CardGroup cols={2}>
@@ -1,19 +1,22 @@
 ---
 title: Pi Agent
-description: "Add persistent memory to Pi Agent with the Mem0 plugin semantic search, auto-capture, and dream consolidation."
+description: "Add persistent memory to Pi Agent with the Mem0 plugin, semantic search, and automatic capture."
 ---

 Add persistent memory to [**Pi Agent**](https://pi.dev) with `@mem0/pi-agent-plugin`. Your agent forgets everything between sessions. This plugin fixes that by automatically capturing knowledge from conversations, storing it in Mem0's cloud memory layer, and retrieving relevant context before every response.

+<Info>Current package version: `0.3.0`.</Info>
+
+Sidekick is available only in the [Claude Code plugin](/integrations/claude-code#sidekick-agent).
+
 ## Overview

 The plugin provides:
 1. **Auto-capture**: Extracts durable facts from both user and assistant messages automatically
-2. **Semantic recall**: Retrieves relevant memories via the `mem0_memory` tool before each response
-3. **Dream consolidation**: Periodic maintenance: merges duplicates, resolves contradictions, prunes stale entries
-4. **Monorepo-aware scoping**: Uses git root for project detection, consistent across subdirectories
-5. **Confirmation dialogs**: Destructive commands ask before acting via Pi's built-in UI
-6. **8 skills + 8 commands**: Essential memory management from slash commands and agent-guided workflows
+2. **Semantic recall**: Automatically searches project memories before each agent turn; `mem0_memory` supports additional explicit searches
+3. **Monorepo-aware scoping**: Uses git root for project detection, consistent across subdirectories
+4. **Confirmation dialogs**: Destructive commands ask before acting via Pi's built-in UI
+5. **6 skills + 6 commands**: Essential memory management from slash commands and agent-guided workflows

 ## Prerequisites

@@ -59,14 +62,7 @@ For advanced settings, create `~/.pi/agent/mem0-config.json`:
  "userId": "your-username",
  "autoCapture": true,
  "defaultScope": "project",
-  "searchThreshold": 0.3,
-  "dream": {
-    "enabled": true,
-    "auto": true,
-    "minHours": 24,
-    "minSessions": 5,
-    "minMemories": 20
-  }
+  "searchThreshold": 0.3
 }
 ```

@@ -76,12 +72,7 @@ For advanced settings, create `~/.pi/agent/mem0-config.json`:
 | `userId` | `string` | `$MEM0_USER_ID` or `"default"` | User identity for memory scoping |
 | `autoCapture` | `boolean` | `true` | Store facts from conversations automatically |
 | `defaultScope` | `string` | `"project"` | Default memory scope: `project`, `session`, or `global` |
-| `searchThreshold` | `number` | `0.3` | Minimum similarity score (0–1) a memory must reach to count as a match for `/mem0-search`, `/mem0-forget`, and `/mem0-pin`, enforced on each result's relevance score. Raise it to be stricter; lower it if relevant results are missed. |
-| `dream.enabled` | `boolean` | `true` | Enable dream consolidation |
-| `dream.auto` | `boolean` | `true` | Auto-trigger dreams when thresholds are met |
-| `dream.minHours` | `number` | `24` | Minimum hours between auto-dreams |
-| `dream.minSessions` | `number` | `5` | Minimum sessions before first auto-dream |
-| `dream.minMemories` | `number` | `20` | Minimum memories before auto-dream triggers |
+| `searchThreshold` | `number` | `0.3` | Minimum similarity score (0–1) a memory must reach to count as a match for `/mem0-search` and `/mem0-forget`, enforced on each result's relevance score. Raise it to be stricter; lower it if relevant results are missed. |


 ## What's Included
@@ -89,11 +80,10 @@ For advanced settings, create `~/.pi/agent/mem0-config.json`:
 | Component | Description |
 |-----------|-------------|
 | `mem0_memory` tool | Agent-callable tool for search, add, get_all, delete, delete_all |
-| 8 slash commands | Essential memory management from the command line |
-| 8 skills | Guide the agent on how to use each capability |
+| 6 slash commands | Essential memory management from the command line |
+| 6 skills | Guide the agent on how to use each capability |
 | Auto-capture | Extracts and stores facts on every `agent_end` event |
 | System prompt | Appends memory policy to every agent turn |
-| Dream consolidation | Automated memory maintenance with session/time/count gates |

 ## Agent Tool

@@ -119,8 +109,6 @@ Tool output is truncated to 200 lines / 50KB to prevent context overflow.
 | `/mem0-forget <query>` | Search and delete memories (with confirmation dialog) |
 | `/mem0-search <query>` | Semantic search across memories |
 | `/mem0-tour [scope]` | Browse all memories grouped by category |
-| `/mem0-dream` | Consolidate: merge duplicates, prune stale, resolve contradictions |
-| `/mem0-pin <query>` | Pin a memory to protect from dream pruning (preserves memory ID) |
 | `/mem0-scope <scope>` | Change default scope for this session (project, session, global) |
 | `/mem0-status` | Connection health, identity, and memory count |

@@ -131,28 +119,19 @@ Memories are scoped using Mem0's `user_id`, `app_id`, and `run_id` parameters:
 | Scope | Filters | Use Case |
 |-------|---------|----------|
 | `project` | user_id + app_id (git root) | **Default.** Project-specific knowledge: decisions, architecture, config |
-| `session` | user_id + app_id + run_id | Ephemeral context for the current session only |
+| `session` | user_id + app_id + run_id | Memories saved with the current session ID (no automatic expiration) |
 | `global` | user_id only | All memories across all your projects |

-The `app_id` is auto-detected from the git repository root (`git rev-parse --show-toplevel`), so all subdirectories within a monorepo share the same memory pool. Falls back to the working directory name for non-git directories. The `run_id` is derived from Pi's session file path.
+The `app_id` is auto-detected from the git repository root (`git rev-parse --show-toplevel`), so all subdirectories within a monorepo share the same memory pool. Falls back to the working directory name for non-git directories. The `run_id` is derived from Pi's session file path. Automatic recall and capture use project scope, regardless of `defaultScope`; automatic writes do not include `run_id`. Use session-scoped tools or commands to save and recall session-specific memories. Captured user and assistant message text is redacted without a per-message character cutoff.

-## Dream Consolidation
+Global tool operations require `/mem0-scope global` or `defaultScope: "global"` in plugin configuration. A model-supplied `scope` argument cannot enable cross-project access on its own. Empty or wildcard user, project, and session identities are rejected.

-### Confirmation Dialogs
+## Confirmation Dialogs

 Destructive and mutating commands use Pi's built-in `ctx.ui.confirm()` dialog before acting:

 - `/mem0-forget` asks "Delete this memory?" before deleting a single match
- `/mem0-pin` asks "Pin this memory?" before modifying it
- Cancelling either operation is always safe. No changes are made
-
-### Pin
-
-`/mem0-pin` uses Mem0's `update()` API to prepend `[PINNED]` to the memory text. This preserves the original memory ID. There is no add+delete cycle that would lose history or change the UUID.
-
-### Dream Consolidation
-
-The plugin includes automated memory maintenance ("dream") that merges duplicates, resolves contradictions, and prunes stale entries. When enabled, dreams auto-trigger after enough sessions, time, and memories accumulate (configurable via `dream.*` settings). Run `/mem0-dream` to trigger consolidation manually at any time. Pinned memories (via `/mem0-pin`) are protected from pruning.
+- Cancelling the operation is always safe. No changes are made.

 ## Example Workflow

@@ -169,10 +148,9 @@ You: What do you know about my preferences?
 ## Troubleshooting

 - **"No API key found"**: Verify `MEM0_API_KEY` is set: `echo $MEM0_API_KEY`. If empty, add it to your shell profile (see Prerequisites)
- **Extension not loading**: Check Pi startup output for errors. Run `pi -e ./src/entry.ts` from the plugin directory for verbose output
+- **Extension not loading**: Check Pi startup output for errors. For a source checkout, run `pnpm build`, then `pi -e ./dist/entry.js` from the plugin directory
 - **Memories not capturing**: Verify `autoCapture` is `true` (default). Check `/mem0-status` for connection health
 - **Wrong project detected**: The plugin uses the git repository root as `app_id`. If not in a git repo, it falls back to the working directory name. Run `/mem0-status` to see the detected project
- **Dream not triggering**: All three gates must pass (time, sessions, memories). Use `/mem0-dream` to force it manually

 <CardGroup cols={2}>
  <Card title="Claude Code Integration" icon="/images/provider-icons/anthropic.svg" href="/integrations/claude-code">
@@ -63,7 +63,7 @@ mode: "custom"
          Add memory to your coding agent
        </h3>
        <p className="text-sm text-gray-600 dark:text-zinc-400">
-          Plugins that let Claude Code, Cursor, Codex, and other harnesses remember your project. Opens the Claude Code guide.
+          Start with Claude Code, then choose the individual guide for Cursor, Codex, Kimi Code, OpenCode, OpenClaw, Pi Agent, DeepSeek Harness, or Antigravity.
        </p>
      </div>
    </a>
@@ -171,6 +171,7 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
 - [Introduction](https://docs.mem0.ai/introduction) [Both]: Use when the user wants a one-page overview of how memory fits between the LLM and the app.
 - [Vibe Code with Mem0](https://docs.mem0.ai/vibecoding) [Both]: Use when the user is in Claude Code, Cursor, or Windsurf and wants memory wired into their editor.
 - [Platform Overview](https://docs.mem0.ai/platform/overview) [Platform]: Use when the user picks the managed product - 4-line integration, hosted API, dashboard.
+- [Mem0 Copilot](https://docs.mem0.ai/platform/copilot) [Platform]: Use when inspecting project memories, reviewing configuration changes, or testing extraction in the dashboard.
 - [Sign up as an agent](https://docs.mem0.ai/platform/agent-signup) [Platform]: Use when an AI agent needs to mint a Mem0 API key autonomously - four commands, no email or dashboard, human claims ownership later.
 - [Platform vs Open Source](https://docs.mem0.ai/platform/platform-vs-oss) [Both]: Use when the user is deciding between managed and self-hosted.
 - [Platform Quickstart](https://docs.mem0.ai/platform/quickstart) [Platform]: Use for the first Platform integration - API key plus `MemoryClient.add/search`.
@@ -185,7 +186,6 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
 ## Core Concepts

 - [How Mem0 Works](https://docs.mem0.ai/core-concepts/how-it-works) [Both]: Use when explaining the end-to-end pipeline: extraction (ADD-only distillation), storage across vector/entity/history stores, and multi-signal retrieval.
- [Memory Types](https://docs.mem0.ai/core-concepts/memory-types) [Both]: Use when checking which `memory_type` values actually work: `procedural_memory` is implemented, `semantic_memory` and `episodic_memory` are defined in the enum but rejected by validation.
 - [Memory Operations - Add](https://docs.mem0.ai/core-concepts/memory-operations/add) [Both]: Use when explaining how `add()` extracts facts, resolves conflicts, and writes to both stores.
 - [Memory Operations - Search](https://docs.mem0.ai/core-concepts/memory-operations/search) [Both]: Use when explaining how queries are processed and ranked.
 - [Memory Operations - Update](https://docs.mem0.ai/core-concepts/memory-operations/update) [Both]: Use when memories need to be edited in place or reconciled against new info.
@@ -197,6 +197,7 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
 ### Features - Essential
 - [V2 Memory Filters](https://docs.mem0.ai/platform/features/v2-memory-filters) [Platform]: Use when compound filters (AND/OR on metadata, entity, time) are needed at search.
 - [Entity-Scoped Memory](https://docs.mem0.ai/platform/features/entity-scoped-memory) [Platform]: Use when partitioning memories by user, agent, app, or run.
+- [Profiles](https://docs.mem0.ai/platform/features/user-profiles) [Platform]: Use when a structured always-current summary of a user is needed in one read, instead of searching their memories.
 - [Graph Memory](https://docs.mem0.ai/platform/features/graph-memory) [Platform]: Use when connecting facts across memories through shared entities for entity-centric or multi-hop questions.
 - [Async Client](https://docs.mem0.ai/platform/features/async-client) [Platform]: Use when the app issues many concurrent Mem0 calls and needs non-blocking I/O.
 - [Multimodal Support](https://docs.mem0.ai/platform/features/multimodal-support) [Platform]: Use when storing images or PDFs as memory input.
@@ -255,25 +256,25 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
 - [Agno](https://docs.mem0.ai/integrations/agno) [Platform]: Use when the user is on Agno.
 - [Camel AI](https://docs.mem0.ai/integrations/camel-ai) [Both]: Use when the user is on Camel AI.
 - [ChatDev](https://docs.mem0.ai/integrations/chatdev) [Platform]: Use when the user is on ChatDev.
- [Hermes](https://docs.mem0.ai/integrations/hermes) [Both]: Use when the user is on Hermes.
- [Pi Agent](https://docs.mem0.ai/integrations/pi-agent) [Platform]: Use when adding persistent memory to Pi Agent with the Mem0 plugin.
- [DeepSeek Harness](https://docs.mem0.ai/integrations/deepseek-plugin) [Platform]: Use when adding persistent memory to the DeepSeek Harness (Cordis) agent via the Mem0 plugin.
+- [Hermes](https://docs.mem0.ai/integrations/hermes) [Both]: Use when installing or configuring the standalone Hermes memory plugin, or migrating from the bundled Mem0 provider.
+- [Pi Agent](https://docs.mem0.ai/integrations/pi-agent) [Platform]: Use when adding automatic capture, prompt recall, scoped memory, and six memory commands to Pi Agent.
+- [DeepSeek Harness](https://docs.mem0.ai/integrations/deepseek-plugin) [Platform]: Use when adding automatic recall, completed-turn capture, and native search/add tools to DeepSeek Harness.
 - [OpenAI Agents SDK](https://docs.mem0.ai/integrations/openai-agents-sdk) [Platform]: Use when the user is on the OpenAI Agents SDK.
 - [Google AI ADK](https://docs.mem0.ai/integrations/google-ai-adk) [Platform]: Use when the user is on Google's Agent Development Kit.
 - [Mastra](https://docs.mem0.ai/integrations/mastra) [Platform]: Use when the user is on Mastra (TypeScript).
- [OpenClaw](https://docs.mem0.ai/integrations/openclaw) [Both]: Use when wiring Mem0 into Claude Code or editors via OpenClaw.
+- [OpenClaw](https://docs.mem0.ai/integrations/openclaw) [Both]: Use when adding persistent memory to OpenClaw agents with Mem0 Platform or a self-hosted backend.
 - [Vercel AI SDK](https://docs.mem0.ai/integrations/vercel-ai-sdk) [Both]: Use when the user is on the Vercel AI SDK.
- [Eve](https://docs.mem0.ai/integrations/eve) [Platform]: Use when adding Mem0 as a first-class Eve memory provider (`@mem0/eve`, `mem0Provider`, hand-written `agent/memory/mem0.ts`). `eve add memory/mem0` is not available yet. Not the Mem0 MCP connection (`eve add connection/mem0`).
 - [Vercel](https://docs.mem0.ai/integrations/vercel) [Platform]: Use when deploying on Vercel and installing Mem0 from the Vercel Marketplace.
 - [Strands Agents](https://docs.mem0.ai/integrations/strands) [Both]: Use when the user is on AWS Strands and wants a native MemoryStore.

 ### AI Coding Tools
- [Claude Code](https://docs.mem0.ai/integrations/claude-code) [Both]: Use when wiring memory into Claude Code.
+- [Claude Code](https://docs.mem0.ai/integrations/claude-code) [Platform]: Use when wiring memory into Claude Code.
 - [Claude.ai](https://docs.mem0.ai/integrations/claude-ai) [Platform]: Use when connecting Mem0 to Claude.ai (the hosted web app) via a custom remote MCP connector, or when Claude's native memory seems to be crowding out mem0 tool calls.
- [Cursor](https://docs.mem0.ai/integrations/cursor) [Platform]: Use when wiring memory into Cursor.
- [Codex](https://docs.mem0.ai/integrations/codex) [Platform]: Use when wiring memory into Codex / other editor assistants.
- [OpenCode](https://docs.mem0.ai/integrations/opencode) [Platform]: Use when wiring memory into OpenCode.
- [Antigravity](https://docs.mem0.ai/integrations/antigravity) [Platform]: Use when wiring memory into Google Antigravity.
+- [Cursor](https://docs.mem0.ai/integrations/cursor) [Platform]: Use when adding lifecycle capture, explicit memory recall, and six memory skills to Cursor.
+- [Codex](https://docs.mem0.ai/integrations/codex) [Platform]: Use when adding automatic capture and recall, six memory skills, and a search tool to OpenAI Codex.
+- [Kimi Code](https://docs.mem0.ai/integrations/kimi) [Platform]: Use when adding persistent project memory to Kimi Code through its native plugin lifecycle.
+- [OpenCode](https://docs.mem0.ai/integrations/opencode) [Platform]: Use when adding ten native SDK memory tools, automatic context, seven skills, and project scoping to OpenCode.
+- [Antigravity](https://docs.mem0.ai/integrations/antigravity) [Platform]: Use when adding lifecycle capture, explicit recall, and six memory skills to Google Antigravity.

 ### Voice & Real-time
 - [LiveKit](https://docs.mem0.ai/integrations/livekit) [Platform]: Use when building real-time voice/video with memory.
@@ -325,6 +326,7 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
 - [Healthcare Google ADK](https://docs.mem0.ai/cookbooks/integrations/healthcare-google-adk) [Platform]: Use when the domain is medical and the framework is Google ADK.
 - [AWS Bedrock](https://docs.mem0.ai/cookbooks/integrations/aws-bedrock) [OSS]: Use when deploying with AWS managed model services.
 - [Tavily Search](https://docs.mem0.ai/cookbooks/integrations/tavily-search) [Platform]: Use when the agent layers web search on memory.
+- [Company Brain (Mem0 Platform + Supabase)](https://docs.mem0.ai/cookbooks/integrations/supabase) [Platform]: Use to build a shared org brain on Mem0 Platform with Supabase as system of record and the MCP server as the access layer (with a new-hire onboarding demo).

 ### Framework Examples
 - [LlamaIndex React](https://docs.mem0.ai/cookbooks/frameworks/llamaindex-react) [Both]: Use when building a React UI with LlamaIndex and memory.
@@ -362,6 +364,11 @@ All API Reference docs describe Mem0 Platform REST endpoints (requires API key).
 ### Entities
 - [Get Users](https://docs.mem0.ai/api-reference/entities/get-users) [Platform]: Use when listing users, agents, or apps known to a project.
 - [Delete User](https://docs.mem0.ai/api-reference/entities/delete-user) [Platform]: Use when removing an entity and all its memories.
+- [Get Profile](https://docs.mem0.ai/api-reference/profiles/get-profile) [Platform]: Use when reading a user's structured profile and branching on its generation status.
+- [Get Profile Settings](https://docs.mem0.ai/api-reference/profiles/get-profile-settings) [Platform]: Use when checking the project's profile schema, instructions, or enabled flag.
+- [Update Profile Settings](https://docs.mem0.ai/api-reference/profiles/update-profile-settings) [Platform]: Use when defining or changing the JSON Schema that shapes profiles for a project.
+- [Generate Profiles](https://docs.mem0.ai/api-reference/profiles/generate-profiles) [Platform]: Use when building profiles now: a sample of ten, or one entity.
+- [Get Generation Job](https://docs.mem0.ai/api-reference/profiles/get-profile-job) [Platform]: Use when checking how far a generation has got, and whether it finished.

 ### Organizations
 - [Create Organization](https://docs.mem0.ai/api-reference/organization/create-org) [Platform]: Use when setting up a new org.
@@ -418,22 +425,25 @@ Each subdirectory is a Claude Code Skill (`SKILL.md` + supporting assets). Load

 Source: https://github.com/mem0ai/mem0/tree/main/integrations/claude-code-plugin

-The `integrations/claude-code-plugin/` directory is the Claude Code plugin (v0.3.0, installs as `mem0@mem0-plugins`). It captures evidence locally through lifecycle hooks, extracts memories in a detached background worker, and exposes a single local MCP tool, `search_memories`, plus six `/mem0:*` skills and the `mem0:sidekick` agent. Pure-stdlib Python, nothing to install.
+The self-contained Claude Code plugin lives in `integrations/claude-code-plugin/` (v0.3.1, installs as `mem0@mem0-plugins`). It captures evidence locally through lifecycle hooks, extracts memories in a detached background worker, and exposes a single local MCP tool, `search_memories`, plus six `/mem0:*` skills and `mem0:sidekick`, available only in Claude Code. Pure-stdlib Python, nothing to install.

-### Editor Plugin (shared glue)
+### Coding-Agent Plugin Sources

-Source: https://github.com/mem0ai/mem0/tree/main/integrations/mem0-plugin
+Source: https://github.com/mem0ai/mem0/tree/main/integrations/agent-plugin-core

-The `integrations/mem0-plugin/` directory provides MCP server connection, lifecycle hooks, and skill bundling for Cursor, Codex, Kimi, Antigravity, and OpenCode. It exposes 9 MCP tools: `add_memory`, `search_memories`, `get_memories`, `get_memory`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`. Claude Code moved to `integrations/claude-code-plugin/` in v0.3.0; do not run both at the same time.
+The `integrations/agent-plugin-core/` directory is the single source for shared Python and TypeScript memory behavior. Native plugins live in their own sibling directories, while `integrations/mem0-agent-plugin/` is the single portable Agent Plugins v1 package. Sidekick is available only in Claude Code. The portable package provides search and skills but no automatic capture; its remember skill cannot save a new memory on its own. Shared Python search accepts optional `run_id` for session-specific recall in every scope. TypeScript integrations reuse the core's lifecycle, formatting, identity, scoping, and telemetry utilities while keeping their public packages and native host APIs unchanged.

 Editor-specific setup docs (already listed above under `## Integrations > AI Coding Tools`):

- `integrations/claude-code` [Both]
+- `integrations/claude-code` [Platform]
 - `integrations/cursor` [Platform]
 - `integrations/codex` [Platform]
+- `integrations/kimi` [Platform]
 - `integrations/opencode` [Platform]
 - `integrations/antigravity` [Platform]
 - `integrations/openclaw` [Both]
+- `integrations/pi-agent` [Platform]
+- `integrations/deepseek-plugin` [Platform]

 ### MCP Endpoints

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