mem9

项目详情摘要

Persistent Memory for AI Agents. Your agents forget everything between sessions. mem9 fixes that with persistent memory across sessions and machines, shared memory for multi-agent workflows, and hybrid recall with a visual dashboard. For OpenClaw and ClawHub installs, start here: mem9.ai/openclaw-memory Hermes Agent, Claude Code, OpenCode, Codex, DeepSeek Harness, and Dify guides are below. Quick Start 1. Choose your mem9 endpoint. Hosted API: `https://api.mem9.ai` Self-hosted: apply the matching control-plane schema, then start `mnemo-server`: See Self-Hosting for backend-specific setup details, and API Reference for provisioning. 2. Pick your integration guide. OpenClaw / ClawHub Hermes Agent Claude Code OpenCode Codex DeepSeek Harness Dify Any HTTP client / custom runtime 3. Set your credentials. For self-hosted deployments, use your server URL and the mem9 API key returned or configured by your provisioning flow. Why mem9 mem9 gives coding agents one shared memory layer instead of separate local notebooks and one-off prompt files. What mem9 gives you | Why it matters | Persistent memory across sessions and machines | Your context survives restarts, laptop switches, and long-running projects | Shared memory across agents and workflow platforms | OpenClaw, Hermes Agent, Claude Code, OpenCode, Codex, DeepSeek Harness, Dify apps, and custom clients can recall the same facts | Stateless integrations | Runtime plugins stay thin because storage, search, ingest, and policy live in the server | Hybrid recall and a visual dashboard | Semantic search, keyword search, and inspection workflows stay in one system | Supported Platforms and Agent Runtimes Platform | Integration shape | Install / docs | OpenClaw | `kind: "memory"` plugin for server-backed shared memory | OpenClaw /