Skip to main content

Global Options

Every prokodo CLI command accepts these options in addition to its own flags. Pass them before or after the command name.

prokodo [global options] <command> [command options]
prokodo <command> [global options] # ← also works

Options reference

FlagTypeDescription
--api-url <url>stringMarketplace API base URL
--api-key <key>stringOverride the resolved API key
--jsonbooleanMachine-readable JSON on stdout; human logs to stderr
--no-colorbooleanDisable ANSI colour in all output
--verbosebooleanDebug-level detail on stderr
-v / --versionPrint the CLI version and exit
-h / --helpShow contextual help

API key resolution order

When multiple sources provide an API key, the highest-priority source wins:

1. --api-key flag            (highest)
2. PROKODO_API_KEY env var
3. ~/.config/prokodo/credentials.json (lowest)

Environment variables

VariableEquivalent flagDescription
PROKODO_API_KEY--api-keyAPI key
PROKODO_API_BASE_URL--api-urlCustom API base URL
NO_COLOR--no-colorDisable colour (POSIX standard)

NO_COLOR follows the no-color.org convention — any non-empty value suppresses colour.

--json mode

All commands emit a structured JSON object to stdout. Human-readable progress and debug lines go to stderr so they don't corrupt the JSON stream:

prokodo verify --json          # JSON on stdout, logs on stderr
prokodo verify --json 2>/dev/null | jq .passed
prokodo doctor --json | jq '[.checks[] | select(.passed == false)]'

--verbose

Enables debug-level output (to stderr):

  • HTTP request / response details
  • Resolved config values
  • File glob matches and counts
  • Internal state transitions

Useful when filing a bug report or diagnosing unexpected behaviour:

prokodo verify --verbose 2>&1 | tee debug.log

--no-color / NO_COLOR

Recommended in CI environments that don't interpret ANSI codes:

env:
NO_COLOR: '1'

Or inline:

prokodo verify --no-color