Config Files

Zeno stores all state locally. Nothing is written to a remote server.

~/.zenoai/config.json

Your saved provider choice and API key. Created on first run after you complete provider setup.

To reset this file, run npx zenoai reset. The next run will prompt you to configure a provider again.

~/.zenoai/last-report.json

The cached output from your last Zeno report. Used to avoid re-scanning when the project has not changed significantly.

To clear this file, run npx zenoai clear-report.

.zeno-history.json

Per-project refactor history. Written to the root of each project Zeno has touched. Tracks which files were reviewed, what actions were taken, and when.

Skipped files are remembered with a reason, for example confidence 0.40 — large diff, no existing tests, so Zeno won’t retry them automatically on future runs. To force a retry, remove the entry manually or run npx zenoai reset-history.

Useful for keeping a record of what was changed and what Zeno approved or flagged.

To reset the history for the current project, run npx zenoai reset-history.

Gitignore recommendation

If you do not want to commit the project-level history file, add it to your .gitignore:

.zeno-history.json

The global config files in ~/.zenoai/ are never committed to version control.

.zeno/project.json

Stores the confirmed project type when automatic detection is ambiguous. This keeps future readiness reviews consistent with the product you are building.

Local report artifacts

Ship-readiness runs save complete JSON, HTML, and CSV reports locally. Use:

npx zenoai report list
npx zenoai report open latest

The HTML report is printable. Use its Print / Save as PDF action to create a PDF through your browser.