Introduction

Zeno is a ship-readiness copilot for vibe-coded apps. It scans your project, traces critical user flows, identifies launch blockers, and turns repository evidence into a readiness verdict.

It is not another coding assistant. Zeno is the judgment layer that answers: can this product’s critical path deliver its intended outcome, and what should happen next?

What Zeno does

• Detects the project type and applies a project-specific readiness rubric
• Traces critical paths such as signup, checkout, capture forms, CLI entrypoints, protected routes, and data writes
• Separates hard blockers, soft blockers, and code ownership risks
• Labels every finding as Confirmed, Likely, Needs verification, or Inferred
• Evaluates private preview, public launch, and paid traffic readiness separately
• Runs local security checks for obvious risk signals
• Applies safety gates to cleanup and deterministic large-file splitting
• Saves complete reports locally as JSON, HTML, and CSV

What Zeno does not do

• Write or generate code
• Replace manual code review
• Guarantee correctness
• Prove runtime behavior from static analysis
• Test every flow end to end
• Replace senior engineering judgment

Requirements

• Node.js 18 or later
• A JavaScript, TypeScript, JSX, or TSX project
• An API key from one of the supported providers, only needed for ship-readiness checks and cleanup. Security scanning and file splitting need no key.

First run

No install required. Run Zeno directly with npx:

npx zenoai

On first run, Zeno will ask you to choose a provider and enter your API key. Your config is saved locally at ~/.zenoai/config.json so you are only prompted once.

After setup, Zeno scans the project, builds a source summary, and prompts you to choose an action.

If project-type detection is ambiguous, Zeno asks you to confirm the type and stores the selection in .zeno/project.json.