Openclaw Mem0

Adds intelligent long-term memory to agents for auto-capturing, recalling, and managing user facts and preferences across sessions.

This plugin implements Mem0 memory features and will send stored conversation data to whatever Mem0 host you configure. Before installing: 1) Confirm you intend to provide a Mem0 API key (platform mode) or run a trusted self-hosted Mem0 instance (open-source mode). The registry metadata not listing required env vars is inconsistent—treat the plugin as requiring a Mem0 key. 2) If you care about privacy, prefer self-hosted OSS mode or verify the mem0.ai service and the plugin package on npm/GitHub. 3) Disable Auto‑Capture or set strict customInstructions to avoid storing secrets (passwords, SSNs, API keys); test behavior in a sandboxed agent first. 4) Review the package.json/package-lock or the upstream repository to ensure dependencies are legitimate. 5) Because the plugin injects memories into the system prompt, only enable it for agents you trust. If you want higher assurance, ask the author for a canonical repository/linked release and an explanation for why required env vars are omitted from the registry metadata.

Type: OpenClaw Skill Name: openclaw-mem0 Version: 1.0.2 The plugin is designed to integrate Mem0 for long-term memory, which is a legitimate function. However, it is classified as 'suspicious' due to several risky capabilities. The plugin allows configuration of an arbitrary `host` for the Mem0 API and retrieves the `apiKey` (potentially from `process.env`), meaning a compromised configuration could redirect sensitive data (API key, user memories) to an attacker-controlled server. Furthermore, the `lib/mem0.ts` client exposes powerful Mem0 API features like `createWebhook` and `createMemoryExport` via agent tools. While these are legitimate API features, they could be abused through prompt injection against the AI agent to exfiltrate data or establish unauthorized communication channels. The `oss.historyDbPath` in `index.ts` also uses `api.resolvePath`, which could be a local file system vulnerability if the OpenClaw platform's path resolution is not adequately sandboxed.