{
  "markdown": "<h1 align=\"center\">Nuzo</h1>\n\n<p align=\"center\">\n  <strong>Local-first, auditable memory for AI agents.</strong><br>\n  Durable context for Codex, Claude Code, and MCP-compatible hosts—without turning memory into hidden state.\n</p>\n\n<p align=\"center\">\n  <a href=\"https://github.com/fabionfsc/nuzo-memory/actions/workflows/ci.yml\"><img alt=\"CI\" src=\"https://github.com/fabionfsc/nuzo-memory/actions/workflows/ci.yml/badge.svg\"></a>\n  <a href=\"https://github.com/fabionfsc/nuzo-memory/actions/workflows/pages.yml\"><img alt=\"Docs\" src=\"https://github.com/fabionfsc/nuzo-memory/actions/workflows/pages.yml/badge.svg\"></a>\n  <a href=\"https://github.com/fabionfsc/nuzo-memory/releases/tag/v1.2.0\"><img alt=\"Release 1.2.0\" src=\"https://img.shields.io/badge/release-v1.2.0-22c55e\"></a>\n  <a href=\"#license\"><img alt=\"Apache 2.0 license\" src=\"https://img.shields.io/badge/license-Apache--2.0-64748b\"></a>\n</p>\n\n<p align=\"center\">\n  <a href=\"https://nuzo.com.br/getting-started/\">Install</a> ·\n  <a href=\"https://nuzo.com.br/getting-started/sixty-second-demo/\">60-second demo</a> ·\n  <a href=\"https://nuzo.com.br/product/why-nuzo/\">Why Nuzo?</a> ·\n  <a href=\"https://nuzo.com.br/operations/privacy-and-security/\">Security</a> ·\n  <a href=\"https://nuzo.com.br/spec/tools/\">MCP contract</a>\n</p>\n\nNuzo keeps scoped memories in local SQLite. Agents can recall bounded context\nacross sessions, while you retain a CLI and public MCP contract to inspect,\nupdate, export, archive, or delete every record. Inferred memories remain\ndrafts until you confirm them; recalled content remains untrusted data.\n\n> [!IMPORTANT]\n> Nuzo `1.2.0` is the final planned release. The repository becomes read-only\n> after publication, and no ongoing maintenance or security response is\n> promised. Published packages remain available for reproducible use and\n> forking. See the [end-of-maintenance notice](docs/operations/end-of-maintenance.md).\n\n## Quick Start\n\nUse Node.js 22 LTS or 24 LTS with npm 10 or newer:\n\n```bash\nnpm install --global @nuzo/memory@1.2.0\nnuzo setup\n```\n\n`nuzo setup` detects Codex and Claude Code, previews host changes, and asks\nbefore writing configuration. To evaluate Nuzo without configuring a host or\ntouching your normal store, run the\n[disposable 60-second demo](docs/getting-started/sixty-second-demo.md).\n\nTwo read-only recall hooks are expected: `SessionStart` and\n`UserPromptSubmit`. They do not write memory.\n\n<details>\n<summary>Non-interactive setup and upgrade commands</summary>\n\n```bash\nnuzo setup --codex --yes\nnuzo setup --claude-code --yes\nnuzo setup --all --yes\nnuzo update --yes\nnuzo memory manage\n```\n\n</details>\n\n## The Memory Loop\n\nAutomatic host hooks only recall. Explicit requests can write directly;\ninferred capture uses a visible suggest-and-confirm flow. The same core policy\napplies through the CLI, MCP server, and supported host integrations.\n\n```bash\nnuzo memory remember \"The demo project uses SQLite.\" \\\n  --kind project_decision --tag demo\nnuzo memory recall \"demo storage\"\n```\n\n## Proof, Not Promises\n\n| Claim | Repository contract |\n| --- | --- |\n| Local by default | SQLite and SQLite FTS are canonical; telemetry and network embeddings are off by default. |\n| Auditable lifecycle | MCP tools cover history and audit alongside update, archive, delete, export, and import. |\n| Explicit inferred writes | Capture suggestions report `memory_writes: false`; confirmation is a separate tool. |\n| Read-only automatic recall | Host hooks open existing stores read-only and fail open without writing application state. |\n| Tested releases | Node 22, Node 24, docs, CodeQL, package validation, and host smoke gates are required before merge. |\n\nInspect the [memory model](docs/spec/memory-model.md),\n[MCP tool contract](docs/spec/tools.md),\n[trust boundary](docs/architecture/memory-trust-boundary.md), and\n[release checklist](docs/operations/release-checklist.md).\n\n## When Nuzo Fits\n\nChoose Nuzo when individual memories need scopes, provenance, review state,\nrelations, audit history, bounded recall, or reuse across supported hosts.\n\nKeep shared repository instructions in `AGENTS.md`. Use a short `MEMORY.md`\nwhen manual curation is enough. Nuzo is not a cloud sync service, team\nknowledge base, autonomous profile builder, or hosted dashboard.\n\nRead the full [decision guide](docs/product/why-nuzo.md) and\n[architecture overview](docs/architecture/overview.md).\n\n## Packages\n\n| Package | Intended use |\n| --- | --- |\n| `@nuzo/memory` | Recommended install: CLI, MCP server, and host hook runtime. |\n| `@nuzo/memory-core` | Library-level integrations. |\n\nSource workspace packages remain private. Public packages are generated and\nvalidated through the documented release process.\n\n## Project Status\n\nThe `1.2.0` release closes the planned roadmap. The repository is retained as\nan auditable reference and is not accepting new feature work. Existing users\nshould pin an exact version and evaluate a maintained alternative or fork for\nfuture runtime and dependency changes. Never publish real memory data,\ncredentials, or exports when discussing or forking Nuzo.\n\n## License\n\nNuzo is licensed under the [Apache License 2.0](LICENSE).\n",
  "bytes": 5160,
  "sha": "15a17c370d58fc0d373c0ab29058d6fcc703cec5b5c6b6ab9bbd0dee7c26b36f",
  "repo_slug": "fabionfsc/nuzo-memory",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_fabionfsc_nuzo_memory_b9a2647c/readme"
}