Skip to content

Quick start

Three steps, a few minutes: check what you need, run doctor, plan something. How it works explains what happens in between.

Terminal window
npm install -g jev-planner
export TYPESAFE_API_KEY="your-key"
jev-planner doctor

doctor checks the selected agents — each CLI installed and logged in, each API key set — and the Jev key, without making a paid model call.

Run it from the repository you want the agents to inspect:

Terminal window
jev-planner -o PLAN.md "Add per-user rate limiting to the public API"
[jev-planner] Drafting independent plans with Codex and Claude…
[jev-planner] Asking Jev for typed quality and routing decisions…
# only when Jev asks: [jev-planner] Cross-reviewing the 2 drafts…
[jev-planner] Wrote /home/you/my-app/PLAN.md

A run takes minutes and makes several paid calls; read cost and data flow before pointing it at a large task.

Next: usage covers every other option, a config file pins them for a repository, and how it works explains Jev’s part. To run it without installing: npx jev-planner "<task>".