Coppermind
Public docs
AppQuick start
Local-first docs

Local-first memory for AI coding agents

Coppermind gives Codex, Claude Code, Cursor, Hermes, and other MCP clients a durable memory layer without making signup, API keys, or database setup your first problem.

Install `coppermind`, run `coppermind setup`, connect your client, and use cloud features later only if you want them.

Quick startChoose your clientFAQ
CodexClaude CodeCursorHermesOther MCP clients
Install
npm install -g coppermind
Connect
Managed install for Codex, Claude Code, Antigravity, or generic MCP
Verify
coppermind doctor is the repair and health surface
Upgrade later
Local is free. Cloud sync and BYODB stay optional.
New here? Read Quick Start first, then jump straight to your client guide. You do not need an account or a manual SurrealDB setup for day-one success.
Start here
1. Install

Install Coppermind locally, run setup once, and let Coppermind own the local runtime.

2. Connect

Choose a client guide for Codex, Claude Code, Cursor, Hermes, or another MCP client.

3. Verify

Use doctor to confirm the runtime is healthy and to repair the common broken states.

What happens after install

Real command flow, not a marketing promise

A first-time user should be able to install Coppermind, connect a client, and confirm the runtime is healthy in a few commands.

npm install -g coppermind
coppermind setup
coppermind daemon start
coppermind doctor
coppermind mcp codex install
Expected result: the runtime is healthy, the client is registered, and you can start using memory without an account or API key.
Local first, cloud optional

No dashboard visit required for first local success

No API key required for the default local runtime

No manual SurrealDB install or database setup required

Hosted sync and BYODB only matter when you choose the cloud layer

Read the FAQ
Choose your path

Client guides for the most common setups

Codex

Install the managed local MCP path, then optionally add hooks for automatic capture.

Claude Code

Use the managed installer for the local MCP path and keep cloud setup out of your first run.

Cursor + MCP clients

Use the generic local MCP config and verify the expected memory tools appear in your client.

Hermes

Patch Hermes into the local runtime path when you want memory woven into the session lifecycle.

Go deeper

Concepts, reference, and help

Concepts
How Coppermind Works
Coppermind keeps the same memory operations across local, hosted sync, and BYODB modes while hiding backend details behind the product surface. Locally, the runtime now separates immutable episodes from promoted truth and uses canonical clusters for current and historical memory.
Memory Lifecycle
The core memory operations stay stable across local, hosted sync, and BYODB modes. Locally, Coppermind now separates immutable episodes from promoted truth records and groups truth into canonical clusters.
Local, Hosted Sync, and BYODB
Understand the three operating modes, when SurrealDB matters, and why the hidden local engine is not the same thing as BYODB.
Reference
Hermes Plugin
Two Hermes paths: runtime-managed and local-first through `coppermind patch hermes`, or the advanced standalone cloud-connected package.
Published Cloud MCP (Advanced)
The advanced direct-cloud MCP path using `@coppermind/mcp`. Most users should use the local `coppermind mcp serve` path instead.
API Reference
Managed cloud memory routes for the SDK, the advanced cloud MCP package, and dashboard operations.
Help & Billing
Troubleshooting and Support
Start with doctor, then classify whether the problem is runtime, client registration, cloud auth, or storage.
Billing and Plans
Local-first usage stays free. Paid plans unlock hosted sync, dashboard controls, and advanced BYODB features.