Codex Setup

Codex works best with Coppermind through the local MCP path.

Use this path if you want:

• local-first memory with no account required
• explicit memory tools
• optional automatic capture later through hooks

Recommended setup

npm install -g coppermind
coppermind setup
coppermind daemon start
coppermind doctor
coppermind mcp codex install

This writes the managed Codex MCP config for the local Coppermind runtime.

Optional: install hooks

Hooks are a separate layer:

coppermind codex hooks install

Use hooks only if you want automatic capture of selected prompt and command outcomes.

The split is intentional:

• coppermind mcp codex install = retrieval and explicit memory control
• coppermind codex hooks install = automatic capture

How to know it worked

After restarting Codex, you should see Coppermind memory tools such as:

• memory_search
• memory_ingest
• memory_get
• memory_stats
• memory_delete

If it does not work

Start here:

coppermind doctor
coppermind doctor --check

Then read Troubleshooting and Support.

Advanced cloud path

If you explicitly want the advanced direct cloud MCP package instead of the local runtime-backed path, see Published Cloud MCP (Advanced).