Local CLI

Nuzo's local CLI command is nuzo.

The CLI package currently lives at packages/cli and exposes the nuzo binary from packages/cli/dist/index.js.

Current Monorepo Path

Use Node.js 22 LTS or 24 LTS with npm 10 or newer.

Until release packaging is finalized, use the root workspace wrapper:

npm install
npm run build
npm run nuzo -- memory doctor

The wrapper runs:

node packages/cli/dist/index.js

Arguments after -- are passed to the CLI.

Examples:

npm run nuzo -- memory init
npm run nuzo -- memory init --project
npm run nuzo -- memory remember "The project uses SQLite for local storage." --kind project_decision --tag storage
npm run nuzo -- memory recall "local storage"
npm run nuzo -- memory export --path ./memories.memory.export.json
npm run nuzo -- memory history mem_01HZY
npm run nuzo -- memory forget-many --tag obsolete
npm run nuzo -- memory forget-many --scope project:auto --apply

Project init creates .nuzo/config.json, a project-local SQLite store, and missing Git ignore rules. Later CLI commands run from that project root resolve the project store and hashed project scope automatically.

Smoke Test

Run:

npm run smoke:cli

This builds the workspace and runs:

nuzo memory doctor

against a temporary store path under /tmp.

The smoke script sets:

NUZO_DOCTOR_SKIP_GIT=1

This keeps restricted agent environments from turning an otherwise healthy temporary store into a warning only because Git process execution is unavailable. Normal nuzo memory doctor runs still check for tracked memory files by default.

For a fuller clean install and import/export walkthrough, see docs/getting-started/clean-install.md.

Package Direction

The public command should remain:

nuzo

The memory commands should remain grouped under:

nuzo memory

The package name can change before public release, but the user-facing command should stay stable.

Boundaries

The CLI must call packages/core use cases.

Do not add memory business logic, storage rules, import/export rules, or policy checks directly in the CLI.

Git Safety

Runtime memory and exports must stay out of Git:

~/.nuzo/memory/
.nuzo/memory/
*.memory.export.json
*.memory.export.md
*.sqlite
*.sqlite-*

If a host blocks child process execution and the Git tracking check is not meaningful, run doctor with:

NUZO_DOCTOR_SKIP_GIT=1 nuzo memory doctor

Use this only for restricted environments or smoke tests. In a normal checkout, leave Git tracking enabled so doctor can warn about committed memory files.