test(plugins): a removed plugin setting gives way to a later mem0 init key

mcp_server.py never calls configure_harness, so it resolved ~/.mem0/mem0-plugin while the Cursor, Kimi and Antigravity hooks use ~/.mem0/<host>-plugin. A key set in Cursor's plugin settings and cached by the sessionStart hook was invisible to search_memories. build.py now writes DATA_DIR_NAME into each bundle's _harness_id.py and memory_core seeds its default from it, like the PLATFORM_* values.

An end-to-end test launches the real session-start hook and MCP server for Claude Code, Cursor and Codex the way each host does, with the key in plugin settings and in the mem0 init config, and checks the search reaches the API with that key.

Bumps the Python plugins to 0.3.4, OpenCode to 0.4.2, Pi and DeepSeek to 0.3.3, with changelog entries for each.

Fixes #7346

.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "mem0",
       "source": "./integrations/claude-code-plugin",
       "description": "Cross-session memory and token savings for coding agents.",
-      "version": "0.3.3"
+      "version": "0.3.4"
     }
   ]
 }

.cursor-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "mem0",
       "source": "./integrations/cursor-plugin",
       "description": "Cross-session memory and token savings for coding agents.",
-      "version": "0.3.3"
+      "version": "0.3.4"
     }
   ]
 }

.kimi-plugin/marketplace.json

@@ -5,7 +5,7 @@
     {
       "id": "mem0",
       "displayName": "Mem0",
-      "version": "0.3.3",
+      "version": "0.3.4",
       "description": "Cross-session memory and token savings for coding agents.",
       "homepage": "https://mem0.ai",
       "keywords": ["memory", "personalization", "mcp", "semantic-search"],

docs/api-reference.mdx

@@ -3,7 +3,7 @@ title: "API Reference Overview"
 sidebarTitle: "Overview"
 icon: "terminal"
 iconType: "solid"
-description: "Explore the Mem0 REST API for adding, searching, updating, and deleting memories, plus managing users, organizations, projects, and webhooks."
+description: "REST APIs for memory management, search, and entity operations"
 ---
 
 ## Mem0 REST API

docs/api-reference/dream/dream-preview.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Preview Dream Scope"
+description: "A no-write preview of the scope Dream synthesis would analyze for a project."
 openapi: "post /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/preview/"
 ---

docs/api-reference/dream/get-dream-activity.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get Dream Activity"
+description: "Supersede/merge activity feed for a project, newest first (keyset-paginated)."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/activity/"
 ---

docs/api-reference/dream/get-dream-config.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get Dream Configuration"
+description: "Retrieve a project's Dream (memory synthesis) configuration and plan entitlements."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/config/"
 ---

docs/api-reference/dream/get-dream-memory-sources.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get a Synthesized Memory's Sources"
+description: "The source memories a synthesized (pattern) memory was distilled from."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/memory/{memory_id}/sources/"
 ---

docs/api-reference/dream/get-dream-run-memories.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get Memories in a Dream Run"
+description: "Keyset page of the synthesized memories within a single synthesis run."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/runs/{run_id}/memories/"
 ---

docs/api-reference/dream/get-dream-runs.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get Dream Synthesis Runs"
+description: "Synthesis activity grouped per run, newest first (keyset-paginated)."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/runs/"
 ---

docs/api-reference/dream/get-dream-stats.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Get Dream Stats"
+description: "Lifecycle and synthesis counts for a project, plus reflection freshness."
 openapi: "get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/stats/"
 ---

docs/api-reference/dream/update-dream-config.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Update Dream Configuration"
+description: "Enable or disable Synthesis (reflection) for a project, or change the reflection mode."
 openapi: "patch /api/v1/orgs/organizations/{org_id}/projects/{project_id}/dream/config/"
 ---

docs/api-reference/entities/delete-user.mdx

@@ -1,5 +1,5 @@
 ---
 title: 'Delete User'
-description: "Send a DELETE request to /v2/entities/{entity_type}/{entity_id}/ to permanently remove a user entity from your Mem0 project by ID."
+description: "Remove a user entity from the Mem0 platform by entity type and ID using the DELETE endpoint."
 openapi: delete /v2/entities/{entity_type}/{entity_id}/
 ---

docs/api-reference/entities/get-users.mdx

@@ -1,5 +1,5 @@
 ---
 title: 'Get Users'
-description: "Send a GET /v1/entities request to list every user entity in your Mem0 project, returning IDs, names, created_at, and metadata fields."
+description: "Retrieve a list of all user entities stored in the Mem0 platform using the GET endpoint."
 openapi: get /v1/entities/
 ---

docs/api-reference/events/get-event.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'Get Event'
-description: "Fetch details of a specific Mem0 event by its event_id, including status, payload, and completion info for async memory operations."
+description: "Retrieve details of a specific event by ID, including status and payload for async memory operations."
 openapi: get /v1/event/{event_id}/
 ---
 

docs/api-reference/events/get-events.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'Get Events'
-description: "List recent events for your Mem0 organization and project to power dashboards, alerting on FAILED writes, and audit logging pipelines."
+description: "List recent events for your organization and project, useful for dashboards, alerting, and audit logging."
 openapi: get /v1/events/
 ---
 

docs/api-reference/memory/add-memories.mdx

@@ -1,5 +1,6 @@
 ---
 title: Add Memories
+description: "Add facts, messages, or metadata to a user memory store with async processing and event tracking via the V3 additive pipeline."
 openapi: post /v3/memories/add/
 ---
 

docs/api-reference/memory/batch-delete.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Batch Delete Memories'
+description: "Delete multiple memories in a single batch request using the Mem0 API DELETE endpoint."
 openapi: delete /v1/batch/
 ---

docs/api-reference/memory/batch-update.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Batch Update Memories'
+description: "Update multiple memories in a single batch request using the Mem0 API PUT endpoint."
 openapi: put /v1/batch/
----
+---

docs/api-reference/memory/create-memory-export.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Create Memory Export'
+description: "Submit an export job to create a structured memory export using a customizable Pydantic schema and filters."
 openapi: post /v1/exports/
 ---
 

docs/api-reference/memory/delete-memories.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Delete Memories'
+description: "Delete all memories matching specified filters from the Mem0 memory store using the DELETE endpoint."
 openapi: delete /v1/memories/
 ---

docs/api-reference/memory/delete-memory.mdx

@@ -1,5 +1,6 @@
 ---
 title: "Delete Memory API Endpoint"
 sidebarTitle: "Delete Memory"
+description: "Delete a single memory by its unique memory ID from the Mem0 platform using the DELETE endpoint."
 openapi: delete /v1/memories/{memory_id}/
 ---

docs/api-reference/memory/feedback.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Feedback'
+description: "Submit positive or negative feedback on memory results to help improve memory accuracy and relevance."
 openapi: post /v1/feedback/
 ---

docs/api-reference/memory/get-memories.mdx

@@ -1,5 +1,6 @@
 ---
 title: "Get Memories"
+description: "Retrieve memories with paginated results and advanced filtering using logical operators like AND, OR, NOT, and comparison queries."
 openapi: post /v3/memories/
 ---
 

docs/api-reference/memory/get-memory-export.mdx

@@ -1,6 +1,7 @@
 ---
 title: 'Get Memory Export'
+description: "Retrieve the latest structured memory export after submitting an export job, with optional entity filters."
 openapi: post /v1/exports/get
 ---
 
-Retrieve the latest structured memory export after submitting an export job. You can filter the export by `user_id`, `agent_id`, `app_id`, `run_id`, `created_at`, or `updated_at` to get the most recent export matching your filters.
+Retrieve the latest structured memory export after submitting an export job. You can filter the export by `user_id`, `agent_id`, `app_id`, `run_id`, `created_at`, or `updated_at` to get the most recent export matching your filters.

docs/api-reference/memory/get-memory.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Get Memory'
+description: "Retrieve a single memory by its unique memory ID from the Mem0 platform using the GET endpoint."
 openapi: get /v1/memories/{memory_id}/
----
+---

docs/api-reference/memory/history-memory.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Memory History'
+description: "Retrieve the full change history of a specific memory to track how it has evolved over time."
 openapi: get /v1/memories/{memory_id}/history/
----
+---

docs/api-reference/memory/search-memories.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Search Memories'
+description: "Search memories with hybrid retrieval (semantic + BM25 + entity matching) and advanced filtering using logical and comparison operators."
 openapi: post /v3/memories/search/
 ---
 

docs/api-reference/memory/update-memory.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Update Memory API Endpoint"
 sidebarTitle: "Update Memory"
+description: "Update the content, metadata, timestamp, or expiration date of a single memory by its unique ID using the PUT endpoint."
 openapi: put /v1/memories/{memory_id}/
 ---
 

docs/api-reference/organization/add-org-member.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Add Organization Member API Endpoint"
 sidebarTitle: "Add Member"
+description: "Add a new member to an organization with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/members/
 ---
 

docs/api-reference/organization/create-org.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Create Organization'
+description: "Create a new organization on the Mem0 platform to manage projects, members, and memory resources."
 openapi: post /api/v1/orgs/organizations/
----
+---

docs/api-reference/organization/delete-org.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Delete Organization'
+description: "Permanently delete an organization and its associated resources from the Mem0 platform."
 openapi: delete /api/v1/orgs/organizations/{org_id}/
----
+---

docs/api-reference/organization/get-org-members.mdx

@@ -1,5 +1,6 @@
 ---
 title: "Get Organization Members API Endpoint"
 sidebarTitle: "Get Members"
+description: "Retrieve a list of all members belonging to a specific organization on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/members/
 ---

docs/api-reference/organization/get-org.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Get Organization'
+description: "Retrieve details of a specific organization by its ID from the Mem0 platform using the GET endpoint."
 openapi: get /api/v1/orgs/organizations/{org_id}/
----
+---

docs/api-reference/organization/get-orgs.mdx

@@ -1,5 +1,5 @@
 ---
 title: 'Get Organizations'
-description: "Call GET /api/v1/orgs/organizations to retrieve every organization tied to your Mem0 account, including IDs, names, and role metadata."
+description: "Retrieve a list of all organizations associated with your Mem0 account using the GET endpoint."
 openapi: get /api/v1/orgs/organizations/
 ---

docs/api-reference/organization/remove-org-member.mdx

@@ -1,5 +1,5 @@
 ---
 title: "Remove Organization Member"
-description: "Send a DELETE request to remove a member from a Mem0 organization and revoke their access to all of its projects, memories, and resources."
+description: "Remove a member from an organization to revoke their access to its projects and resources."
 openapi: "delete /api/v1/orgs/organizations/{org_id}/members/"
 ---

docs/api-reference/organization/update-org-member.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Update Organization Member"
+description: "Update an existing member's role within an organization to change their permissions and access level."
 openapi: "put /api/v1/orgs/organizations/{org_id}/members/"
 ---

docs/api-reference/organizations-projects.mdx

@@ -1,7 +1,7 @@
 ---
 title: Organizations & Projects
 icon: "building"
-description: "Manage multi-tenant Mem0 apps with the organizations and projects APIs, covering isolation, access control, API keys, and team collaboration."
+description: "Manage multi-tenant applications with organization and project APIs"
 ---
 
 ## Overview

docs/api-reference/profiles/generate-profiles.mdx

@@ -1,4 +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/
 ---

docs/api-reference/profiles/get-profile-job.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Get Generation Job'
+description: "Read the progress of a generation, and whether it finished."
 openapi: get /v2/profiles/jobs/{job_id}/
 ---

docs/api-reference/profiles/get-profile-settings.mdx

@@ -1,4 +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/
 ---

docs/api-reference/profiles/get-profile.mdx

@@ -1,4 +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/
 ---

docs/api-reference/profiles/update-profile-settings.mdx

@@ -1,4 +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/
 ---

docs/api-reference/project/add-project-member.mdx

@@ -1,6 +1,7 @@
 ---
 title: "Add Project Member API Endpoint"
 sidebarTitle: "Add Member"
+description: "Add a new member to a project with a specified role such as READER or OWNER access level."
 openapi: post /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---
 

docs/api-reference/project/create-project.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Create Project'
+description: "Create a new project within an organization on the Mem0 platform to isolate memory resources."
 openapi: post /api/v1/orgs/organizations/{org_id}/projects/
----
+---

docs/api-reference/project/delete-project.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Delete Project'
+description: "Permanently delete a project and its associated data from the Mem0 platform by project ID."
 openapi: delete /api/v1/orgs/organizations/{org_id}/projects/{project_id}/
----
+---

docs/api-reference/project/get-project-members.mdx

@@ -1,5 +1,6 @@
 ---
 title: "Get Project Members API Endpoint"
 sidebarTitle: "Get Members"
+description: "Retrieve a list of all members belonging to a specific project on the Mem0 platform."
 openapi: get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/
 ---

docs/api-reference/project/get-project.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Get Project'
+description: "Retrieve details of a specific project by its organization and project ID using the GET endpoint."
 openapi: get /api/v1/orgs/organizations/{org_id}/projects/{project_id}/
----
+---

docs/api-reference/project/get-projects.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Get Projects'
+description: "Retrieve a list of all projects within an organization on the Mem0 platform using the GET endpoint."
 openapi: get /api/v1/orgs/organizations/{org_id}/projects/
----
+---

docs/api-reference/project/remove-project-member.mdx

@@ -1,5 +1,5 @@
 ---
 title: "Remove Project Member"
-description: "Send a DELETE request to remove a member from a Mem0 project and revoke their access to its memories, settings, API keys, and resources."
+description: "Remove a member from a project to revoke their access to its memories, configuration, and resources."
 openapi: "delete /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/"
 ---

docs/api-reference/project/update-project-member.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Update Project Member"
+description: "Update an existing member's role within a project to change their permissions and access level."
 openapi: "put /api/v1/orgs/organizations/{org_id}/projects/{project_id}/members/"
 ---

docs/api-reference/project/update-project.mdx

@@ -1,4 +1,5 @@
 ---
 title: "Update Project"
+description: "Update a project's settings, including name, custom instructions, and other configuration options."
 openapi: "patch /api/v1/orgs/organizations/{org_id}/projects/{project_id}/"
 ---

docs/api-reference/webhook/create-webhook.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Create Webhook'
+description: "Create a new webhook for a project to receive real-time notifications about memory events."
 openapi: post /api/v1/webhooks/projects/{project_id}/
 ---
 

docs/api-reference/webhook/delete-webhook.mdx

@@ -1,4 +1,5 @@
 ---
 title: 'Delete Webhook'
+description: "Delete an existing webhook by its ID to stop receiving notifications for memory events."
 openapi: delete /api/v1/webhooks/{webhook_id}/
 ---

docs/api-reference/webhook/get-webhook.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Get Webhook'
+description: "Retrieve webhook configuration details for a specific project on the Mem0 platform."
 openapi: get /api/v1/webhooks/projects/{project_id}/
 ---
 

docs/api-reference/webhook/update-webhook.mdx

@@ -1,5 +1,6 @@
 ---
 title: 'Update Webhook'
+description: "Update an existing webhook configuration, such as its URL or event subscriptions, by webhook ID."
 openapi: put /api/v1/webhooks/{webhook_id}/
 ---
 

docs/changelog/highlights.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Highlights"
-description: "Highlights of major Mem0 product launches, headline features, integrations like n8n and Zapier, and milestones across the platform and SDKs."
+description: "Major product launches, headline features, and milestones for Mem0."
 mode: "wide"
 ---
 

docs/changelog/platform.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Platform"
-description: "Release notes for the Mem0 hosted platform covering backend APIs, dashboard, billing, temporal reasoning, search, and infrastructure updates."
+description: "Release notes for the Mem0 hosted platform: backend, dashboard, billing, and infrastructure changes."
 mode: "wide"
 ---
 

docs/changelog/sdk.mdx

@@ -1,24 +1,12 @@
 ---
 title: "SDK & Tools"
-description: "Release notes for the Mem0 Python SDK, TypeScript SDK, Vercel AI SDK, CLI, and editor plugins, including new vector stores and bug fixes."
+description: "Release notes for the Mem0 Python SDK, TypeScript SDK, Vercel AI SDK, CLI, and editor plugins."
 mode: "wide"
 ---
 
 <Tabs>
 <Tab title="Python">
 
-<Update label="2026-09-25" description="v2.2.1">
-
-**Bug Fixes:**
-- **Core:** `add()` (`Memory` and `AsyncMemory`) no longer reports records the vector store rejected as successful `ADD` events. Only records that were actually inserted are written to history, entity-linked, and returned. If none of the extracted memories could be inserted, `add()` now raises `VectorStoreError` instead of returning memories that were never stored ([#7066](https://github.com/mem0ai/mem0/pull/7066))
-- **Core:** Restore the context-manager protocol on `Memory` (`with Memory() as m:`) and `AsyncMemory` (`async with AsyncMemory() as m:`), which closes the instance on exit ([#7354](https://github.com/mem0ai/mem0/pull/7354))
-- **LLMs:** The AWS Bedrock Anthropic path now returns the first Converse content block that carries text instead of always reading `content[0]`. Claude reasoning models can emit a `reasoningContent` block before the text block, which previously made the call fail with a `KeyError` ([#6369](https://github.com/mem0ai/mem0/pull/6369))
-- **Vector Stores:** Turbopuffer filters now apply every operator (`eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`). Only `gte` and `lte` were read before, so any other operator was silently dropped and the query returned unfiltered results. An unsupported operator now raises `ValueError` ([#6564](https://github.com/mem0ai/mem0/pull/6564))
-- **Vector Stores:** Turbopuffer `search()` scores now respect `distance_metric`. With `euclidean_squared`, the unbounded squared distance maps to `1 / (1 + distance)` instead of `1 - distance`, which went negative and inverted ranking for any distance above 1 ([#6559](https://github.com/mem0ai/mem0/pull/6559))
-- **Vector Stores:** S3 Vectors `search()` scores are now metric-aware. With `euclidean`, the distance maps to `1 / (1 + distance)` instead of `max(0, 1 - distance)`, which collapsed most scores to 0 ([#6547](https://github.com/mem0ai/mem0/pull/6547))
-
-</Update>
-
 <Update label="2026-09-23" description="v2.2.0">
 
 **New Features:**
@@ -1257,16 +1245,6 @@ See the [OSS v2 to v3 migration guide](https://docs.mem0.ai/migration/oss-v2-to-
 
 <Tab title="TypeScript">
 
-<Update label="2026-09-25" description="v3.3.1">
-
-**Bug Fixes:**
-- **Config (OSS):** `ConfigManager` no longer injects OpenAI's default `baseURL` and `model` into non-OpenAI LLM providers. The defaults now apply only to `openai` and `openai_structured`, so a DeepSeek, xAI, or other provider config without an explicit `baseURL` or `model` falls back to that provider's own defaults and env vars (`DEEPSEEK_API_BASE`, `XAI_API_BASE`, ...) instead of pointing at OpenAI with an OpenAI model name ([#7350](https://github.com/mem0ai/mem0/pull/7350))
-- **Vector Stores:** Turbopuffer filters now apply every operator (`eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`). Only the range operators were read before, so `eq`, `ne`, `in`, and `nin` were silently dropped. A `"*"` value now matches anything instead of nothing, an array value is treated as `in`, and an unsupported operator throws ([#6578](https://github.com/mem0ai/mem0/pull/6578))
-- **Vector Stores:** Turbopuffer `search()` with `euclidean_squared` now maps the unbounded squared distance to `1 / (1 + distance)` instead of `1 - distance`, which went negative and inverted ranking for any distance above 1 ([#6580](https://github.com/mem0ai/mem0/pull/6580))
-- **Packaging:** `pg`, `@types/pg`, and `natural` are now optional peer dependencies, and `pg` / `@types/pg` accept caret ranges instead of the exact `8.11.3` / `8.11.0` pins, so installing `mem0ai` no longer pulls in `pg` or conflicts with an app's own `pg` version. The PGVector store now imports `pg` only when it is used, so install it alongside `mem0ai` (`npm install pg`) if you use that store. `@types/jest` moved from peer dependencies to dev dependencies ([#7450](https://github.com/mem0ai/mem0/pull/7450))
-
-</Update>
-
 <Update label="2026-09-23" description="v3.3.0">
 
 **New Features:**
@@ -2122,6 +2100,16 @@ A full-featured command-line interface for Mem0, available in both Python and No
 <Tabs>
 <Tab title="Mem0 Plugin">
 
+<Update label="2026-09-25" description="Portable agent plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when no key is set in the plugin settings or `MEM0_API_KEY`, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Auth:** A plugin setting that reaches the plugin as an unexpanded `${api_key}` or `${user_id}` placeholder is treated as unset. It is no longer sent as the API key, cached to disk, or used as the user ID ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **State:** The `search_memories` MCP server now keeps its state in `~/.mem0/coding-agent-plugin`, the same directory the status, pause, resume and forget skills use, instead of `~/.mem0/mem0-plugin` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-08" description="Shared agent plugin runtime">
 
 **Changed:**
@@ -2433,6 +2421,15 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex
 
 <Tab title="Claude Code">
 
+<Update label="2026-09-25" description="Claude Code plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when no key is set in the plugin settings or `MEM0_API_KEY`, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Auth:** A plugin setting that reaches the plugin as an unexpanded `${api_key}` or `${user_id}` placeholder is treated as unset. It is no longer sent as the API key, cached to disk, or used as the user ID ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Claude Code plugin v0.3.3">
 
 **Improvements:**
@@ -2474,6 +2471,16 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex
 
 <Tab title="Cursor">
 
+<Update label="2026-09-25" description="Cursor plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** An API key set in the Cursor plugin settings now reaches the `search_memories` MCP server. The server looked for the cached key in `~/.mem0/mem0-plugin` while the hooks cached it in `~/.mem0/cursor-plugin`, so search asked for auth whenever Cursor did not pass the setting to the MCP server directly ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when no key is set in the plugin settings or `MEM0_API_KEY`, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Auth:** A plugin setting that reaches the plugin as an unexpanded `${api_key}` or `${user_id}` placeholder is treated as unset. It is no longer sent as the API key, cached to disk, or used as the user ID ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Cursor plugin v0.3.3">
 
 **Improvements:**
@@ -2514,6 +2521,14 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex
 
 <Tab title="Codex">
 
+<Update label="2026-09-25" description="Codex plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when `MEM0_API_KEY` is not set, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Codex plugin v0.3.3">
 
 **Improvements:**
@@ -2553,6 +2568,13 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex
 
 <Tab title="OpenCode">
 
+<Update label="2026-09-25" description="OpenCode plugin v0.4.2">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when neither `MEM0_API_KEY` nor a shell profile sets one, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="OpenCode plugin v0.4.1">
 
 **Improvements:**
@@ -2668,6 +2690,15 @@ Initial release of the Mem0 plugin for Claude Code and Cursor, followed by Codex
 
 <Tab title="Antigravity">
 
+<Update label="2026-09-25" description="Antigravity plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when `MEM0_API_KEY` is not set, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Data directory:** The `search_memories` MCP server uses `~/.mem0/antigravity-plugin`, the data directory the hooks use, instead of `~/.mem0/mem0-plugin` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Antigravity plugin v0.3.3">
 
 **Improvements:**
@@ -2781,6 +2812,15 @@ Existing memories written by the previous versions are not rewritten. If your me
 
 <Tab title="Kimi">
 
+<Update label="2026-09-25" description="Kimi Code plugin v0.3.4">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when `MEM0_API_KEY` is not set, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Data directory:** The `search_memories` MCP server uses `~/.mem0/kimi-plugin`, the data directory the hooks use, instead of `~/.mem0/mem0-plugin` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Packaging:** `PLUGIN_VERSION` bumped to `0.3.4`, so the `mem0-plugin/<version>` wire header and `plugin_version` telemetry field identify builds with this fix ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Kimi Code plugin v0.3.3">
 
 **Improvements:**
@@ -3139,6 +3179,13 @@ Existing memories written by the previous versions are not rewritten. If your me
 
 <Tab title="Pi Agent">
 
+<Update label="2026-09-25" description="Pi Agent plugin v0.3.3">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when neither `MEM0_API_KEY` nor `~/.pi/agent/mem0-config.json` sets one, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="Pi Agent plugin v0.3.2">
 
 **Improvements:**
@@ -3268,6 +3315,14 @@ Existing memories written by the previous versions are not rewritten. If your me
 
 <Tab title="DeepSeek Harness">
 
+<Update label="2026-09-25" description="deepseek-plugin v0.3.3">
+
+**Fixes:**
+- **Auth:** Falls back to the API key `mem0 init` saved in `~/.mem0/config.json` when neither `config.apiKey` nor `MEM0_API_KEY` is set, so search and the status check no longer report a missing key after `mem0 init` ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+- **Config:** An empty `apiKey` now counts as unset and falls through to `MEM0_API_KEY` and the `mem0 init` key, instead of failing validation ([#7449](https://github.com/mem0ai/mem0/pull/7449))
+
+</Update>
+
 <Update label="2026-09-23" description="deepseek-plugin v0.3.2">
 
 **Improvements:**

docs/components/embedders/models/fastembed.mdx

@@ -1,6 +1,6 @@
 ---
 title: "FastEmbed"
-description: "Run FastEmbed inside Mem0 to generate ONNX-based text embeddings locally on CPU without API keys, using models like gte-large or bge-small."
+description: "Configure FastEmbed as an embedding provider in Mem0 to generate embeddings locally using ONNX-based models without a GPU."
 ---
 
 You can use FastEmbed to run embedding models locally in Mem0. FastEmbed is an ONNX-based embedding library that runs efficiently on CPU without requiring a GPU or an external API key.

docs/components/embedders/models/huggingface.mdx

@@ -1,6 +1,6 @@
 ---
 title: Hugging Face
-description: "Use Hugging Face embeddings in Mem0 via local sentence-transformers or a Text Embeddings Inference (TEI) endpoint for fast, self-hosted vectors."
+description: "Configure Hugging Face as an embedding provider in Mem0 for local embedding generation with open-source models."
 ---
 
 You can use embedding models from Huggingface to run Mem0 locally.

docs/components/embedders/models/vertexai.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Vertex AI"
-description: "Use Google Cloud Vertex AI embeddings in Mem0 with ADC authentication, gemini-embedding-001, and task-specific types for add, update, and search."
+description: "Configure Google Cloud Vertex AI as an embedding provider in Mem0 with support for task-specific embedding types."
 ---
 ### Vertex AI
 

docs/components/llms/models/anthropic.mdx

@@ -1,6 +1,6 @@
 ---
 title: Anthropic
-description: "Use Anthropic Claude models such as claude-sonnet-4-6 as your Mem0 LLM with the ANTHROPIC_API_KEY, plus temperature and max token controls."
+description: "Configure Anthropic Claude models as the LLM provider in Mem0 with API key setup and usage examples."
 ---
 
 

docs/components/llms/models/deepseek.mdx

@@ -1,6 +1,6 @@
 ---
 title: DeepSeek
-description: "Use DeepSeek chat models such as deepseek-chat as a Mem0 LLM with the DEEPSEEK_API_KEY and an optional DEEPSEEK_API_BASE custom endpoint URL."
+description: "Configure DeepSeek as an LLM provider in Mem0 with API key setup and optional custom endpoint configuration."
 ---
 
 To use DeepSeek LLM models, you have to set the `DEEPSEEK_API_KEY` environment variable. You can also optionally set `DEEPSEEK_API_BASE` if you need to use a different API endpoint (defaults to `https://api.deepseek.com`).

docs/components/llms/models/groq.mdx

@@ -1,6 +1,6 @@
 ---
 title: Groq
-description: "Use Groq LPU-hosted models such as llama-3.3-70b-versatile as a Mem0 LLM for very low-latency inference with the GROQ_API_KEY environment variable."
+description: "Configure Groq as an LLM provider in Mem0 for high-speed inference using LPU-powered language models."
 ---
 
 [Groq](https://groq.com/) is the creator of the world's first Language Processing Unit (LPU), providing exceptional speed performance for AI workloads running on their LPU Inference Engine.

docs/components/llms/models/litellm.mdx

@@ -1,6 +1,6 @@
 ---
 title: "LiteLLM"
-description: "Route Mem0 through LiteLLM to reach 100+ providers via one API in Python, or a LiteLLM proxy at LITELLM_API_BASE from the TypeScript SDK."
+description: "Use LiteLLM as an LLM provider in Mem0 to access over 100 language models through a unified interface."
 ---
 [Litellm](https://litellm.vercel.app/docs/) is compatible with over 100 large language models (LLMs), all using a standardized input/output format. You can explore the [available models](https://litellm.vercel.app/docs/providers) to use with Litellm. Ensure you set the `API_KEY` for the model you choose to use.
 

docs/components/llms/models/minimax.mdx

@@ -1,6 +1,6 @@
 ---
 title: MiniMax
-description: "Use MiniMax chat models like MiniMax-M2.7 as a Mem0 LLM with the MINIMAX_API_KEY and an optional MINIMAX_API_BASE custom endpoint override."
+description: "Configure MiniMax as an LLM provider in Mem0 with API key setup and optional custom endpoint configuration."
 ---
 
 To use MiniMax LLM models, you have to set the `MINIMAX_API_KEY` environment variable. You can also optionally set `MINIMAX_API_BASE` if you need to use a different API endpoint (defaults to `https://api.minimax.io/v1`).

docs/components/llms/models/mistral-ai.mdx

@@ -1,6 +1,6 @@
 ---
 title: Mistral AI
-description: "Use Mistral AI models such as open-mixtral-8x7b as a Mem0 LLM through the litellm provider with the MISTRAL_API_KEY environment variable."
+description: "Configure Mistral AI as an LLM provider in Mem0 using the litellm integration and Mixtral model family."
 ---
 
 To use mistral's models, please obtain the Mistral AI api key from their [console](https://console.mistral.ai/). Set the `MISTRAL_API_KEY` environment variable to use the model as given below in the example.

docs/components/llms/models/sarvam.mdx

@@ -1,6 +1,6 @@
 ---
 title: Sarvam AI
-description: "Use Sarvam AI models like sarvam-m as a Mem0 LLM for Indian language conversations, with reasoning_effort, frequency_penalty, and seed controls."
+description: "Configure Sarvam AI as an LLM provider in Mem0, specializing in Indian language support with the Sarvam-M model."
 ---
 
 **Sarvam AI** is an Indian AI company developing language models with a focus on Indian languages and cultural context. Their latest model **Sarvam-M** is designed to understand and generate content in multiple Indian languages while maintaining high performance in English.

docs/components/llms/models/vllm.mdx

@@ -1,6 +1,6 @@
 ---
 title: vLLM
-description: "Serve local models like Qwen2.5-32B-Instruct through a vLLM server and connect Mem0 to it via VLLM_BASE_URL for fast, GPU-optimized inference."
+description: "Configure vLLM as an LLM provider in Mem0 for high-performance local inference with GPU-optimized serving."
 ---
 
 [vLLM](https://docs.vllm.ai/) is a high-performance inference engine for large language models that provides significant performance improvements for local inference. It's designed to maximize throughput and memory efficiency for serving LLMs.

docs/components/rerankers/config.mdx

@@ -1,6 +1,6 @@
 ---
 title: Config
-description: "Reference for Mem0 reranker configuration covering Cohere, Zero Entropy, sentence-transformer, HuggingFace, and LLM-based providers with top_k limits."
+description: "Reference for shared and provider-specific reranker configuration options in Mem0, including top_k and API key settings."
 ---
 
 ## Common Configuration Parameters

docs/components/rerankers/custom-prompts.mdx

@@ -1,6 +1,6 @@
 ---
 title: Custom Prompts
-description: "Write custom LLM reranker scoring prompts in Mem0 using query and document variables to tune relevance ranking for your specific domain or use case."
+description: "Customize the LLM reranker prompt template in Mem0 to control how search results are ranked and scored."
 ---
 
 When using LLM rerankers, you can customize the prompts used for ranking to better suit your specific use case and domain.

docs/components/rerankers/models/cohere.mdx

@@ -1,6 +1,6 @@
 ---
 title: Cohere
-description: "Use Cohere rerank-v3.5 or older v3.0 models as a Mem0 reranker for English and multilingual search relevance with COHERE_API_KEY authentication."
+description: "Configure Cohere as a reranker in Mem0 with support for English and multilingual reranking models."
 ---
 
 Cohere provides enterprise-grade reranking models with excellent multilingual support and production-ready performance.

docs/components/rerankers/models/huggingface.mdx

@@ -1,6 +1,6 @@
 ---
 title: Hugging Face Reranker
-description: 'Access thousands of Hugging Face Hub reranking models in Mem0, including BAAI BGE cross-encoders, to boost memory search relevance and precision.'
+description: 'Access thousands of reranking models from Hugging Face Hub'
 ---
 
 ## Overview

docs/components/rerankers/models/llm-reranker.mdx

@@ -1,6 +1,6 @@
 ---
 title: LLM Reranker
-description: 'Use any Mem0-supported LLM as a reranker with custom prompts to score and rank memories by query relevance for flexible, tunable retrieval.'
+description: 'Use any language model as a reranker with custom prompts'
 ---
 
 ## Overview

docs/components/rerankers/models/sentence-transformer.mdx

@@ -1,6 +1,6 @@
 ---
 title: Sentence Transformer
-description: 'Run local reranking in Mem0 with Sentence Transformers cross-encoder models like ms-marco-MiniLM for privacy-focused, on-premises deployments.'
+description: 'Local reranking with HuggingFace cross-encoder models'
 ---
 
 Sentence Transformer reranker provides local reranking using HuggingFace cross-encoder models, perfect for privacy-focused deployments where you want to keep data on-premises.

docs/components/rerankers/models/zero-entropy.mdx

@@ -1,6 +1,6 @@
 ---
 title: Zero Entropy
-description: "Configure Zero Entropy neural reranking in Mem0 with the zerank-1 and zerank-1-small models for fast, high-relevance search over stored memories."
+description: "Configure Zero Entropy neural reranking models in Mem0 with zerank-1 and zerank-1-small support."
 ---
 
 [Zero Entropy](https://www.zeroentropy.dev) provides neural reranking models that significantly improve search relevance with fast performance.

docs/components/rerankers/optimization.mdx

@@ -1,6 +1,6 @@
 ---
 title: Performance Optimization
-description: "Best practices for tuning reranker performance in Mem0, covering candidate set sizing, batching, model selection, and latency versus precision tradeoffs."
+description: "Best practices for optimizing reranker performance in Mem0, covering candidate sizing, batching, and tuning."
 ---
 
 Optimizing reranker performance is crucial for maintaining fast search response times while improving result quality. This guide covers best practices for different reranker types.

docs/components/rerankers/overview.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Reranker Providers Overview"
 sidebarTitle: "Overview"
-description: "Compare Mem0 reranker providers (Cohere, Hugging Face, Sentence Transformers, LLM reranker, Zero Entropy) and boost vector search relevance."
+description: 'Pick the right reranker path to boost Mem0 search relevance.'
 ---
 
 Mem0 rerankers rescore vector search hits so your agents surface the most relevant memories. Use this hub to decide when reranking helps, configure a provider, and fine-tune performance.

docs/components/vectordbs/dbs/azure-mysql.mdx

@@ -1,6 +1,6 @@
 ---
 title: Azure MySQL
-description: "Use Azure Database for MySQL as a vector store in Mem0 with JSON-based vector storage for semantic memory search on a managed MySQL backend."
+description: "Use Azure Database for MySQL as a vector store in Mem0 with JSON-based vector storage for semantic search."
 ---
 
 [Azure Database for MySQL](https://azure.microsoft.com/products/mysql) is a fully managed relational database service that provides enterprise-grade reliability and security. It supports JSON-based vector storage for semantic search capabilities in AI applications.

docs/components/vectordbs/dbs/azure.mdx

@@ -1,6 +1,6 @@
 ---
 title: Azure AI Search
-description: "Configure Azure AI Search as a managed vector store in Mem0 using your service name, API key, and index for secure, scalable memory retrieval."
+description: "Use Azure AI Search as a vector store in Mem0 for managed vector search with service name and API key setup."
 ---
 
 [Azure AI Search](https://learn.microsoft.com/azure/search/search-what-is-azure-search/) (formerly known as "Azure Cognitive Search") provides secure information retrieval at scale over user-owned content in traditional and generative AI search applications.

docs/components/vectordbs/dbs/baidu.mdx

@@ -1,6 +1,6 @@
 ---
 title: Baidu VectorDB (Mochow)
-description: "Use Baidu VectorDB (Mochow) as an enterprise-grade vector store in Mem0 for high-performance, distributed vector storage and semantic retrieval."
+description: "Use Baidu Mochow as an enterprise vector database in Mem0 for high-performance vector storage and retrieval."
 ---
 
 [Baidu VectorDB](https://cloud.baidu.com/doc/VDB/index.html) is an enterprise-level distributed vector database service developed by Baidu Intelligent Cloud. It is powered by Baidu's proprietary "Mochow" vector database kernel, providing high performance, availability, and security for vector search.

docs/components/vectordbs/dbs/cassandra.mdx

@@ -1,6 +1,6 @@
 ---
 title: Apache Cassandra
-description: "Use Apache Cassandra as a distributed NoSQL vector store in Mem0 for scalable, fault-tolerant semantic memory search over large-scale datasets."
+description: "Use Apache Cassandra as a distributed vector store in Mem0 with semantic search over large-scale datasets."
 ---
 
 [Apache Cassandra](https://cassandra.apache.org/) is a highly scalable, distributed NoSQL database designed for handling large amounts of data across many commodity servers with no single point of failure. It supports vector storage for semantic search capabilities in AI applications and can scale to massive datasets with linear performance improvements.

docs/components/vectordbs/dbs/chroma.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Chroma"
-description: "Use Chroma as an AI-native vector database in Mem0 for local or cloud-hosted embedding storage, quick prototyping, and simple LLM app development."
+description: "Use Chroma as a vector database in Mem0 for local or cloud-hosted vector storage with built-in embedding support."
 ---
 [Chroma](https://www.trychroma.com/) is an AI-native open-source vector database that simplifies building LLM apps by providing tools for storing, embedding, and searching embeddings with a focus on simplicity and speed. It supports both local deployment and cloud hosting through ChromaDB Cloud.
 

docs/components/vectordbs/dbs/databricks.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Databricks"
-description: "Use Databricks Vector Search as a serverless vector store in Mem0 with auto-updating indexes synced from Delta tables and Unity Catalog governance."
+description: "Use Databricks Vector Search as a serverless vector store in Mem0 with auto-updating indexes from Delta tables."
 ---
 [Databricks Vector Search](https://docs.databricks.com/en/generative-ai/vector-search.html) is a serverless similarity search engine that allows you to store a vector representation of your data, including metadata, in a vector database. With Vector Search, you can create auto-updating vector search indexes from Delta tables managed by Unity Catalog and query them with a simple API to return the most similar vectors.
 

docs/components/vectordbs/dbs/elasticsearch.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Elasticsearch"
-description: "Use Elasticsearch as a distributed vector database in Mem0 with dense vectors and k-NN queries for hybrid semantic and keyword memory search."
+description: "Use Elasticsearch as a vector database in Mem0 for distributed vector search using dense vectors and k-NN queries."
 ---
 [Elasticsearch](https://www.elastic.co/) is a distributed, RESTful search and analytics engine that can efficiently store and search vector data using dense vectors and k-NN search.
 

docs/components/vectordbs/dbs/faiss.mdx

@@ -1,6 +1,6 @@
 ---
 title: "FAISS"
-description: "Use Meta FAISS as a high-performance local vector store in Mem0, optimized for memory usage and fast in-process similarity search over dense vectors."
+description: "Use Facebook FAISS as a high-performance vector store in Mem0, optimized for memory usage and fast similarity search."
 ---
 [FAISS](https://github.com/facebookresearch/faiss) is a library for efficient similarity search and clustering of dense vectors. It is designed to work with large-scale datasets and provides a high-performance search engine for vector data. FAISS is optimized for memory usage and search speed, making it an excellent choice for production environments.
 

docs/components/vectordbs/dbs/milvus.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Milvus"
-description: "Use Milvus as an open-source vector database in Mem0, scaling from Jupyter notebook demos to production similarity search across billions of vectors."
+description: "Use Milvus as an open-source vector database in Mem0, scalable from local development to production workloads."
 ---
 [Milvus](https://milvus.io/) is an open-source vector database that suits AI applications of every size, from running a demo chatbot in a Jupyter notebook to building web-scale search that serves billions of users.
 

docs/components/vectordbs/dbs/mongodb.mdx

@@ -1,6 +1,6 @@
 ---
 title: "MongoDB"
-description: "Use MongoDB Atlas as a vector database in Mem0 with native vector search for high-dimensional similarity queries alongside your document data."
+description: "Use MongoDB as a vector database in Mem0 with built-in vector search for high-dimensional similarity queries."
 ---
 
 # MongoDB

docs/components/vectordbs/dbs/neon.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Neon"
-description: "Use Neon serverless Postgres with the pgvector extension as a vector store in Mem0 for autoscaling, branchable memory storage with a Postgres URL."
+description: "Use Neon as a vector store in Mem0, powered by PostgreSQL and pgvector."
 ---
 
 Use [Neon](https://neon.com/) as a vector store in Mem0, powered by PostgreSQL and the

docs/components/vectordbs/dbs/neptune-analytics.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Neptune Analytics"
-description: "Use AWS Neptune Analytics as a memory-optimized vector store in Mem0, combining graph analytics with vector search for connected data insights."
+description: "Use AWS Neptune Analytics as a vector store in Mem0, combining graph analytics with vector search capabilities."
 ---
 
 [Neptune Analytics](https://docs.aws.amazon.com/neptune-analytics/latest/userguide/what-is-neptune-analytics.html) is a memory-optimized graph database engine for analytics. With Neptune Analytics, you can get insights and find trends by processing large amounts of graph data in seconds, including vector search.

docs/components/vectordbs/dbs/opensearch.mdx

@@ -1,6 +1,6 @@
 ---
 title: "OpenSearch"
-description: "Use OpenSearch as a vector database in Mem0 with k-NN search over dense embeddings, including AWS OpenSearch Service serverless collections."
+description: "Use OpenSearch as a vector database in Mem0 with k-NN search support via AWS OpenSearch Service serverless collections."
 ---
 [OpenSearch](https://opensearch.org/) is an enterprise-grade search and observability suite that brings order to unstructured data at scale. OpenSearch supports k-NN (k-Nearest Neighbors) and allows you to store and retrieve high-dimensional vector embeddings efficiently.
 

docs/components/vectordbs/dbs/oracledb.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Oracle AI Vector Search"
-description: "Use Oracle Database AI Vector Search as a vector store in Mem0 with the native VECTOR type to combine semantic memory search and relational queries."
+description: "Use Oracle Database AI Vector Search as a vector store in Mem0 for semantic and relational queries."
 ---
 
 {/* Copyright (c) 2026, Oracle and/or its affiliates. */}

docs/components/vectordbs/dbs/pgvector.mdx

@@ -1,16 +1,10 @@
 ---
 title: "pgvector"
-description: "Use the pgvector extension as a vector store in Mem0 for PostgreSQL-based similarity search with open-source simplicity and standard SQL tooling."
+description: "Use pgvector as a vector store in Mem0 for PostgreSQL-based vector similarity search with open-source simplicity."
 ---
 
 [pgvector](https://github.com/pgvector/pgvector) is an open-source vector similarity search extension for Postgres. After connecting to Postgres, run `CREATE EXTENSION IF NOT EXISTS vector;` to create the vector extension.
 
-The TypeScript SDK loads the `pg` driver only when you use this store, so install it alongside `mem0ai`:
-
-```bash
-npm install pg
-```
-
 ### Usage
 
 <CodeGroup>

docs/components/vectordbs/dbs/pinecone.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Pinecone"
-description: "Use Pinecone as a fully managed vector database in Mem0 with serverless indexes and namespace-based multi-tenancy for low-latency semantic search."
+description: "Use Pinecone as a fully managed vector database in Mem0 with serverless deployment and namespace-based multi-tenancy."
 ---
 [Pinecone](https://www.pinecone.io/) is a fully managed vector database designed for machine learning applications, offering high performance vector search with low latency at scale. It's particularly well-suited for semantic search, recommendation systems, and other AI-powered applications.
 

docs/components/vectordbs/dbs/qdrant.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Qdrant"
-description: "Use Qdrant as an open-source vector search engine in Mem0 for high-performance, filterable similarity search at scale, self-hosted or on Qdrant Cloud."
+description: "Use Qdrant as an open-source vector search engine in Mem0 for high-performance similarity search at scale."
 ---
 [Qdrant](https://qdrant.tech/) is an open-source vector search engine. It is designed to work with large-scale datasets and provides a high-performance search engine for vector data.
 

docs/components/vectordbs/dbs/redis.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Redis"
-description: "Use Redis as a real-time vector database in Mem0 for fast in-memory similarity search using Redis Stack, the RediSearch module, and the redisvl client."
+description: "Use Redis as a real-time vector database in Mem0 for fast vector search using Redis Stack and redisvl."
 ---
 [Redis](https://redis.io/) is a scalable, real-time database that can store, search, and analyze vector data.
 

docs/components/vectordbs/dbs/s3-vectors.mdx

@@ -1,6 +1,6 @@
 ---
 title: Amazon S3 Vectors
-description: "Use Amazon S3 Vectors as a cost-optimized vector storage service in Mem0 with AWS credential auth, sub-second queries, and S3-level durability."
+description: "Use Amazon S3 Vectors as a cost-optimized vector storage service in Mem0 with AWS credential authentication."
 ---
 
 [Amazon S3 Vectors](https://aws.amazon.com/s3/features/vectors/) is a purpose-built, cost-optimized vector storage and query service for semantic search and AI applications. It provides S3-level elasticity and durability with sub-second query performance.

docs/components/vectordbs/dbs/supabase.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Supabase"
-description: "Use Supabase as a vector store in Mem0, backed by PostgreSQL and the pgvector extension with HNSW indexing for scalable embedding search."
+description: "Use Supabase as a vector store in Mem0, powered by PostgreSQL and pgvector with HNSW indexing support."
 ---
 [Supabase](https://supabase.com/) is an open-source Firebase alternative that provides a PostgreSQL database with pgvector extension for vector similarity search. It offers a powerful and scalable solution for storing and querying vector embeddings.
 

docs/components/vectordbs/dbs/turbopuffer.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Turbopuffer"
-description: "Use Turbopuffer as a serverless vector database in Mem0 for low-latency search at scale with native metadata filtering and cost-effective storage."
+description: "Use Turbopuffer as a serverless vector database in Mem0 for low-latency search at scale with native metadata filtering."
 ---
 [Turbopuffer](https://turbopuffer.com) is a serverless vector database optimized for low-latency search at scale. It offers cost-effective vector storage with native metadata filtering.