test(profiles): use placeholder ids in the job response fixture

The fixture carried a real job_id and event_id from a live generation. The shape is what the test needs, not the values, and this repo is public.
docs(profiles): match the job create response in openapi
2026-09-23 10:49:16 -07:00 · 2026-09-23 10:29:15 -07:00 · 2026-09-23 22:56:48 +05:30 · 2026-09-23 19:53:41 +05:30 · 2026-09-23 19:53:34 +05:30 · 2026-09-23 19:50:48 +05:30
510 changed files with 44258 additions and 20696 deletions
@@ -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 to Claude workflows.",
-      "version": "0.2.15"
+      "source": "./integrations/claude-code-plugin",
+      "description": "Cross-session memory and token savings for coding agents.",
+      "version": "0.3.1"
    }
  ]
 }
@@ -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.1"
    }
  ]
 }
@@ -18,8 +18,9 @@ Package workflows keep their own push-to-main and manual triggers. Their `pull_r
 | Python CLI | `cli-python-ci.yml` | Push to main (`cli/python/`), manual | Ruff + pytest + hatch build on Python 3.10, 3.11, 3.12 |
 | Node CLI | `cli-node-ci.yml` | Push to main (`cli/node/`), manual | Biome + tsc + vitest + tsup on Node 20, 22 |
 | OpenClaw | `openclaw-checks.yml` | Push to main (`integrations/openclaw/`), manual | tsc + vitest (Codecov) + tsup on Node 20, 22 |
-| Mem0 Plugin | `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 |
-| OpenCode Plugin | `opencode-plugin-checks.yml` | Push to main (`.opencode-plugin/`), manual | Bun: tsc + build + dist artifact check |
+| Agent Plugins Python | `agent-plugins-python-checks.yml` | Push to main (shared Python core and native/portable plugin directories), manual | Runtime tests on Python 3.10; full pytest on 3.11, 3.12; ruff + generated-package drift on 3.12 |
+| Agent Plugins TypeScript | `agent-plugins-typescript-checks.yml` | Push to main (`integrations/agent-plugin-core/typescript/`), manual | tsc + node:test on Node 22 |
+| OpenCode Plugin | `opencode-plugin-checks.yml` | Push to main (`integrations/opencode-plugin/`), manual | Bun: tsc + build + dist artifact check |
 | Pi Agent Plugin | `pi-agent-plugin-checks.yml` | Push to main (`integrations/pi-agent-plugin/`), manual | tsc + vitest + tsup on Node 20, 22 |
 | DeepSeek Harness Plugin | `deepseek-plugin-checks.yml` | Push to main (`integrations/deepseek-plugin/`), manual | tsc + vitest + tsup on Node 20, 22 |
 | n8n Node | `n8n-nodes-mem0-checks.yml` | Push to main (`integrations/n8n-nodes-mem0/`), manual | ESLint + tsc build on Node 20 |
@@ -0,0 +1,97 @@
+name: Agent Plugins Python Checks
+
+# Python runtime, adapters, generated bundles, and portable plugin validation.
+# On PRs this is invoked by ci-gate.yml (the single required check);
+# push-to-main and manual runs remain standalone.
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+    paths:
+      - 'integrations/agent-plugin-core/**'
+      - '!integrations/agent-plugin-core/typescript/**'
+      - 'integrations/mem0-agent-plugin/**'
+      - 'integrations/claude-code-plugin/**'
+      - 'integrations/cursor-plugin/**'
+      - 'integrations/codex-plugin/**'
+      - 'integrations/kimi-plugin/**'
+      - 'integrations/antigravity-plugin/**'
+      - 'marketplace.json'
+      - '.agents/plugins/marketplace.json'
+      - '.claude-plugin/marketplace.json'
+      - '.codex-plugin/marketplace.json'
+      - '.cursor-plugin/marketplace.json'
+      - '.kimi-plugin/marketplace.json'
+      - '.github/workflows/agent-plugins-python-checks.yml'
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install runtime test tooling
+        if: matrix.python-version == '3.10'
+        run: pip install pytest
+
+      - name: Install build and test tooling
+        if: matrix.python-version != '3.10'
+        run: pip install pytest ruff -r integrations/agent-plugin-core/requirements-dev.txt
+
+      - name: Check Python runtime compatibility
+        run: >-
+          python3 -m compileall -q
+          integrations/agent-plugin-core/python
+          integrations/claude-code-plugin/adapters
+          integrations/cursor-plugin/hooks
+          integrations/codex-plugin/hooks
+          integrations/kimi-plugin/hooks
+          integrations/antigravity-plugin/hooks
+
+      - name: Lint
+        if: matrix.python-version == '3.12'
+        run: >-
+          python3 -m ruff check
+          integrations/agent-plugin-core
+          integrations/claude-code-plugin
+          integrations/cursor-plugin
+          integrations/codex-plugin
+          integrations/kimi-plugin
+          integrations/antigravity-plugin
+
+      - name: Verify installable plugins are current
+        if: matrix.python-version == '3.12'
+        run: |
+          for host in claude-code cursor codex kimi antigravity; do
+            python3 integrations/agent-plugin-core/build/build.py "$host" --kind native --check
+          done
+          python3 integrations/agent-plugin-core/build/build.py mem0-agent-plugin --kind portable --check
+
+      - name: Run Python 3.10 runtime tests
+        if: matrix.python-version == '3.10'
+        run: >-
+          python3 -m pytest -q
+          integrations/claude-code-plugin/tests/test_memory_core.py
+          integrations/claude-code-plugin/tests/test_telemetry.py
+
+      - name: Run full tests
+        if: matrix.python-version != '3.10'
+        run: >-
+          python3 -m pytest -q
+          integrations/agent-plugin-core/tests
+          integrations/claude-code-plugin/tests
+          integrations/cursor-plugin/tests
+          integrations/codex-plugin/tests
+          integrations/kimi-plugin/tests
+          integrations/antigravity-plugin/tests
+          --ignore=integrations/claude-code-plugin/tests/integration
@@ -0,0 +1,42 @@
+name: Agent Plugins TypeScript Checks
+
+# Shared TypeScript runtime checks. Each consuming integration keeps its own
+# build workflow, which is also triggered when this shared core changes.
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+    paths:
+      - 'integrations/agent-plugin-core/typescript/**'
+      - '.github/workflows/agent-plugins-typescript-checks.yml'
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: 'pnpm'
+          cache-dependency-path: integrations/agent-plugin-core/typescript/pnpm-lock.yaml
+
+      - name: Install dependencies
+        working-directory: integrations/agent-plugin-core/typescript
+        run: pnpm install --frozen-lockfile
+
+      - name: Type check
+        working-directory: integrations/agent-plugin-core/typescript
+        run: pnpm typecheck
+
+      - name: Run tests
+        working-directory: integrations/agent-plugin-core/typescript
+        run: pnpm test
@@ -38,7 +38,8 @@ jobs:
      cli_python: ${{ steps.filter.outputs.cli_python }}
      cli_node: ${{ steps.filter.outputs.cli_node }}
      openclaw: ${{ steps.filter.outputs.openclaw }}
-      mem0_plugin: ${{ steps.filter.outputs.mem0_plugin }}
+      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 }}
@@ -75,23 +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'
+            agent_plugins_python:
+              - 'integrations/agent-plugin-core/**'
+              - '!integrations/agent-plugin-core/typescript/**'
+              - 'integrations/mem0-agent-plugin/**'
+              - 'integrations/claude-code-plugin/**'
+              - 'integrations/cursor-plugin/**'
+              - 'integrations/codex-plugin/**'
+              - 'integrations/kimi-plugin/**'
+              - 'integrations/antigravity-plugin/**'
+              - 'marketplace.json'
+              - '.agents/plugins/marketplace.json'
+              - '.claude-plugin/marketplace.json'
+              - '.codex-plugin/marketplace.json'
+              - '.cursor-plugin/marketplace.json'
+              - '.kimi-plugin/marketplace.json'
+              - '.github/workflows/agent-plugins-python-checks.yml'
+              - '.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:
@@ -155,11 +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
+    if: needs.changes.outputs.agent_plugins_python == 'true'
+    uses: ./.github/workflows/agent-plugins-python-checks.yml
+
+  agent-plugins-typescript:
+    name: Agent Plugins TypeScript
+    needs: changes
+    if: needs.changes.outputs.agent_plugins_typescript == 'true'
+    uses: ./.github/workflows/agent-plugins-typescript-checks.yml
    secrets: inherit

  opencode-plugin:
@@ -236,7 +263,8 @@ jobs:
      - cli-python
      - cli-node
      - openclaw
-      - mem0-plugin
+      - agent-plugins-python
+      - agent-plugins-typescript
      - opencode-plugin
      - pi-agent-plugin
      - deepseek-plugin
@@ -8,6 +8,7 @@ on:
    branches: [main]
    paths:
      - 'integrations/deepseek-plugin/**'
+      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/deepseek-plugin-checks.yml'
  workflow_call:

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

-      - name: Verify dist output exists
-        run: |
-          test -f integrations/deepseek-plugin/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
-          test -f integrations/deepseek-plugin/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
+      - name: Verify package artifact
+        run: python3 integrations/agent-plugin-core/conformance/artifacts.py deepseek
@@ -1,58 +0,0 @@
-name: Mem0 Plugin Checks
-
-# On PRs this is invoked by ci-gate.yml (the single required check);
-# push-to-main and manual runs remain standalone.
-#
-# Covers the Python plugin (scripts/ + tests/). The nested .opencode-plugin/
-# is a separate package with its own workflow (opencode-plugin-checks.yml).
-on:
-  workflow_dispatch:
-  push:
-    branches: [main]
-    paths:
-      - 'integrations/mem0-plugin/**'
-      - '!integrations/mem0-plugin/.opencode-plugin/**'
-      - '.github/workflows/mem0-plugin-checks.yml'
-  workflow_call:
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: ["3.10", "3.11", "3.12"]
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-
-      - name: Install dependencies
-        working-directory: integrations/mem0-plugin
-        run: |
-          pip install -r requirements.txt
-          pip install pytest
-
-      - name: Verify hook entry points are executable
-        working-directory: integrations/mem0-plugin
-        run: |
-          missing=$(find scripts -name '*.sh' ! -name '_*' ! -perm -u+x -print)
-          if [ -n "$missing" ]; then
-            echo "Hook entry points must be executable:"
-            echo "$missing"
-            exit 1
-          fi
-
-      - name: Check hook manifests are valid JSON
-        working-directory: integrations/mem0-plugin
-        run: |
-          for f in plugin.json mcp_config.json hooks.json hooks/*.json; do
-            jq empty "$f" || (echo "Invalid JSON: $f" && exit 1)
-          done
-
-      - name: Run tests
-        working-directory: integrations/mem0-plugin
-        run: pytest -q
@@ -8,6 +8,7 @@ on:
    branches: [main]
    paths:
      - 'integrations/openclaw/**'
+      - 'integrations/agent-plugin-core/typescript/**'
      - '.github/workflows/openclaw-checks.yml'
  workflow_call:

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

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

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

@@ -34,6 +35,6 @@ jobs:
      - name: Build
        run: bun run build

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

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

-      - name: Verify dist output exists
-        run: |
-          test -f integrations/pi-agent-plugin/dist/index.js || (echo "Build output missing: dist/index.js" && exit 1)
-          test -f integrations/pi-agent-plugin/dist/index.d.ts || (echo "Build output missing: dist/index.d.ts" && exit 1)
-          test -f integrations/pi-agent-plugin/dist/entry.js || (echo "Build output missing: dist/entry.js" && exit 1)
-          test -f integrations/pi-agent-plugin/dist/entry.d.ts || (echo "Build output missing: dist/entry.d.ts" && exit 1)
+      - name: Verify package artifact
+        run: python3 integrations/agent-plugin-core/conformance/artifacts.py pi-agent
@@ -14,6 +14,10 @@ server/.env
 # Distribution / packaging
 .Python
 build/
+!integrations/agent-plugin-core/build/
+!integrations/agent-plugin-core/build/*.py
+!integrations/agent-plugin-core/build/schemas/
+!integrations/agent-plugin-core/build/schemas/*.json
 develop-eggs/
 dist/
 downloads/
@@ -5,11 +5,11 @@
    {
      "id": "mem0",
      "displayName": "Mem0",
-      "version": "0.1.0",
-      "description": "Persistent memory for Kimi Code. Remembers decisions, patterns, and preferences across sessions.",
+      "version": "0.3.1",
+      "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.
@@ -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
@@ -1,5 +1,7 @@
 ---
 title: "Overview"
+seo:
+  title: "API Reference Overview - Mem0"
 icon: "terminal"
 iconType: "solid"
 description: "REST APIs for memory management, search, and entity operations"
@@ -10,7 +12,7 @@ description: "REST APIs for memory management, search, and entity operations"
 Mem0 provides a comprehensive REST API for integrating advanced memory capabilities into your applications. Create, search, update, and manage memories across users, agents, and custom entities with simple HTTP requests.

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

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

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

 <Warning>
 **Keep your API key secure.** Never expose it in client-side code or public repositories. Use environment variables and server-side requests only.
@@ -1,5 +1,7 @@
 ---
 title: 'Delete Memory'
+seo:
+  title: "Delete Memory API Endpoint - Mem0"
 description: "Delete a single memory by its unique memory ID from the Mem0 platform using the DELETE endpoint."
 openapi: delete /v1/memories/{memory_id}/
 ---
@@ -1,5 +1,7 @@
 ---
 title: 'Update Memory'
+seo:
+  title: "Update Memory API Endpoint - Mem0"
 description: "Update the content, metadata, timestamp, or expiration date of a single memory by its unique ID using the PUT endpoint."
 openapi: put /v1/memories/{memory_id}/
 ---
@@ -1,5 +1,7 @@
 ---
 title: 'Add Member'
+seo:
+  title: "Add Organization Member API Endpoint - Mem0"
 description: "Add a new member to an organization with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/members/
 ---
@@ -1,5 +1,7 @@
 ---
 title: 'Get Members'
+seo:
+  title: "Get Organization Members API Endpoint - Mem0"
 description: "Retrieve a list of all members belonging to a specific organization on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/members/
 ---
@@ -0,0 +1,5 @@
+---
+title: 'Generate Profiles'
+description: "Start one generation: sample a few entities, or build one for a single entity."
+openapi: post /v2/profiles/jobs/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Get Generation Job'
+description: "Read the progress of a generation, and whether it finished."
+openapi: get /v2/profiles/jobs/{job_id}/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Get Profile Settings'
+description: "Retrieve the profile schema, custom instructions, and enabled flag for the current project."
+openapi: get /v2/profiles/settings/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Get Profile'
+description: "Retrieve the structured profile for a user, with a status describing whether generation has completed."
+openapi: get /v2/entities/{entity_type}/{entity_id}/profile/
+---
@@ -0,0 +1,5 @@
+---
+title: 'Update Profile Settings'
+description: "Set the JSON Schema, custom instructions, or enabled flag that control profile generation for the project."
+openapi: post /v2/profiles/settings/
+---
@@ -1,5 +1,7 @@
 ---
 title: 'Add Member'
+seo:
+  title: "Add Project Member API Endpoint - Mem0"
 description: "Add a new member to a project with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---
@@ -1,5 +1,7 @@
 ---
 title: 'Get Members'
+seo:
+  title: "Get Project Members API Endpoint - Mem0"
 description: "Retrieve a list of all members belonging to a specific project on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---
@@ -7,6 +7,21 @@ mode: "wide"
 <Tabs>
 <Tab title="Python">

+<Update label="2026-09-23" description="v2.1.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, and every job POST carries an `Idempotency-Key` so a retry reuses the job instead of paying twice ([#7340](https://github.com/mem0ai/mem0/pull/7340))
+
+</Update>
+
+<Update label="2026-09-02" description="v2.0.20">
+
+**Improvements:**
+- **OSS notices:** Notice configuration now comes from a static, cacheable repository file with a bundled disabled fallback and deterministic rollout assignment, instead of calling PostHog's feature-flag evaluation API. This keeps notices fail-safe when the remote config is unavailable and removes the PostHog feature-flag request from notice evaluation ([#7185](https://github.com/mem0ai/mem0/pull/7185))
+- **Vector Stores:** `RedisDBConfig` now uses Pydantic's native `extra="forbid"` handling for unknown fields instead of a custom model validator, preserving strict validation while returning standard Pydantic errors ([#7089](https://github.com/mem0ai/mem0/pull/7089))
+
+</Update>
+
 <Update label="2026-08-24" description="v2.0.19">

 **Bug Fixes:**
@@ -1219,6 +1234,20 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-

 <Tab title="TypeScript">

+<Update label="2026-09-23" description="v3.2.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, and every job POST carries an `Idempotency-Key` so a retry reuses the job instead of paying twice ([#7340](https://github.com/mem0ai/mem0/pull/7340))
+
+</Update>
+
+<Update label="2026-09-02" description="v3.1.8">
+
+**Improvements:**
+- **OSS notices:** Notice configuration now comes from a static, cacheable repository file with a bundled disabled fallback and deterministic rollout assignment, instead of calling PostHog's feature-flag evaluation API. This keeps notices fail-safe when the remote config is unavailable and removes the PostHog feature-flag request from notice evaluation ([#7185](https://github.com/mem0ai/mem0/pull/7185))
+
+</Update>
+
 <Update label="2026-08-24" description="v3.1.7">

 **Bug Fixes:**
@@ -1528,7 +1557,7 @@ The largest provider release for the TypeScript OSS SDK so far: 17 new vector st
 **Improvements:**
 - **Telemetry:** Sample OSS hot-path events at 10% to reduce PostHog event volume ([#4771](https://github.com/mem0ai/mem0/pull/4771))

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

 </Update>

@@ -2045,6 +2074,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, Pi Agent, and DeepSeek Harness are `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:**
@@ -2331,8 +2383,124 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex

 </Tab>

+<Tab title="Claude Code">
+
+<Update label="Unreleased" description="Sidekick availability">
+
+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="Unreleased" description="Sidekick availability">
+
+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="Unreleased" description="Sidekick availability">
+
+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="Agent Plugins v1">
+
+<Update label="Unreleased" description="Sidekick availability">
+
+Sidekick is available only in Claude Code, not in the portable package.
+
+</Update>
+
+<Update label="2026-09-08" description="Portable Mem0 plugin v0.3.1">
+
+**Added:**
+- One portable package at `integrations/mem0-agent-plugin/`, using the Agent Plugins 1.0.0 root `plugin.json`, `mcp.json`, and fixed `skills/` locations.
+- Ships a local, read-only `search_memories` server and the six shared memory skills. Uses `PLUGIN_ROOT` for bundled files and `PLUGIN_DATA` for persistent plugin state; all package files remain inside the installable directory.
+
+**Packaging:**
+- Generated from the shared Python runtime and skill templates. Builds validate the manifest, MCP configuration, skills, and generated-file consistency.
+- Host lifecycle hooks and native Sidekick declarations remain in the native plugin packages; the portable package does not provide automatic lifecycle capture or host-specific subagent isolation. Its bundled remember skill cannot persist a new memory on its own because the portable package has no capture hooks or write tool.
+
+[#7203](https://github.com/mem0ai/mem0/pull/7203)
+
+</Update>
+
+</Tab>
+
 <Tab title="OpenCode">

+<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:**
@@ -2413,6 +2581,28 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex

 <Tab title="Antigravity">

+<Update label="Unreleased" description="Sidekick availability">
+
+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:**
@@ -2489,6 +2679,30 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="Kimi">

+<Update label="Unreleased" description="Sidekick availability">
+
+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))
@@ -2505,6 +2719,24 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="OpenClaw">

+<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:**
@@ -2775,6 +3007,24 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="Pi Agent">

+<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:**
@@ -2870,6 +3120,23 @@ Existing memories written by the previous versions are not rewritten. If your me

 <Tab title="DeepSeek Harness">

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1,5 +1,7 @@
 ---
 title: LangChain
+seo:
+  title: "LangChain as Vector Store Provider - Mem0"
 description: "Use LangChain as a unified vector store provider in Mem0 to access multiple vector databases through one interface."
 ---

@@ -14,7 +14,7 @@ description: "Use Oracle Database AI Vector Search as a vector store in Mem0 for

 <CodeGroup>
 ```bash Python
-pip install oracledb
+pip install mem0ai
 ```

 ```bash TypeScript
@@ -141,11 +141,13 @@ const config = {

 Here are the parameters available for configuring Oracle AI Vector Search:

+Provide either `connection_params`/`connectionParams` or an existing connection or pool as `client`.
+
 | Python | TypeScript | Description | Default Value |
 | --- | --- | --- | --- |
-| `connection_params` | `connectionParams` | Connection settings passed to the Oracle driver, such as `user`, `password` and `dsn` (`connectString` in TypeScript). See the [Python](https://python-oracledb.readthedocs.io/en/latest/user_guide/connection_handling.html) or [Node.js](https://node-oracledb.readthedocs.io/en/latest/user_guide/connection_handling.html) connection handling guide. | `None` |
+| `connection_params` | `connectionParams` | Connection settings passed to the Oracle driver, such as `user`, `password` and `dsn` (`connectString` in TypeScript). Required unless `client` is provided. See the [Python](https://python-oracledb.readthedocs.io/en/latest/user_guide/connection_handling.html) or [Node.js](https://node-oracledb.readthedocs.io/en/latest/user_guide/connection_handling.html) connection handling guide. | `None` |
 | `use_connection_pool` | `useConnectionPool` | Create a connection pool from the connection parameters instead of a single connection | `True` |
-| `client` | `client` | An existing Oracle connection or pool to use instead of building one from the connection parameters | `None` |
+| `client` | `client` | An existing Oracle connection or pool to use instead of building one from the connection parameters. Required unless connection parameters are provided. | `None` |
 | `collection_name` | `collectionName` | Name of the Oracle table that stores vectors and payloads | `mem0` |
 | `embedding_model_dims` | `embeddingModelDims` | Dimension of your embedding vectors, must be greater than 0 | `1536` |
 | `distance_metric` | `distanceMetric` | Distance function used for indexing and search: `COSINE`, `EUCLIDEAN`, `EUCLIDEAN_SQUARED`, `DOT`, `HAMMING` or `MANHATTAN` | `COSINE` |
@@ -222,15 +224,21 @@ Multiple fields at the top level are combined with `AND`:
 ```python Python
 m.search(
    "movie recommendations",
-    user_id="alice",
-    filters={"category": {"in": ["movies", "books"]}, "rating": {"gte": 4}},
+    filters={
+        "user_id": "alice",
+        "category": {"in": ["movies", "books"]},
+        "rating": {"gte": 4},
+    },
 )
 ```

 ```typescript TypeScript
 await memory.search("movie recommendations", {
-  userId: "alice",
-  filters: { category: { in: ["movies", "books"] }, rating: { gte: 4 } },
+  filters: {
+    user_id: "alice",
+    category: { in: ["movies", "books"] },
+    rating: { gte: 4 },
+  },
 });
 ```
 </CodeGroup>
@@ -102,7 +102,7 @@ Here are the parameters available for configuring Upstash Vector:
 | `url`               | URL for the Upstash Vector index   | `None`        |
 | `token`             | Token for the Upstash Vector index | `None`        |
 | `client`            | An `upstash_vector.Index` instance | `None`        |
-| `collection_name`   | The default namespace used         | `""`          |
+| `collection_name`   | The default namespace used         | `"mem0"`      |
 | `enable_embeddings` | Whether to use Upstash embeddings  | `False`       |

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

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

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

 ---

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

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

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

 ## Store and Retrieve Scoped Memories

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

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

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

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

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

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

 ## Complete Implementation

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

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

 ---

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

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

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

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

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

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

 ```python
@@ -26,7 +26,7 @@ MEM0_API_KEY=your_mem0_api_key
 OPENAI_API_KEY=your_openai_api_key
 ```

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

 ### Configuration

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

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

@@ -1,5 +1,7 @@
 ---
 title: Overview
+seo:
+  title: "Cookbooks and Tutorials - Mem0"
 description: "Browse cookbook examples and tutorials for building AI applications with Mem0, from companion chatbots to AI agents."
 ---

@@ -66,7 +66,7 @@ The combined score outperformed every individual signal across every category te

 ### LoCoMo

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

 | Category | Score |
 |---|---|
@@ -1,5 +1,7 @@
 ---
 title: Delete Memory
+seo:
+  title: "Delete Memory Operation - Mem0"
 description: Remove memories from Mem0 either individually, in bulk, or via filters.
 icon: "trash"
 iconType: "solid"
@@ -1,5 +1,7 @@
 ---
 title: Update Memory
+seo:
+  title: "Update Memory Operation - Mem0"
 description: Modify an existing memory by updating its content or metadata.
 icon: "pen-to-square"
 iconType: "solid"
@@ -71,6 +71,7 @@
                        "pages": [
                          "platform/features/v2-memory-filters",
                          "platform/features/entity-scoped-memory",
+                          "platform/features/user-profiles",
                          "platform/features/graph-memory",
                          "platform/features/async-client",
                          "platform/features/multimodal-support",
@@ -152,7 +153,7 @@
                      "open-source/features/multimodal-support",
                      "open-source/features/custom-instructions",
                      "open-source/features/rest-api",
-                      "open-source/features/openai_compatibility",
+                      "open-source/features/openai-compatibility",
                      "platform/features/memory-expiration"
                    ]
                  },
@@ -173,14 +174,14 @@
                            "pages": [
                              "components/llms/models/openai",
                              "components/llms/models/anthropic",
-                              "components/llms/models/azure_openai",
+                              "components/llms/models/azure-openai",
                              "components/llms/models/ollama",
                              "components/llms/models/together",
                              "components/llms/models/groq",
                              "components/llms/models/litellm",
-                              "components/llms/models/mistral_AI",
-                              "components/llms/models/google_AI",
-                              "components/llms/models/aws_bedrock",
+                              "components/llms/models/mistral-ai",
+                              "components/llms/models/google-ai",
+                              "components/llms/models/aws-bedrock",
                              "components/llms/models/deepseek",
                              "components/llms/models/minimax",
                              "components/llms/models/xAI",
@@ -210,7 +211,7 @@
                              "components/vectordbs/dbs/mongodb",
                              "components/vectordbs/dbs/oracledb",
                              "components/vectordbs/dbs/azure",
-                              "components/vectordbs/dbs/azure_mysql",
+                              "components/vectordbs/dbs/azure-mysql",
                              "components/vectordbs/dbs/redis",
                              "components/vectordbs/dbs/valkey",
                              "components/vectordbs/dbs/elasticsearch",
@@ -218,16 +219,16 @@
                              "components/vectordbs/dbs/supabase",
                              "components/vectordbs/dbs/upstash-vector",
                              "components/vectordbs/dbs/vectorize",
-                              "components/vectordbs/dbs/vertex_ai",
+                              "components/vectordbs/dbs/vertex-ai",
                              "components/vectordbs/dbs/weaviate",
                              "components/vectordbs/dbs/faiss",
                              "components/vectordbs/dbs/langchain",
                              "components/vectordbs/dbs/baidu",
                              "components/vectordbs/dbs/cassandra",
-                              "components/vectordbs/dbs/s3_vectors",
+                              "components/vectordbs/dbs/s3-vectors",
                              "components/vectordbs/dbs/databricks",
                              "components/vectordbs/dbs/neon",
-                              "components/vectordbs/dbs/neptune_analytics",
+                              "components/vectordbs/dbs/neptune-analytics",
                              "components/vectordbs/dbs/turbopuffer"
                            ]
                          }
@@ -244,15 +245,15 @@
                            "icon": "list",
                            "pages": [
                              "components/embedders/models/openai",
-                              "components/embedders/models/azure_openai",
+                              "components/embedders/models/azure-openai",
                              "components/embedders/models/ollama",
                              "components/embedders/models/huggingface",
                              "components/embedders/models/vertexai",
-                              "components/embedders/models/google_AI",
+                              "components/embedders/models/google-ai",
                              "components/embedders/models/lmstudio",
                              "components/embedders/models/together",
                              "components/embedders/models/langchain",
-                              "components/embedders/models/aws_bedrock",
+                              "components/embedders/models/aws-bedrock",
                              "components/embedders/models/fastembed"
                            ]
                          }
@@ -271,10 +272,10 @@
                            "icon": "list",
                            "pages": [
                              "components/rerankers/models/cohere",
-                              "components/rerankers/models/sentence_transformer",
+                              "components/rerankers/models/sentence-transformer",
                              "components/rerankers/models/huggingface",
-                              "components/rerankers/models/llm_reranker",
-                              "components/rerankers/models/zero_entropy"
+                              "components/rerankers/models/llm-reranker",
+                              "components/rerankers/models/zero-entropy"
                            ]
                          }
                        ]
@@ -373,6 +374,7 @@
                      "integrations/claude-ai",
                      "integrations/cursor",
                      "integrations/codex",
+                      "integrations/kimi",
                      "integrations/opencode",
                      "integrations/antigravity"
                    ]
@@ -510,6 +512,17 @@
                      "api-reference/entities/delete-user"
                    ]
                  },
+                  {
+                    "group": "Profiles",
+                    "icon": "id-card",
+                    "pages": [
+                      "api-reference/profiles/get-profile",
+                      "api-reference/profiles/get-profile-settings",
+                      "api-reference/profiles/update-profile-settings",
+                      "api-reference/profiles/generate-profiles",
+                      "api-reference/profiles/get-profile-job"
+                    ]
+                  },
                  {
                    "group": "Organizations",
                    "icon": "building",
@@ -642,7 +655,7 @@
    },
    {
      "source": "/components/rerankers/models/llm",
-      "destination": "/components/rerankers/models/llm_reranker"
+      "destination": "/components/rerankers/models/llm-reranker"
    },
    {
      "source": "/migration/breaking-changes",
@@ -818,7 +831,7 @@
    },
    {
      "source": "/components/llms/models/azure_openai_structured",
-      "destination": "/components/llms/models/azure_openai"
+      "destination": "/components/llms/models/azure-openai"
    },
    {
      "source": "/components/llms/models/openai_structured",
@@ -834,7 +847,7 @@
    },
    {
      "source": "/components/vectordbs/dbs/vertex_ai_vector_search",
-      "destination": "/components/vectordbs/dbs/vertex_ai"
+      "destination": "/components/vectordbs/dbs/vertex-ai"
    },
    {
      "source": "/platform/features/selective-memory",
@@ -1082,7 +1095,7 @@
    },
    {
      "source": "/components/embedders/models/google_ai",
-      "destination": "/components/embedders/models/google_AI"
+      "destination": "/components/embedders/models/google-ai"
    },
    {
      "source": "/components/embedders/models/lm_studio",
@@ -1094,24 +1107,16 @@
    },
    {
      "source": "/components/llms/models/google_ai",
-      "destination": "/components/llms/models/google_AI"
+      "destination": "/components/llms/models/google-ai"
    },
    {
      "source": "/components/llms/models/mistral_ai",
-      "destination": "/components/llms/models/mistral_AI"
+      "destination": "/components/llms/models/mistral-ai"
    },
    {
      "source": "/components/llms/models/lm_studio",
      "destination": "/components/llms/models/lmstudio"
    },
-    {
-      "source": "/components/vectordbs/dbs/neptune-analytics",
-      "destination": "/components/vectordbs/dbs/neptune_analytics"
-    },
-    {
-      "source": "/components/vectordbs/dbs/s3-vectors",
-      "destination": "/components/vectordbs/dbs/s3_vectors"
-    },
    {
      "source": "/open-source/python_quickstart",
      "destination": "/open-source/python-quickstart"
@@ -1315,6 +1320,262 @@
    {
      "source": "/api-reference/entities/get-entities",
      "destination": "/api-reference/entities/get-users"
+    },
+    {
+      "source": "/api-reference/event/get-events",
+      "destination": "/api-reference/events/get-events"
+    },
+    {
+      "source": "/api-reference/entities/delete-users",
+      "destination": "/api-reference/entities/delete-user"
+    },
+    {
+      "source": "/api-reference/organization/update-organization-member",
+      "destination": "/api-reference/organization/update-org-member"
+    },
+    {
+      "source": "/api-reference/organization/get-organizations",
+      "destination": "/api-reference/organization/get-orgs"
+    },
+    {
+      "source": "/api-reference/entities/get-user",
+      "destination": "/api-reference/entities/get-users"
+    },
+    {
+      "source": "/api-reference/export/create-memory-export",
+      "destination": "/api-reference/memory/create-memory-export"
+    },
+    {
+      "source": "/integrations/mcp",
+      "destination": "/platform/mem0-mcp"
+    },
+    {
+      "source": "/platform/api-reference",
+      "destination": "/api-reference"
+    },
+    {
+      "source": "/api-reference/memory/add-memory",
+      "destination": "/api-reference/memory/add-memories"
+    },
+    {
+      "source": "/api-reference/overview",
+      "destination": "/api-reference"
+    },
+    {
+      "source": "/platform/reference/python-sdk",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/platform/python",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/platform/features/memory",
+      "destination": "/platform/features/memory-decay"
+    },
+    {
+      "source": "/platform/api-reference/python",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/api-reference/webhooks",
+      "destination": "/api-reference/webhook/create-webhook"
+    },
+    {
+      "source": "/platform/python-quickstart",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/api-reference/organization/delete-org-project",
+      "destination": "/api-reference/organization/delete-org"
+    },
+    {
+      "source": "/platform/features/scoping",
+      "destination": "/platform/features/entity-scoped-memory"
+    },
+    {
+      "source": "/platform/quickstart/python",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/api-reference/memory/history",
+      "destination": "/api-reference/memory/history-memory"
+    },
+    {
+      "source": "/api-reference/entities/get-user-memories",
+      "destination": "/api-reference/entities/get-users"
+    },
+    {
+      "source": "/platform/api-reference/webhooks/create",
+      "destination": "/api-reference/webhook/create-webhook"
+    },
+    {
+      "source": "/platform/python/quickstart",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/api-reference/memory/batch-update-memory",
+      "destination": "/api-reference/memory/batch-update"
+    },
+    {
+      "source": "/api-reference/memories/add",
+      "destination": "/api-reference/memory/add-memories"
+    },
+    {
+      "source": "/python-quickstart",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/api-reference/webhook/list-webhooks",
+      "destination": "/api-reference/webhook/get-webhook"
+    },
+    {
+      "source": "/platform/reference/memory/delete-memory",
+      "destination": "/api-reference/memory/delete-memory"
+    },
+    {
+      "source": "/platform/webhooks",
+      "destination": "/platform/features/webhooks"
+    },
+    {
+      "source": "/platform/api-reference/memories/add",
+      "destination": "/api-reference/memory/add-memories"
+    },
+    {
+      "source": "/api-reference/organization/organizations",
+      "destination": "/api-reference/organization/create-org"
+    },
+    {
+      "source": "/sdk/python/quickstart",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/platform/export",
+      "destination": "/platform/features/memory-export"
+    },
+    {
+      "source": "/open-source/python-memory",
+      "destination": "/open-source/python-quickstart"
+    },
+    {
+      "source": "/platform/reference",
+      "destination": "/api-reference"
+    },
+    {
+      "source": "/api-reference/memory/get-all-memories",
+      "destination": "/api-reference/memory/get-memories"
+    },
+    {
+      "source": "/api-reference/user/delete-users",
+      "destination": "/api-reference/entities/delete-user"
+    },
+    {
+      "source": "/api-reference/memories/search-memories",
+      "destination": "/api-reference/memory/search-memories"
+    },
+    {
+      "source": "/api-reference/organization/update-members",
+      "destination": "/api-reference/project/update-project-member"
+    },
+    {
+      "source": "/platform/api-reference/memory/batch-update",
+      "destination": "/api-reference/memory/batch-update"
+    },
+    {
+      "source": "/api-reference/memory/search",
+      "destination": "/api-reference/memory/search-memories"
+    },
+    {
+      "source": "/api-reference/batch/update-memories",
+      "destination": "/api-reference/memory/batch-update"
+    },
+    {
+      "source": "/api-reference/organization/update-organization-member-role",
+      "destination": "/api-reference/project/update-project-member"
+    },
+    {
+      "source": "/api-reference/webhooks/delete",
+      "destination": "/api-reference/webhook/delete-webhook"
+    },
+    {
+      "source": "/api-reference/memory/delete-all-memories",
+      "destination": "/api-reference/memory/delete-memories"
+    },
+    {
+      "source": "/platform/reference/overview",
+      "destination": "/api-reference"
+    },
+    {
+      "source": "/api-reference/mem0/add-memories",
+      "destination": "/api-reference/memory/add-memories"
+    },
+    {
+      "source": "/platform/mcp/overview",
+      "destination": "/platform/mem0-mcp"
+    },
+    {
+      "source": "/openmemory/mcp/introduction",
+      "destination": "https://mem0.ai/blog/introducing-openmemory-mcp"
+    },
+    {
+      "source": "/components/embedders/models/aws_bedrock",
+      "destination": "/components/embedders/models/aws-bedrock"
+    },
+    {
+      "source": "/components/embedders/models/azure_openai",
+      "destination": "/components/embedders/models/azure-openai"
+    },
+    {
+      "source": "/components/embedders/models/google_AI",
+      "destination": "/components/embedders/models/google-ai"
+    },
+    {
+      "source": "/components/llms/models/aws_bedrock",
+      "destination": "/components/llms/models/aws-bedrock"
+    },
+    {
+      "source": "/components/llms/models/azure_openai",
+      "destination": "/components/llms/models/azure-openai"
+    },
+    {
+      "source": "/components/llms/models/google_AI",
+      "destination": "/components/llms/models/google-ai"
+    },
+    {
+      "source": "/components/llms/models/mistral_AI",
+      "destination": "/components/llms/models/mistral-ai"
+    },
+    {
+      "source": "/components/rerankers/models/llm_reranker",
+      "destination": "/components/rerankers/models/llm-reranker"
+    },
+    {
+      "source": "/components/rerankers/models/sentence_transformer",
+      "destination": "/components/rerankers/models/sentence-transformer"
+    },
+    {
+      "source": "/components/rerankers/models/zero_entropy",
+      "destination": "/components/rerankers/models/zero-entropy"
+    },
+    {
+      "source": "/components/vectordbs/dbs/azure_mysql",
+      "destination": "/components/vectordbs/dbs/azure-mysql"
+    },
+    {
+      "source": "/components/vectordbs/dbs/neptune_analytics",
+      "destination": "/components/vectordbs/dbs/neptune-analytics"
+    },
+    {
+      "source": "/components/vectordbs/dbs/s3_vectors",
+      "destination": "/components/vectordbs/dbs/s3-vectors"
+    },
+    {
+      "source": "/components/vectordbs/dbs/vertex_ai",
+      "destination": "/components/vectordbs/dbs/vertex-ai"
+    },
+    {
+      "source": "/open-source/features/openai_compatibility",
+      "destination": "/open-source/features/openai-compatibility"
    }
  ]
 }
@@ -0,0 +1,88 @@
+<svg viewBox="0 0 600 420" role="img" aria-labelledby="venn-title venn-desc" xmlns="http://www.w3.org/2000/svg">
+  <title id="venn-title">Mem0 Memory Scoping</title>
+  <desc id="venn-desc">Venn diagram showing how a single add call produces shared project memory and personal memory, with search returning the union of both.</desc>
+
+  <rect width="600" height="420" fill="#f5f5f5"/>
+
+  <text x="300" y="36" fill="#2d3142" font-size="20" font-weight="400"
+        font-family="Georgia, serif" text-anchor="middle">Memory Scoping</text>
+  <text x="300" y="56" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle" letter-spacing="0.08em">ONE ADD CALL · TWO MEMORY BUCKETS</text>
+
+  <circle cx="228" cy="212" r="132" fill="rgba(45,49,66,0.05)" stroke="#4f5d75" stroke-width="1"/>
+  <circle cx="372" cy="212" r="132" fill="rgba(79,93,117,0.05)" stroke="#7a8399" stroke-width="1"/>
+
+  <defs>
+    <clipPath id="clip-left">
+      <circle cx="228" cy="212" r="132"/>
+    </clipPath>
+  </defs>
+  <circle cx="372" cy="212" r="132" fill="rgba(235,108,54,0.10)" clip-path="url(#clip-left)"/>
+
+  <text x="124" y="84" fill="#2d3142" font-size="13" font-weight="600"
+        font-family="sans-serif" text-anchor="middle">Shared Project</text>
+  <text x="124" y="100" fill="#4f5d75" font-size="9"
+        font-family="monospace" text-anchor="middle">agent_id = repo slug</text>
+
+  <text x="476" y="84" fill="#2d3142" font-size="13" font-weight="600"
+        font-family="sans-serif" text-anchor="middle">Personal</text>
+  <text x="476" y="100" fill="#4f5d75" font-size="9"
+        font-family="monospace" text-anchor="middle">user_id = you</text>
+
+  <text x="168" y="176" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Conventions</text>
+  <text x="168" y="196" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Commands</text>
+  <text x="168" y="216" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Decisions</text>
+  <text x="168" y="236" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Fixes</text>
+
+  <text x="168" y="264" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">no user_id</text>
+  <text x="168" y="276" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">visible to team</text>
+
+  <text x="432" y="192" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Preferences</text>
+  <text x="432" y="212" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Habits</text>
+  <text x="432" y="232" fill="#2d3142" font-size="11" font-weight="500"
+        font-family="sans-serif" text-anchor="middle">Style</text>
+
+  <text x="432" y="260" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">no agent_id</text>
+  <text x="432" y="272" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">private to you</text>
+
+  <text x="300" y="196" fill="#eb6c36" font-size="12" font-weight="600"
+        font-family="sans-serif" text-anchor="middle">Search</text>
+  <text x="300" y="212" fill="#eb6c36" font-size="12" font-weight="600"
+        font-family="sans-serif" text-anchor="middle">Result</text>
+  <text x="300" y="232" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">OR [agent_id+app_id,</text>
+  <text x="300" y="244" fill="#7a8399" font-size="9"
+        font-family="monospace" text-anchor="middle">user_id+app_id]</text>
+
+  <line x1="40" y1="360" x2="560" y2="360" stroke="rgba(45,49,66,0.12)" stroke-width="0.8"/>
+
+  <text x="80" y="380" fill="#4f5d75" font-size="9" font-weight="600"
+        font-family="monospace" text-anchor="middle" letter-spacing="0.06em">agent_id</text>
+  <text x="80" y="396" fill="#7a8399" font-size="8"
+        font-family="monospace" text-anchor="middle">repo slug</text>
+
+  <text x="220" y="380" fill="#4f5d75" font-size="9" font-weight="600"
+        font-family="monospace" text-anchor="middle" letter-spacing="0.06em">app_id</text>
+  <text x="220" y="396" fill="#7a8399" font-size="8"
+        font-family="monospace" text-anchor="middle">repo</text>
+
+  <text x="380" y="380" fill="#4f5d75" font-size="9" font-weight="600"
+        font-family="monospace" text-anchor="middle" letter-spacing="0.06em">user_id</text>
+  <text x="380" y="396" fill="#7a8399" font-size="8"
+        font-family="monospace" text-anchor="middle">you</text>
+
+  <text x="520" y="380" fill="#4f5d75" font-size="9" font-weight="600"
+        font-family="monospace" text-anchor="middle" letter-spacing="0.06em">run_id</text>
+  <text x="520" y="396" fill="#7a8399" font-size="8"
+        font-family="monospace" text-anchor="middle">session</text>
+</svg>
@@ -0,0 +1,133 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 860 784" width="860" role="img" aria-labelledby="seq-title seq-desc">
+  <title id="seq-title">Mem0 Plugin Architecture</title>
+  <desc id="seq-desc">Sequence diagram showing the full Claude Code plugin: lifecycle hooks, first-prompt memory recall, capture events, background extraction via detached worker, and on-demand skills and search tool.</desc>
+
+  <defs>
+    <marker id="arrow" markerWidth="8" markerHeight="6" refX="7" refY="3" orient="auto">
+      <polygon points="0 0, 8 3, 0 6" fill="#4f5d75"/>
+    </marker>
+    <marker id="arrow-accent" markerWidth="8" markerHeight="6" refX="7" refY="3" orient="auto">
+      <polygon points="0 0, 8 3, 0 6" fill="#eb6c36"/>
+    </marker>
+    <marker id="arrow-link" markerWidth="8" markerHeight="6" refX="7" refY="3" orient="auto">
+      <polygon points="0 0, 8 3, 0 6" fill="#2e5aa8"/>
+    </marker>
+    <marker id="arrow-open" markerWidth="8" markerHeight="6" refX="7" refY="3" orient="auto">
+      <polyline points="0 0, 8 3, 0 6" fill="none" stroke="#4f5d75" stroke-width="1.2"/>
+    </marker>
+    <style>
+      text { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; }
+    </style>
+  </defs>
+
+  <rect width="100%" height="100%" fill="#f5f5f5"/>
+
+  <!-- LIFELINES -->
+  <line x1="108" y1="76" x2="108" y2="720" stroke="rgba(45,49,66,0.12)" stroke-width="1" stroke-dasharray="3,3"/>
+  <line x1="320" y1="76" x2="320" y2="720" stroke="rgba(45,49,66,0.12)" stroke-width="1" stroke-dasharray="3,3"/>
+  <line x1="540" y1="76" x2="540" y2="720" stroke="rgba(45,49,66,0.12)" stroke-width="1" stroke-dasharray="3,3"/>
+  <line x1="740" y1="76" x2="740" y2="720" stroke="rgba(45,49,66,0.12)" stroke-width="1" stroke-dasharray="3,3"/>
+
+  <!-- PHASE 1: SESSION INIT -->
+  <text x="32" y="100" fill="#7a8399" font-size="9" font-style="italic">Session init</text>
+
+  <rect x="164" y="104" width="84" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="206" y="114" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">SESSION-START</text>
+  <line x1="112" y1="128" x2="316" y2="128" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+
+  <!-- PHASE 2: CAPTURE & RECALL -->
+  <text x="32" y="160" fill="#7a8399" font-size="9" font-style="italic">Capture and recall</text>
+
+  <rect x="162" y="168" width="88" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="206" y="178" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">USER-PROMPT</text>
+  <line x1="112" y1="192" x2="316" y2="192" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+
+  <!-- OPT fragment -->
+  <rect x="260" y="212" width="520" height="148" rx="4" fill="rgba(235,108,54,0.08)" stroke="#eb6c36" stroke-width="1" stroke-opacity="0.4"/>
+  <rect x="260" y="212" width="36" height="16" rx="2" fill="#f5f5f5" stroke="#eb6c36" stroke-width="1" stroke-opacity="0.4"/>
+  <text x="278" y="224" fill="#eb6c36" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.12em">OPT</text>
+  <text x="308" y="236" fill="#7a8399" font-size="8" font-family="monospace" letter-spacing="0.04em">[first prompt]</text>
+
+  <rect x="472" y="248" width="108" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="526" y="258" fill="#2e5aa8" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">SEARCH MEMORIES</text>
+  <line x1="324" y1="272" x2="736" y2="272" stroke="#2e5aa8" stroke-width="1" marker-end="url(#arrow-link)"/>
+
+  <rect x="480" y="280" width="80" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="520" y="290" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">≤5 MEMORIES</text>
+  <line x1="736" y1="304" x2="324" y2="304" stroke="#4f5d75" stroke-width="1" stroke-dasharray="5,4" marker-end="url(#arrow)"/>
+
+  <rect x="148" y="316" width="120" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="208" y="326" fill="#eb6c36" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">CONTEXT INJECTED</text>
+  <line x1="316" y1="348" x2="112" y2="348" stroke="#eb6c36" stroke-width="1" stroke-dasharray="5,4" marker-end="url(#arrow-accent)"/>
+
+  <rect x="176" y="380" width="60" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="206" y="390" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">POST-TOOL</text>
+  <line x1="112" y1="404" x2="316" y2="404" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+
+  <rect x="156" y="416" width="100" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="206" y="426" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">SIDEKICK-START</text>
+  <line x1="112" y1="440" x2="316" y2="440" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+
+  <rect x="184" y="452" width="48" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="208" y="462" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">STOP</text>
+  <line x1="112" y1="476" x2="316" y2="476" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+
+  <text x="332" y="466" fill="#7a8399" font-size="8" font-style="italic">repeats each exchange</text>
+
+  <!-- PHASE 3: BACKGROUND EXTRACTION -->
+  <text x="32" y="508" fill="#7a8399" font-size="9" font-style="italic">Background extraction</text>
+
+  <rect x="380" y="516" width="96" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="428" y="526" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">HAND_OFF_FLUSH</text>
+  <line x1="324" y1="540" x2="536" y2="540" stroke="#4f5d75" stroke-width="1" stroke-dasharray="5,4" marker-end="url(#arrow-open)"/>
+  <text x="332" y="556" fill="#7a8399" font-size="8" font-style="italic">periodic, idle (5 min), or session-end</text>
+
+  <rect x="620" y="568" width="28" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="634" y="578" fill="#2e5aa8" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">ADD</text>
+  <line x1="544" y1="592" x2="736" y2="592" stroke="#2e5aa8" stroke-width="1" marker-end="url(#arrow-link)"/>
+  <rect x="564" y="596" width="160" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="644" y="606" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle">agent_id + user_id + app_id + run_id</text>
+
+  <rect x="616" y="616" width="48" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="640" y="626" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.06em">STORED</text>
+  <line x1="736" y1="640" x2="544" y2="640" stroke="#4f5d75" stroke-width="1" stroke-dasharray="5,4" marker-end="url(#arrow)"/>
+
+  <!-- PHASE 4: ON-DEMAND -->
+  <text x="32" y="672" fill="#7a8399" font-size="9" font-style="italic">On-demand (skills + tool)</text>
+
+  <rect x="136" y="680" width="144" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="208" y="690" fill="#7a8399" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.04em">/MEM0:SEARCH, FORGET</text>
+  <line x1="112" y1="704" x2="316" y2="704" stroke="#4f5d75" stroke-width="1" marker-end="url(#arrow)"/>
+  <rect x="468" y="680" width="108" height="12" rx="2" fill="#f5f5f5"/>
+  <text x="522" y="690" fill="#2e5aa8" font-size="8" font-family="monospace" text-anchor="middle" letter-spacing="0.04em">SEARCH / DELETE</text>
+  <line x1="324" y1="704" x2="736" y2="704" stroke="#2e5aa8" stroke-width="1" marker-end="url(#arrow-link)"/>
+
+  <!-- ACTIVATION BARS -->
+  <rect x="316" y="124" width="8" height="232" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="316" y="400" width="8" height="84" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="316" y="536" width="8" height="12" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="316" y="700" width="8" height="12" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="736" y="268" width="8" height="40" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="536" y="536" width="8" height="108" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="736" y="588" width="8" height="56" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+  <rect x="736" y="700" width="8" height="12" fill="rgba(45,49,66,0.06)" stroke="#4f5d75" stroke-width="0.8"/>
+
+  <!-- ACTOR BOXES -->
+  <rect x="48" y="36" width="120" height="40" rx="6" fill="#ececec" stroke="#2d3142" stroke-width="1"/>
+  <text x="108" y="60" fill="#2d3142" font-size="12" font-weight="600" text-anchor="middle">Claude Code</text>
+
+  <rect x="268" y="36" width="104" height="40" rx="6" fill="rgba(235,108,54,0.08)" stroke="#eb6c36" stroke-width="1"/>
+  <rect x="276" y="42" width="44" height="12" rx="2" fill="transparent" stroke="#eb6c36" stroke-width="0.8" stroke-opacity="0.5"/>
+  <text x="298" y="51" fill="#eb6c36" font-size="7" font-family="monospace" text-anchor="middle" letter-spacing="0.08em">PLUGIN</text>
+  <text x="320" y="64" fill="#2d3142" font-size="12" font-weight="600" text-anchor="middle">Mem0</text>
+
+  <rect x="476" y="36" width="128" height="40" rx="6" fill="rgba(45,49,66,0.05)" stroke="#4f5d75" stroke-width="1"/>
+  <rect x="484" y="42" width="52" height="12" rx="2" fill="transparent" stroke="#4f5d75" stroke-width="0.8" stroke-opacity="0.5"/>
+  <text x="510" y="51" fill="#7a8399" font-size="7" font-family="monospace" text-anchor="middle" letter-spacing="0.08em">DETACHED</text>
+  <text x="540" y="64" fill="#2d3142" font-size="12" font-weight="600" text-anchor="middle">flush_worker</text>
+
+  <rect x="680" y="36" width="120" height="40" rx="6" fill="rgba(45,49,66,0.03)" stroke="rgba(45,49,66,0.3)" stroke-width="1"/>
+  <rect x="688" y="42" width="28" height="12" rx="2" fill="transparent" stroke="rgba(45,49,66,0.3)" stroke-width="0.8"/>
+  <text x="702" y="51" fill="#7a8399" font-size="7" font-family="monospace" text-anchor="middle" letter-spacing="0.08em">API</text>
+  <text x="740" y="64" fill="#2d3142" font-size="12" font-weight="600" text-anchor="middle">Mem0 Platform</text>
+</svg>
@@ -1,5 +1,7 @@
 ---
 title: Overview
+seo:
+  title: "Integrations Overview - Mem0"
 description: "Overview of Mem0 integrations with popular AI frameworks and tools for persistent memory and context management."
 ---

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

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

 ## Integrations
@@ -22,9 +22,9 @@ pip install mem0ai agentops python-dotenv
 ```

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

 ## Basic Integration Example

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

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

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

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

 ## Prerequisites

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

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

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

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

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

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

 ## What's Included

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

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

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

 ## Lifecycle Hooks

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

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

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

 ## Troubleshooting

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

 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
@@ -19,7 +19,7 @@ pip install autogen mem0ai openai python-dotenv

 First, we'll import the necessary libraries and set up our configurations.

-<Note>Remember to get the Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-autogen" rel="nofollow">Mem0 Platform</a>.</Note>
+<Note>Remember to get the Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-autogen">Mem0 Platform</a>.</Note>

 ```python
 import os
@@ -1,5 +1,7 @@
 ---
 title: AWS Bedrock
+seo:
+  title: "AWS Bedrock Integration with Mem0"
 description: "Use Mem0 with AWS Bedrock and OpenSearch Service for cloud-native persistent semantic memory storage."
 ---

@@ -18,7 +18,7 @@ In this guide, you'll:
 - **Python 3.12+**
 - **[uv](https://docs.astral.sh/uv/)**: Python package manager
 - **Node.js 18+** and **npm**: only needed if using the web console
- A **Mem0 API key** from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev" rel="nofollow">app.mem0.ai</a>
+- A **Mem0 API key** from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev">app.mem0.ai</a>
 - An **OpenAI API key** (or another LLM provider supported by ChatDev)

 ## Setup and Configuration
@@ -39,7 +39,7 @@ cd frontend && npm install && cd ..

 Set up your environment variables in a `.env` file:

-<Note>Get your Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev" rel="nofollow">Mem0 Platform</a>.</Note>
+<Note>Get your Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev">Mem0 Platform</a>.</Note>

 ```bash
 MEM0_API_KEY=your-mem0-api-key
@@ -194,7 +194,7 @@ This means retrieval returns memories from **both** the user's scope and the age

 | Field | Required | Description |
 |-------|----------|-------------|
-| `api_key` | Yes | Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev" rel="nofollow">app.mem0.ai</a> |
+| `api_key` | Yes | Mem0 API key from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev">app.mem0.ai</a> |
 | `user_id` | No | Scope memories to a specific user |
 | `agent_id` | No | Scope memories to a specific agent |

@@ -216,9 +216,9 @@ This means retrieval returns memories from **both** the user's scope and the age

 - **No memories returned on first run**: This is expected. Memories are stored *after* the agent responds, so the first interaction has no prior context. Memories appear starting from the second interaction onward.
 - **`mem0ai` not installed**: If you see `ImportError: mem0ai is required for Mem0Memory`, run `uv add mem0ai` or `pip install mem0ai` to add the dependency.
- **Invalid API key**: A wrong or expired `MEM0_API_KEY` will log errors like `Mem0 search failed` or `Mem0 add failed` but won't crash the agent. Check your key at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev" rel="nofollow">app.mem0.ai</a>.
+- **Invalid API key**: A wrong or expired `MEM0_API_KEY` will log errors like `Mem0 search failed` or `Mem0 add failed` but won't crash the agent. Check your key at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev">app.mem0.ai</a>.
 - **Pipeline headers in memories**: ChatDev automatically strips internal pipeline headers (e.g., `=== INPUT FROM TASK (user) ===`) before sending text to Mem0, so your memories stay clean.
- **Clearing test memories**: To delete memories created during testing, use the Mem0 dashboard at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev" rel="nofollow">app.mem0.ai</a> or the Python SDK: `MemoryClient().delete_all(user_id="your-test-user")`.
+- **Clearing test memories**: To delete memories created during testing, use the Mem0 dashboard at <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-chatdev">app.mem0.ai</a> or the Python SDK: `MemoryClient().delete_all(user_id="your-test-user")`.

 ## Key Features

@@ -7,7 +7,7 @@ Add persistent memory to [**Claude.ai**](https://claude.ai) (the hosted web app,

 ## Prerequisites

-1. A Mem0 Platform account: <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-claude-ai" rel="nofollow">sign up at app.mem0.ai</a>
+1. A Mem0 Platform account: <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-claude-ai">sign up at app.mem0.ai</a>
 2. A Claude.ai account on any plan (free, Pro, Max, Team, or Enterprise)

 You don't need an API key up front: the connector uses browser-based sign-in the first time Claude calls a Mem0 tool (see [Signing in](#signing-in)).
@@ -1,189 +1,176 @@
 ---
 title: Claude Code
-description: "Add persistent memory to Claude Code and Claude Cowork with the Mem0 plugin: MCP server, lifecycle hooks, and SDK skill."
+description: "Persistent cross-session memory for Claude Code. Install once, memories are captured automatically and recalled in every future session."
 ---

-Add persistent memory to [**Claude Code**](https://docs.anthropic.com/en/docs/claude-code) (CLI) and **Claude Cowork** (desktop app) with the Mem0 plugin. Your agent forgets everything between sessions. 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.
+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

-Before setting up Mem0 with Claude Code, ensure you have:
+1. A Mem0 Platform account and API key (starts with `m0-`):
+   - [Sign up at app.mem0.ai](https://app.mem0.ai?utm_source=oss&utm_medium=integration-claude-code)
+   - [Get your API key](https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-claude-code)

-1. A Mem0 Platform account and API key:
-   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-claude-code" rel="nofollow">Sign up at app.mem0.ai</a>
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-claude-code" rel="nofollow">Get your API key</a> (starts with `m0-`)
+2. A Claude Code version that supports plugin agents, worktree isolation for agents, and the `SubagentStart`, `SubagentStop`, and `PostToolUseFailure` hook events.

-2. Claude Code CLI or Claude Cowork desktop app installed
+3. Python 3.10+ and Git on your machine.

-3. Your API key added to your shell profile (persists across sessions):
-
-<CodeGroup>
-```bash zsh
-echo 'export MEM0_API_KEY="m0-your-api-key"' >> ~/.zshrc
-source ~/.zshrc
-```
-
-```bash bash
-echo 'export MEM0_API_KEY="m0-your-api-key"' >> ~/.bashrc
-source ~/.bashrc
-```
-</CodeGroup>
-
-Confirm it's set:
+## Quick start

 ```bash
-echo $MEM0_API_KEY
-# Should print: m0-your-api-key
+export MEM0_API_KEY='your-mem0-api-key'
+claude plugin marketplace add mem0ai/mem0
+claude plugin install mem0@mem0-plugins --scope user --config api_key="$MEM0_API_KEY"
+unset MEM0_API_KEY
 ```

-## Installation
+Restart Claude Code (or run `/reload-plugins`), open a Git repository, and work normally. That's it.

-### Option A: Plugin Marketplace (Recommended)
-
-Install the full plugin including MCP server, lifecycle hooks, and SDK skill.
-
-1. Add the Mem0 marketplace:
-
-   ```bash
-   claude plugin marketplace add mem0ai/mem0
-   ```
-
-2. Install the plugin:
-
-   ```bash
-   claude plugin install mem0@mem0-plugins
-   ```
-
-**Claude Cowork desktop app:** Open the Cowork tab, click **Customize** in the sidebar, click **Browse plugins**, and install Mem0.
-
-### Option B: MCP Only
-
-Add the Mem0 MCP server directly with a single command:
+### Managing the plugin

 ```bash
-npx mcp-add \
-  --name mem0-mcp \
-  --type http \
-  --url "https://mcp.mem0.ai/mcp/" \
-  --clients "claude code"
-```
-
-This gives you the MCP tools but not the lifecycle hooks or SDK skill.
-
-### Option C: Manual MCP Configuration
-
-Add to your Claude Code MCP config (`.mcp.json`):
-
-```json
-{
-  "mcpServers": {
-    "mem0": {
-      "type": "http",
-      "url": "https://mcp.mem0.ai/mcp/",
-      "headers": {
-        "Authorization": "Token ${MEM0_API_KEY}"
-      }
-    }
-  }
-}
-```
-
-### Managing the Plugin
-
-```bash
-claude plugin update mem0@mem0-plugins         # update the plugin to the latest version (restart to apply)
 claude plugin marketplace update mem0-plugins  # refresh the marketplace catalog
+claude plugin update mem0@mem0-plugins --scope user  # update the plugin (restart to apply)
 claude plugin uninstall mem0@mem0-plugins      # uninstall the plugin (keeps the marketplace)
-claude plugin marketplace remove mem0-plugins  # unregister the marketplace entirely
 ```

-<Info icon="check">
-  Start a new session and ask: *"List my mem0 entities"* or *"Search my memories for hello"*. If the `mem0` tools appear and respond, you're all set.
-</Info>
+## What you can do

-## Post-Installation: Run `/mem0:onboard`
+### Automatic memory

-After installing the plugin, start a new Claude Code session and run:
+Once installed, memory works without any action from you:

-```
-/mem0:onboard
-```
+- **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.

-This runs the setup wizard which:
-1. Verifies your API key and MCP connection
-2. Detects and imports project files (`CLAUDE.md`, `AGENTS.md`, `.cursorrules`)
-3. Installs coding-optimized memory categories
-4. Shows your identity (user ID, project scope, branch)
+### Commands

-The onboarding is idempotent and safe to re-run anytime. It auto-triggers on first session in a new project, but you can always invoke it manually.
+| Command | What it does |
+| --- | --- |
+| `/mem0:search` | Search memories from earlier sessions. Supports `--top-k <n>`, `--category <name>`, `--scope <repo\|dir\|mine>`, and `--run-id <session-id>`. |
+| `/mem0: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. |
+| `/mem0:resume` | Resume capture after a pause. |
+| `/mem0:remember` | Tell Claude to capture something specific in its reply. |

-## What's Included
+Categories for `--category`: `project_knowledge`, `decisions_and_constraints`, `workflows`, `problems_and_fixes`, `results`. Without it, all categories are searched.

-| Component | Plugin Install | MCP Only |
-|-----------|:--------------:|:--------:|
-| MCP Server (9 memory tools) | Yes | Yes |
-| Lifecycle Hooks | Yes | No |
-| Mem0 SDK Skill | Yes | No |
+### Search tool

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

-Once installed, the following tools are available in every Claude Code session:
+### Sidekick agent

-| Tool | Description |
-|------|-------------|
-| `add_memory` | Save text or conversation history for a user/agent |
-| `search_memories` | Semantic search across memories with filters |
-| `get_memories` | List memories with filters and pagination |
-| `get_memory` | Retrieve a specific memory by ID |
-| `update_memory` | Overwrite a memory's text by ID |
-| `delete_memory` | Delete a single memory by ID |
-| `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 |
+Sidekick is available only in Claude Code.

-## Lifecycle Hooks
-
-When installed via the plugin marketplace, Mem0 hooks into Claude Code's lifecycle to automatically manage memory:
-
-| Hook | Event | What it does |
-|------|-------|-------------|
-| **Setup** | `Setup` | Installs the mem0 SDK and dependencies (runs on init and maintenance) |
-| **Session start** | `SessionStart` | Loads prior memories and displays status banner |
-| **User prompt** | `UserPromptSubmit` | Searches relevant memories before each message; skips short prompts |
-| **Pre-tool (3 handlers)** | `PreToolUse` | Blocks MEMORY.md writes; enforces `user_id`/`app_id` on mem0 tool calls; scans files being read for relevant memory context |
-| **Post-tool** | `PostToolUse` | Tracks stats, scans bash errors for related memories |
-| **Stop** | `Stop` | Stores a session summary at the end of every assistant turn (not just at session end) |
-| **Pre-compact** | `PreCompact` | Stores a summary before the context is compacted |
-
-What you type is stored as yours. What Claude produces (session summaries and compaction summaries) is stored as the assistant's, so its suggestions never become your stated preferences.
-
-## Example Workflow
+`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
-# Session 1: Working on a feature
-You: Let's refactor the auth module to use JWT tokens instead of sessions.
+Ask Mem0's sidekick to investigate and implement this in its separate worktree.
+Review its result and send any corrections back to the same sidekick.
+```

-# Claude searches memories, finds nothing relevant, proceeds with the work.
-# Mem0 stores what you said as yours:
-#   - Your preference: "Prefers TypeScript, uses ESLint"
-# ...and what Claude did as the assistant's, in the session summary:
-#   - Decision: "Migrated auth from sessions to JWT tokens"
-#   - Files modified: auth/middleware.ts, auth/token.ts
+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.

-# Session 2 (days later): Related work
-You: Add refresh token rotation to the auth system.
+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.

-# Claude searches memories, retrieves the JWT migration context.
-# Knows the file structure, decisions made, and your stated preferences.
-# Continues seamlessly without re-explaining the codebase.
+## How it works
+
+The plugin follows a simple cycle: capture during a session, extract memories in the background, recall in the next session.
+
+<Frame>
+  <img src="/images/plugin-sequence.svg" alt="Sequence diagram: the first user prompt triggers search, hooks capture activity during the session, a background worker extracts memories after every five exchanges or on idle/exit, and the next session recalls them." />
+</Frame>
+
+**Step by step:**
+
+1. **Capture.** Hooks save the main agent's activity locally: user messages, Claude's answers, changed files, and short test/build results. Direct Sidekick lifecycle records stay local. Subagent results included in the main transcript can provide supporting evidence for extraction; the main agent's final response establishes the outcome. Capture does not call a model.
+
+2. **Flush.** After every five completed exchanges, a detached background worker sends that batch to Mem0. Large exchanges flush sooner. Ending or compacting the session flushes anything remaining. If the session sits idle, an auto-flush runs after five minutes (configurable with `MEM0_CODE_IDLE_FLUSH_SECONDS`). The timer resets on each new exchange. The worker survives Claude Code exiting.
+
+3. **Extract.** Each flush sends `add` calls with `agent_id` (the project identity), `user_id` (you), `app_id` (the repository), and `run_id` (the session). Prompts and responses are redacted without a character cutoff. Large conversations are split across requests without dropping message text. Mem0 classifies each extracted memory as shared project knowledge or a personal preference.
+
+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.
+
+## Memory scoping
+
+Each `add` call carries separate extraction instructions for project facts and personal facts. Mem0 sorts each memory into one of two buckets:
+
+- **Shared project memory** (keyed by `agent_id`, scoped by `app_id`): one namespace per repository. Stores conventions, decisions, constraints, commands that work, and commands that failed with what fixed them. Everyone on the repo reads and writes the same pool. Project memory never carries a `user_id`, so teammates' searches never mix in your preferences. Directory information is stored in metadata for directory-scoped searches.
+
+- **Personal memory** (keyed by `user_id`, scoped by `app_id`): your preferred tools, style, habits, and anything you asked to be remembered. Scoped to the repository by `app_id`, private to you.
+
+Credentials are redacted before anything leaves your machine.
+
+<Frame>
+  <img src="/images/memory-scoping-venn.svg" alt="Venn diagram showing one add call producing shared project memory (agent_id, visible to team) and personal memory (user_id, private to you). Search returns the union of both." />
+</Frame>
+
+## Search scope
+
+Every memory carries identifiers showing where it came from:
+
+| Identifier | What it is | Example |
+| --- | --- | --- |
+| `user_id` | You (personal memory only) | Your Mem0 user ID |
+| `agent_id` | The project identity (shared memory only) | `acme-payments-api-<hash>` |
+| `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 |
+| --- | --- |
+| `repo` (default) | All project memory across every subdirectory, plus your preferences |
+| `dir` | Project memory from the directory you're in (and its children), plus your preferences |
+| `mine` | Your personal preferences only |
+
+The `dir` scope is hierarchical: a parent directory sees everything in its children, but a child never sees the parent's memories.
+
+The search tool accepts an optional `run_id` with every scope (`repo`, `dir`, and `mine`); `/mem0:search` exposes it as `--run-id session-id`. It restricts both shared and personal results to memories saved in that coding-agent session. Omit it to search across sessions. This is a memory filter, not a label for the session making the request; automatically filtering by the current session would hide earlier-session memories. Each memory update still records the session's `run_id`. Set the default scope with the `search_scope` setting or `MEM0_CODE_SEARCH_SCOPE` env var.
+
+## Settings
+
+| Setting | Default | What it controls |
+| --- | --- | --- |
+| `api_key` | required | Mem0 Platform API key. |
+| `user_id` | local account name | User ID for memory storage. Resolved from: setting, `MEM0_CODE_USER_ID`, `MEM0_USER_ID`, `MEM0_RESOLVED_USER_ID`, `$USER`, `%USERNAME%`, then `default`. Set explicitly to share memories across machines. |
+| `top_k` | `3` | Max memories per explicit search (1 to 20). |
+| `max_context_chars` | `4000` | Max characters returned per search (1,000 to 10,000). |
+| `search_scope` | `repo` | Default scope: `repo`, `dir`, or `mine`. Also read from `MEM0_CODE_SEARCH_SCOPE`. |
+
+## Upgrading from 0.2.x
+
+Breaking update. Your memories carry over, most local config does not.
+
+- **Memories carry over.** Same user and repository scoping, including `~/.mem0/project_map.json`.
+- **Env vars still work.** `MEM0_API_KEY`, `MEM0_USER_ID`, `MEM0_PROJECT_ID`.
+- **Commands replaced.** Old commands replaced by `/mem0:search`, `/mem0:status`, `/mem0:forget`, `/mem0:pause`, `/mem0:resume`, `/mem0:remember`.
+- **MCP server replaced.** Nine read/write tools replaced by the single read-only `search_memories` tool.
+- **Local config ignored.** `~/.mem0/settings.json` and per-project `mem0.md` files are no longer read.
+- **Old memories remain searchable.** Pre-upgrade memories may use different categories. Omit category filters if an older memory is missing from the results.
+
+```bash
+claude plugin marketplace update mem0-plugins
+claude plugin update mem0@mem0-plugins --scope user
 ```

 ## Troubleshooting

- **"Connection failed"**: Verify `MEM0_API_KEY` is set in your shell: `echo $MEM0_API_KEY`. If empty, add it to your shell profile (see Prerequisites)
- **No tools appearing**: Restart your Claude Code session after installation
- **Memories not being captured**: Ensure you installed via the plugin marketplace (Option A) for lifecycle hooks. MCP-only installs require manual memory operations
- **"Mem0 Inactive" banner every session**: Your API key isn't persisting. Add `export MEM0_API_KEY="m0-..."` to your `~/.zshrc` (or `~/.bashrc`) and run `source ~/.zshrc`
+| Problem | Fix |
+| --- | --- |
+| Missing key | Reinstall with `--config api_key="$MEM0_API_KEY"` while the var is set. |
+| `401 Unauthorized` | API key is invalid or expired. Run `/mem0:status` to confirm. |
+| No memory after ending a session | Extraction runs in the background. Wait a moment, then search again. |
+| 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` |

 <CardGroup cols={2}>
  <Card title="Mem0 MCP Setup" icon="puzzle-piece" href="/platform/mem0-mcp">
@@ -1,21 +1,27 @@
 ---
 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/index/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/index/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

 Before setting up Mem0 with Codex, ensure you have:

 1. A Mem0 Platform account and API key:
-   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-codex" rel="nofollow">Sign up at app.mem0.ai</a>
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-codex" rel="nofollow">Get your API key</a> (starts with `m0-`)
+   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-codex">Sign up at app.mem0.ai</a>
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-codex">Get your API key</a> (starts with `m0-`)

 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">
@@ -22,7 +22,7 @@ pip install crewai crewai-tools mem0ai

 Import required modules and set up configurations:

-<Note>Remember to get your API keys from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-crewai" rel="nofollow">Mem0 Platform</a>, [OpenAI](https://platform.openai.com) and [Serper Dev](https://serper.dev) for search capabilities.</Note>
+<Note>Remember to get your API keys from <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-crewai">Mem0 Platform</a>, [OpenAI](https://platform.openai.com) and [Serper Dev](https://serper.dev) for search capabilities.</Note>

 ```python
 import os
@@ -1,21 +1,27 @@
 ---
 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

 Before setting up Mem0 with Cursor, ensure you have:

 1. A Mem0 Platform account and API key:
-   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-cursor" rel="nofollow">Sign up at app.mem0.ai</a>
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-cursor" rel="nofollow">Get your API key</a> (starts with `m0-`)
+   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-cursor">Sign up at app.mem0.ai</a>
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-cursor">Get your API key</a> (starts with `m0-`)

 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,30 +1,44 @@
 ---
 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

 1. A Mem0 Platform account and API key:
-   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-deepseek-plugin" rel="nofollow">Sign up at app.mem0.ai</a>
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-deepseek-plugin" rel="nofollow">Get your API key</a> (starts with `m0-`)
+   - <a href="https://app.mem0.ai?utm_source=oss&utm_medium=integration-deepseek-plugin">Sign up at app.mem0.ai</a>
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-deepseek-plugin">Get your API key</a> (starts with `m0-`)

 2. The DeepSeek Harness installed.

@@ -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. Anonymous usage events include operation names, durations, result counts, and coarse failure kinds. 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.
@@ -36,7 +36,7 @@ npx flowise start

 ### 2. Obtain Your Mem0 API Key

-1. Navigate to the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-flowise" rel="nofollow">Mem0 API Key dashboard</a>.
+1. Navigate to the <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-flowise">Mem0 API Key dashboard</a>.
 2. Generate or copy your existing Mem0 API Key.

 ### 3. Configure Mem0 Credentials
@@ -61,7 +61,7 @@ Test your memory configuration:

 1. Save your Flowise configuration
 2. Run a test chat and store some information
-3. Verify the stored memories in the <a href="https://app.mem0.ai/dashboard/requests?utm_source=oss&utm_medium=integration-flowise" rel="nofollow">Mem0 Dashboard</a>
+3. Verify the stored memories in the <a href="https://app.mem0.ai/dashboard/requests?utm_source=oss&utm_medium=integration-flowise">Mem0 Dashboard</a>

 ### 2. Memory Retention

@@ -88,7 +88,7 @@ Available settings include:

 ### Platform Configuration

-Additional settings available in <a href="https://app.mem0.ai/dashboard/project-settings?utm_source=oss&utm_medium=integration-flowise" rel="nofollow">Mem0 Project Settings</a>:
+Additional settings available in <a href="https://app.mem0.ai/dashboard/project-settings?utm_source=oss&utm_medium=integration-flowise">Mem0 Project Settings</a>:

 1. **Custom Instructions**: Define memory extraction rules
 2. **Expiration Date**: Set automatic memory cleanup periods
@@ -22,10 +22,10 @@ pip install google-adk mem0ai python-dotenv
 ```

 Set up your API keys:
-   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-google-ai-adk" rel="nofollow">Mem0 API Key</a>
+   - <a href="https://app.mem0.ai/dashboard/api-keys?utm_source=oss&utm_medium=integration-google-ai-adk">Mem0 API Key</a>
   - Google AI Studio API Key

-<Note>Remember to get your API key from <a href="https://app.mem0.ai" rel="nofollow">Mem0 Platform</a> and set up a [Google AI Studio API Key](https://aistudio.google.com/apikey).</Note>
+<Note>Remember to get your API key from <a href="https://app.mem0.ai">Mem0 Platform</a> and set up a [Google AI Studio API Key](https://aistudio.google.com/apikey).</Note>

 ```python
 import os
@@ -1,39 +1,35 @@
 ---
 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 long-term memory to Hermes agents with Mem0: managed Platform, a self-hosted server, or fully local OSS — with current-turn recall and background fact extraction."
 ---

-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. 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 for the current question, without slowing down the chat.

-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 — so a slow backend never blocks a turn.

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

-### 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.
-
 ## 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` (default `false`, 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) |
@@ -61,7 +57,7 @@ hermes memory setup

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

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

 ### Option 2: Manual Configuration

@@ -79,6 +75,36 @@ memory:

 That's it. Mem0 runs automatically from here.

+## 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 "Self-hosted server", and enter the server URL
+```
+
+### With flags
+
+```bash
+hermes memory setup mem0 --mode selfhosted \
+  --host http://localhost:8888 \
+  --api-key your-admin-api-key
+```
+
+### With environment variables
+
+```bash
+echo "MEM0_HOST=http://localhost:8888" >> ~/.hermes/.env
+echo "MEM0_API_KEY=your-admin-api-key" >> ~/.hermes/.env
+```
+
+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 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.
@@ -111,15 +137,20 @@ hermes memory setup mem0 --mode oss \

 | Flag | Description |
 |------|-------------|
-| `--mode` | `platform` or `oss` |
+| `--mode` | `platform`, `selfhosted`, or `oss` |
+| `--api-key` | Platform API key, or the admin key of a self-hosted server |
+| `--host` | Self-hosted server URL (with `--mode selfhosted`) |
 | `--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-embedder-model` | Override the embedder model |
+| `--oss-embedder-url` | Embedder base URL (for `ollama` or a custom endpoint) |
 | `--oss-vector` | Vector store (`qdrant` or `pgvector`, default `qdrant`) |
 | `--oss-vector-path` | Local Qdrant storage path |
+| `--oss-vector-url` | Qdrant server URL |
 | `--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 |
@@ -127,7 +158,7 @@ hermes memory setup mem0 --mode oss \

 ## Switching Modes

-You can move between Platform and OSS at any time. Run the setup command again, or edit `~/.hermes/mem0.json` directly.
+You can move between the three modes at any time. Run the setup command again, or edit `~/.hermes/mem0.json` directly.

 ```bash
 # Platform to OSS
@@ -136,6 +167,9 @@ hermes memory setup mem0 --mode oss --oss-llm-key sk-...
 # OSS to Platform
 hermes memory setup mem0 --mode platform --api-key sk-...

+# Platform to a self-hosted server
+hermes memory setup mem0 --mode selfhosted --host http://localhost:8888
+
 # Preview without writing anything
 hermes memory setup mem0 --mode oss --oss-llm-key sk-... --dry-run
 ```
@@ -146,7 +180,7 @@ A self-hosted `~/.hermes/mem0.json` looks like this:
 {
  "mode": "oss",
  "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"}}
  }
@@ -159,11 +193,12 @@ Behavioral settings live in `~/.hermes/mem0.json` and are written for you by `he

 | 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` |
+| `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` | `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` | Rerank search results for relevance (Platform mode only) |

 ### Cross-channel memories

@@ -174,12 +209,11 @@ Hermes can run from the CLI and from gateways like Telegram, Slack, and Discord.

 Either way, every write is tagged with `metadata.channel` (for example `telegram` or `cli`), so per-channel views are still possible at query time.

-
 ## 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.
+- **Non-blocking**: fact extraction runs in a background daemon thread, and current-turn recall waits at most 3 seconds, so a slow or failed call never blocks your conversation.
+- **Thread-safe**: the client uses lazy initialization with locking, and the background sync and recall threads are guarded so concurrent gateway messages cannot produce duplicate memories.

 ## Troubleshooting

@@ -188,6 +222,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
@@ -217,8 +252,8 @@ curl http://localhost:11434/api/tags

 ## Key Features

-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.
+1. **Three ways to run**: managed Platform, a self-hosted server, or fully local OSS, switchable at any time.
+2. **Current-turn recall**: memories for the current question are injected within a 3-second window, with `mem0_search` as the model's own backstop.
 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`).
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Pratik	1f68430471	test(profiles): use placeholder ids in the job response fixture The fixture carried a real job_id and event_id from a live generation. The shape is what the test needs, not the values, and this repo is public.	2026-09-23 10:49:16 -07:00
Pratik	1121efe365	docs(profiles): match the job create response in openapi The 202 body documented usage_units and a results array. The API returns entity_count_reserved, event_id and, for sample jobs, entity_ids; results only appears on GET /v2/profiles/jobs/{id}/. The SDK types already use entityCountReserved and entityIds, so the spec was the one out of step. The docs sample example indexes entity_ids with .get(), matching the notebook and the TS example's ?? [].	2026-09-23 10:29:15 -07:00
karthik	be1ded5793	fix(profiles): address SDK/docs review for user profiles v1 Addresses @kartik-mem0's review on mem0#7340, verified against the live staging profiles API on a neuron: - generate_profile / sample_profiles accept a caller-supplied idempotency_key, so retrying a lost request reuses the job instead of creating a second billable one (Python sync+async and TS) - TS uses the uuid dependency instead of the global crypto.randomUUID(), which throws on the supported Node 18 target - update_profile_settings distinguishes an omitted argument from an explicit None, so schema / custom_instructions can be cleared (Python sentinel) - export ProfileJobResponse and ProfileJobStatus; drop the deprecated ProfileTriggerResponse / ProfileSamplesResponse aliases and the unpopulated results field; correct usageUnits -> entityCountReserved; add error to ProfileResponse - openapi: nest schema / custom_instructions under entities in the settings request and response, add capabilities, and mark entity_type required on the job body - docs sample example polls to a terminal job status with a timeout, then reads the create response's entity_ids (status.results raised KeyError) - notebook: include PARTIALLY_SUCCEEDED in terminal states, raise on timeout, and snapshot/restore project settings so a shared env is left as found - tests: real job_id create shape, idempotency-key reuse, and clear-with-None Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-23 22:56:48 +05:30
karthik	f29820886a	docs(profiles): make user-profiles guide and notebook user-only Remove leftover agent and regenerate references so the docs match the shipped v1 SDK: drop the entity_type settings argument and the agent entities example from the guide, and remove the regenerate demo section and cheat-sheet row from the notebook. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-23 19:53:41 +05:30
karthik	d91d793c52	chore(profiles): bump SDKs and add changelog for user profiles v1 Python mem0ai 2.0.20 -> 2.1.0, TypeScript mem0ai 3.1.8 -> 3.2.0 (minor: new user-profiles methods). Add matching sdk.mdx entries under the Python and TypeScript tabs to satisfy the changelog CI gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-23 19:53:34 +05:30
karthik	48ae36ad94	feat(profiles): user-only SDK for v1 (drop regenerate + agent) Reduce the User Profiles SDK to the shipped v1 scope: user profiles only, no full rebuild. - Remove regenerate_profiles / regenerateProfiles (sync + async, Python + TS) and the ProfileRegenerateResponse type. Full rebuild is gated off server-side (409 not_yet_available). - Drop the entity_type / entityType parameter from get_profile, generate_profile, sample_profiles, and update_profile_settings; every path and payload is scoped to "user". Narrow ProfileEntityType to "user". - Update tests to the user-only surface. Endpoint paths (/v2/profiles/jobs/, /v2/profiles/settings/, /v2/entities/user/{id}/profile/) and the per-job Idempotency-Key are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-23 19:50:48 +05:30
Pratik	949b026991	fix(profiles): correct the settings shape, job entity_type and status type Four bugs that made the profile SDK unusable against the live API, each found by running the demo notebook end to end rather than by reading. 1. `update_profile_settings()` sent a flat body: {"enabled": ..., "schema": ..., "custom_instructions": ...} The API takes only `enabled` and `entities` at the top level and answers 400 "Unsupported settings: custom_instructions, schema." to anything else, so every call passing a schema failed. `get_profile_settings()` already returned the nested shape, so the read and the write disagreed and the method could not round-trip its own settings. Both SDKs now nest `schema` and `custom_instructions` under `entities.<entity_type>` while keeping the flat call signature; `entity_type` is a new optional argument defaulting to "user". 2. `sample_profiles()` and `regenerate_profiles()` never sent `entity_type`. Every profile job must name an entity kind, so both failed with "entity_type must be one of: user, agent." 3. The TypeScript read path rewrote the customer's schema property names. Once the schema moved under `entities`, `snakeToCamelKeys` camel-cased the keys inside it, because only a top-level schema was restored verbatim. A field named `favorite_topics` came back as `favoriteTopics`. 4. `ProfileStatus` declared `notEnabled` and `insufficientData`, but a status is a value, not a key, so it is never camel-cased. tsc rejected `status === "insufficient_data"`, which is true at runtime, and accepted `status === "insufficientData"`, which can never fire. Branching on status is the documented way to use a profile, so the type steered every TypeScript caller into a dead branch. Response-shape corrections found alongside them: sample returns `entity_ids` on create and a richer `results` array on the job, so the TS `results` field on the create response is marked deprecated and never set; regenerate answers 409, not the 501 the docstrings claimed. Verified against a live environment, from both SDKs: a settings write followed by a read returns the schema property for property, a partial update no longer blanks it, sample returns 202 with the entities it picked, regenerate reaches the server and answers its real not_yet_available, and a user with no profile returns "insufficient_data". Adds a user-profiles demo notebook covering the whole loop: schema, ingestion, generation, a before/after diff of a profile rewriting itself, schema sampling, and a failure-scenario section for each way the API says no. It polls the add event to a terminal status instead of sleeping, waits for the extracted memory count to settle rather than trusting the first page, and reports plainly when generation cannot finish instead of presenting an empty profile as a result. Executed end to end: 0 failing cells. - python: 20 passed (tests/test_client_profiles.py) - typescript: 203 passed (src/client/tests/)	2026-09-18 17:10:31 -07:00
Pratik	414aef6f1a	docs(profiles): drop the sidebar icon and the plan table Review feedback from Rudraj on the docs preview. The sidebar icon made Profiles the only entry in platform/features with one; every sibling page has no icon, so it read as a rendering accident. The plan table stated Pro/Enterprise availability, which is not how the feature is reaching customers: it is enabled per organization on request while in beta. A table naming tiers invites a self-serve upgrade that does not turn it on. Keeps the two conditions that are not about pricing — schema configured and an entity-scoped memory — and the note that a disabled project reads back not_enabled rather than erroring.	2026-09-18 17:10:03 -07:00
karthik	9192b9b565	docs(profiles): make profiles docs user-only and match the shipped API Hide agent profiles for this release (backend exists but is gated off) and sync the guide, api-reference, openapi, and llms.txt to the User Profiles feature head. Agent removal: - Drop "users and agents" framing, the entity_type="agent" get_profile example, and the "profiles for agents" FAQ from the guide. - Reduce entity_type to user-only in the read path/param/response and the jobs request body in openapi.json; drop "or agent" from the api-ref and llms.txt descriptions. Code sync (verified against the feature head): - Read example + prose now include generation_count alongside profile, status, entity_type, entity_id, updated_at. - Sample flow corrected: sample_profiles returns a job; poll get_profile_job and read each result's entity, instead of iterating a non-existent results field on the create response. - Bulk regenerate is gated off for v1 (FULL_REBUILD_ENABLED=False): remove it from the guide, openapi operation enum, and the 501 note; keep only sample and trigger. Idempotency-Key marked required to match the backend. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-18 03:49:32 +05:30
karthik	4b9a27aac1	fix(profiles): format TS SDK profile client with prettier The ts-sdk CI Lint step (npx prettier --check .) failed on the three profile client files, which also failed the aggregate CI Gate. Reformat them with prettier 3.8.4 (the pinned devDependency); whitespace only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-18 03:18:19 +05:30
Pratik	34894e2cea	fix(profiles): follow the jobs API Four POST routes became one collection with the operation in the body, so the three route pages collapse into one. samples became sample. Creates send an Idempotency-Key and return a status_url to poll, which the client follows rather than building the path. Full rebuild is closed: regenerate_profiles answers 501 not_yet_available and the docs say so instead of teaching a daily cadence that cannot run.	2026-09-16 17:02:10 -07:00
karthik	c4eea87526	Merge branch 'main' into user/karthik/user-profiles-docs	2026-09-15 22:12:30 +05:30
karthik	b852f9240c	docs(profiles): correct response example and regenerate cadence from live API Live e2e against the feature neuron: the profile envelope has no generation_count, and the regenerate cooldown is once per day (86400s), not hourly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-15 21:46:53 +05:30
karthik	ac2c5cbfbf	docs(profiles): add plan availability, cadence, and FAQ to the profiles guide Model the profiles feature guide on the Dream guide: add a Plan availability table with eligibility criteria, a 'When profiles update' cadence section, a schema size-budget note, and an FAQ. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-09-15 21:38:00 +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
Pratik	623e33f2db	feat(profiles): SDK methods and docs for entity profiles Adds the profile surface to both SDKs and documents it. Python (MemoryClient + AsyncMemoryClient) and TypeScript gain: get/generate profile, get/update settings, sample, regenerate. A profile's keys come from the customer's own JSON Schema, so the TS client keeps `profile` opaque and passes `schema` through untouched in both directions. Camel-casing them would return field names that do not match the schema the customer wrote. Reads use the v2 envelope, where a known entity with no profile yet is a 200 carrying a status rather than a 404, so an empty state is distinguishable from an error. Verified against a live environment running this API: settings round-trip, a partial update leaves the schema intact, generation produces a profile under the configured schema, and sample, regenerate, cooldown and the 400/404 paths all answer as documented.	2026-09-10 16:04:09 -07:00
Kartik	d873892dad	feat(plugins)!: make Sidekick exclusive to Claude Code (#7278 )	2026-09-10 20:51:50 +05:30
Kartik	02f7a9b2c4	docs: align agent plugin guides with shared runtime behavior (#7269 )	2026-09-09 01:03:26 +05:30
Kartik	73e7b8763a	refactor(integrations): shared agent plugin runtimes and native adapters (#7203 )	2026-09-08 23:32:25 +05:30
Kartik	dae67f74f5	fix(docs): SEO improvements for page titles, internal links, and URL structure (#7224 )	2026-09-04 20:32:23 +05:30
Kartik	9a7924befd	chore(release): bump Python and TypeScript SDK patch versions (#7210 )	2026-09-02 18:44:55 +05:30
Kartik	3cf41878ea	fix: replace PostHog evaluate_flags with static config for OSS notices (#7185 )	2026-09-02 18:00:01 +05:30
Elif Sema Balcioglu	c33ca27f5e	docs: fix Oracle vector store setup and search examples (#7111 )	2026-09-01 19:19:48 +05:30
Kartik	71fba8d464	feat(claude-code-plugin): move the Claude Code plugin to its own integration and ship it as 0.3.0 (#7106 )	2026-09-01 02:34:45 +05:30
Kartik	19cb89aff4	docs: add 301 redirects for 49 legacy 404 pages (#7161 )	2026-08-28 17:44:10 +05:30