Installation

SETUP

Maverick is a dependency-free Node.js CLI. It needs Node 20 or newer and works in any repository — the language of your project does not matter.

Run it

npx (no install)

npx @maverick-ai/cli init

npm (global)

npm install -g @maverick-ai/cli
maverick init

pnpm

pnpm add -g @maverick-ai/cli
maverick init

Every example in these docs uses the short maverick binary. With npx, replace maverick with npx @maverick-ai/cli.

npx says "could not determine executable to run"

Your npm registry is not serving the real package. This happens when registry= in ~/.npmrc points to a company mirror (Azure Artifacts, Artifactory, Nexus, Verdaccio) whose npmjs upstream cached an early placeholder version of @maverick-ai/cli with no binary. Check what your registry resolves:

npm view @maverick-ai/cli version

If it is not the latest release, fetch the @maverick-ai scope from the public registry and keep everything else on the mirror:

npm config set @maverick-ai:registry https://registry.npmjs.org/

For a one-off run, npx --registry=https://registry.npmjs.org/ @maverick-ai/cli init also works.

Check the setup

maverick doctor

doctor checks the configuration, the detected stack and that each toolchain binary it would run (for example npm, pytest or go) is on your PATH. Add --fix for a list of suggested fixes.

What gets written

init creates a single .maverick/config.json. Tasks live under .maverick/tasks/<slug>/ as JSON and Markdown you can commit and review. The Lens cache in .maverick/cache/ is local and can be ignored.

.maverick/
├── config.json          # project settings and default workflow
├── tasks/
│   └── add-pagination/  # TASK.json, PRD.md, TECHSPEC.md, subtasks/, REVIEW.md
└── cache/               # Lens index (safe to .gitignore)

No telemetry

Maverick never sends project data anywhere. Lens listens on loopback only.

Next: your first task.