Claude Code, Codex, and Cursor

Claude CodeCodexCursor

Dedicated setup guides are available for OpenCode, Pi & Oh My Pi, and Hermes.

Install

Select one or more harnesses:

mimir install --harness claude-code --harness codex --harness cursor

Activate

The installer enrolls receipt-owned hook manifests in each harness’s supported location. Existing different hook files are preserved as conflicts rather than merged or overwritten.

• Claude Code: Reload with /reload-plugins or restart Claude Code.
• Codex: Requires a restart after install.
• Cursor: Cursor automatically reloads hooks.json when you open or continue an agent session.

Run mimir doctor --json after activation and resolve every failed check.

How capture works

Start, prompt, completion, and end hooks invoke the hidden mimir _hook adapter. It reconstructs bounded prompt and assistant exchanges and queues delivery when the Worker is unavailable.

Verify

Complete one real turn, find it with mimir list --json, then verify durable persistence with mimir session status <id> --json.

Connect other tools

To connect custom harnesses or third-party tools:

mimir connection

The connection manifest supplies proxy base URLs, credential sources, and supported metadata headers. The CLI inspects and controls memory; it does not capture unrelated model traffic.

Session titles

Titles are first-class session metadata, separate from the original task intent. The displayed title falls back through title, intent, then session ID. A manual dashboard title has highest precedence, followed by a title reported by the harness, a saved generated title exchange, and the first saved primary user intent. Lower-precedence sources cannot overwrite a stronger title.