Local-first memory for AI agents
Nuzo
Inspectable, portable memory for Codex, Claude Code, and MCP-compatible agents. Built for developer workflows where useful context should not become hidden state.
85% estimated MVP progress
Why¶
Agents can write code, inspect repositories, run tools, and help make project decisions. But most sessions still start from zero. Nuzo preserves useful context locally so users can inspect, edit, export, and delete what agents remember.
Principles¶
Local¶
Memories live on the user's machine by default.
Auditable¶
Every memory should expose content, scope, source, metadata, and history.
Portable¶
Import/export formats are documented instead of opaque.
Agent-ready¶
The integration boundary is a stable MCP tool contract.
Current Focus¶
Nuzo is in early MVP development. The repository now includes a TypeScript core package, a local CLI backed by SQLite, an MCP server, host plugin metadata, release artifact checks, and npm package staging validation.
| Area | State |
|---|---|
| Core | Memory lifecycle, policy checks, SQLite storage, FTS search, tests. |
| CLI | User/project init, lifecycle commands, audit history, dry-run bulk forget, portability, and diagnostics. |
| MCP | 11 stdio tools covering recall, lifecycle, audit history, bulk safety, portability, and diagnostics. |
| Host Plugins | Codex and Claude Code wrapper metadata exists; both remain thin MCP packaging layers. |
| Release | CI, Pages, plugin packaging, npm artifact staging, release-state checks. |
| Next | Published core/CLI/MCP packages, fresh host plugin installs, and the first public 0.1.0 release. |
Runtime Storage¶
Runtime memory is user-owned state. It is ignored by Git by default and should not be committed.