Feedback And Support

Nuzo uses GitHub Issues as its public feedback and support path. GitHub Discussions is not required, and Nuzo does not collect product telemetry by default.

Choose the narrowest form:

• Installation Feedback for clean-install success or friction;
• Bug for reproducible incorrect behavior;
• Feature for a scoped product outcome;
• Documentation for unclear or stale guidance;
• Architecture Proposal for substantial, cross-boundary, or hard-to-reverse changes;
• Security policy for vulnerability reporting instructions.

Safe Diagnostic Information

Useful reports include:

• operating system and architecture;
• node --version, npm --version, and nuzo --version;
• the host name and whether setup, hooks, or MCP discovery failed;
• the exact command and sanitized error text;
• whether a disposable fake-data store reproduces the issue.

Do not attach a SQLite store, real memory export, credentials, tokens, private host configuration, home-directory paths, or personal conversation content. Run diagnostics locally and include only the minimum sanitized fields needed to reproduce the problem. Do not paste a normal doctor report wholesale, because local paths can be useful to the operator while remaining unsuitable for a public issue.