Harness-mem
Local project memory for AI coding sessions — a continuity runtime, not a generic memory API.
Harness-mem keeps a single local SQLite memory per project so the next Claude Code or Codex session opens on the thread you were already working on, instead of a blank slate. ~5ms cold start. Zero cloud, zero API keys.
English | 日本語
Table of Contents
What changes
30-second version
Harness-mem gives Claude Code and Codex the same local project memory, so the next session can open on the thread you were already working on instead of a blank slate. Cursor can also be wired as a supported local client for MCP search and hook-based conversation capture. It is built for people who switch tools inside the same project and do not want to re-explain the same decisions twice.
Why people install it
- Resume the actual thread: the next Claude Code or Codex turn can start from the current project chain, not a generic memory dump.
- Keep memory local: project data stays in local SQLite unless you explicitly configure an external integration.
- Share one runtime: Claude Code and Codex CLI use the same daemon, database, and setup / doctor flow.
- Stay honest about scope: Cursor is supported for user-scoped MCP plus hook ingest/search, but Tier 1 continuity is optimized for Claude Code + Codex.
3-minute setup path
- Run
npx -y --package @chachamaru127/harness-mem harness-mem setup --platform codex,claude.
- Run
npx -y --package @chachamaru127/harness-mem harness-mem doctor --platform codex,claude.
- Confirm both clients are green and point at the current checkout or install path.
- Start a fresh Claude Code or Codex CLI session and check that the first turn already knows the current thread.
If Cursor is part of your workflow, use --platform codex,claude,cursor or run a separate harness-mem setup --platform cursor followed by harness-mem doctor --platform cursor. Cursor may need an MCP reload or a new Cursor session before the harness-mem server appears.
Trust block
- Local-first: the database lives on your machine at
~/.harness-mem/harness-mem.db.
- Privacy: there is no cloud memory service, no API keys, and no off-machine upload just to remember context.
- Private tags: wrap any text in
<private>...</private> and it is automatically stripped before storage — use this to keep secrets out of memory without disabling memory entirely.
- Project isolation: each project keeps its own memory lane, so one repo does not bleed into another.
Support tiers
