Skip to main content
Version: 0.4.0

Memzoi

Memzoi, pronounced "mem-zoy", is safe project memory for coding agents. It gives agents a repo-local place to recall durable knowledge, propose new memories, check planned work against warnings, export reviewable instruction files, and connect through MCP.

Memzoi v0 is local-first and intended for dogfooding and early experimentation. It is usable from release binaries or from source today; package-manager installs are still roadmap items.

Start here​

  • Quickstart: run the first workflow in a demo repo.
  • Install: install the memzoi and memzoi-mcp binaries from this repo.
  • Memory lifecycle: propose, review, apply, supersede, or tombstone records.
  • OKF profile: file-native record and proposal layouts, schema fields, and apply target flow.
  • Recall and precheck: search memory, build context and handoff packs, and check risky work.
  • MCP and agent integration: connect agents and install instruction prompts.
  • Reference: CLI commands, MCP tools, schema values, and limitations.

What works now​

  • File-native canonical memory records under .memzoi/records/.
  • OKF-compatible proposal file schema under .memzoi/proposals/pending/.
  • Local runtime state under ~/.memzoi/projects/<project-key>/ for derived SQLite indexes, generated exports, and DB-local open proposal state.
  • Safe memory lifecycle: propose, approve, reject, apply, supersede, and tombstone.
  • Rebuild from canonical records with memzoi rebuild when the derived runtime index needs to be regenerated.
  • Text search, prompt-ready context packs, and CLI handoff packs.
  • Pre-action governance checks with citations and suggested next steps.
  • Deterministic generated exports: OKF Markdown projections, AGENTS.memory.md, and CLAUDE.memory.md.
  • Minimal stdio MCP server with safe tools:
    • search_memory
    • inspect_memory_expiry
    • build_context_pack
    • plan_capture_v1
    • propose_memory
    • precheck_path
    • precheck_action
    • precheck_command

Design shape​

Memzoi separates canonical memory files from derived runtime state.

  1. Typed, scoped, versioned durable memory records live under .memzoi/records/.
  2. Verbose review packets can live under .memzoi/proposals/pending/ before becoming compact records.
  3. A local runtime directory under ~/.memzoi/projects/<project-key>/ holds derived SQLite indexes, generated exports, and DB-local pending proposal state.
  4. Agent-facing APIs support recall, context building, proposed writes, exports, and pre-action checks.

The project keeps reviewability central: agent writes should be proposed first, human-readable exports should be diffable, and repo-shared memory must not contain secrets or private personal data.