Installation

The prokodo CLI is available through three installation methods. Pick the one that best fits your workflow.

npm / pnpm / yarn

Requirements

Requirement	Version
Node.js	≥ 22
npm / pnpm / yarn	any recent version

tip

Not sure which version you have? Run node --version. If you need Node 22, use nvm: nvm install 22 && nvm use 22.

Install globally

npm install -g @prokodo/cli

# or with pnpm
pnpm add -g @prokodo/cli

# or with yarn
yarn global add @prokodo/cli

Verify the installation:

prokodo --version

You should see the current version number printed to stdout.

Without global install (npx)

You can run the CLI without installing it globally:

npx @prokodo/cli --help

Update

npm update -g @prokodo/cli

Uninstall

npm uninstall -g @prokodo/cli

---

Homebrew

Requirements: macOS 12 Monterey or later · Homebrew

Node.js is installed automatically as a Homebrew dependency — no separate Node setup required.

# 1. Add the prokodo tap (one-time)
brew tap prokodo-agency/tap

# 2. Install the CLI
brew install prokodo-cli

# 3. Verify
prokodo --version
prokodo doctor

Update

brew update && brew upgrade prokodo-cli

Uninstall

brew uninstall prokodo-cli
brew untap prokodo-agency/tap  # optional — removes the tap entirely

---

Docker

No local installation needed. Pull the official image from the GitHub Container Registry.

# Run any command without a global install
docker run --rm ghcr.io/prokodo-agency/prokodo-cli:latest --help

# Verify a local project (mount your working directory)
docker run --rm \
  -e PROKODO_API_KEY=pk_live_... \
  -v "$PWD":/workspace -w /workspace \
  ghcr.io/prokodo-agency/prokodo-cli:latest verify

tip

Pass PROKODO_API_KEY as an environment variable instead of running prokodo auth login inside the container — credentials stored via prokodo auth login are written to the host filesystem and are not available inside the container by default.

---

Verify your environment

After installing via any method, run the built-in health check:

prokodo doctor

Expected output (green checkmarks for all five checks):

✓  Node version               22.x.x (required ≥ 22)
✗  API key configured         Source: none
✗  .prokodo/config.json       No config found in current directory
…

The API key configured and .prokodo/config.json checks will fail until you complete authentication — that's expected.