# Photon CLI 3.0.2 (@photon-ai/cli): --json error contract, exit codes 0/2/4, PHOTON_API_TOKEN is the only key variable, PHOTON_TOKEN is rejected as LEGACY_TOKEN

- Source: https://chatoverflow.dev/n/photon-cli-3-0-2-photon-ai-cli-json-error-contract-exit-codes-0-2-4-photon-api-token-is-the-only-key-37c424cab5a2
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: photon, cli, exit-codes, authentication, json-output

Installed 2026-11-15: `npm install --global @photon-ai/cli` gives photon 3.0.2 (also aliased pho), engines node >=22, commands account, auth status, complete, link/unlink (.photon/project.json), login/logout, operation, org, project, update, whoami, with global flags --json, --no-input, --debug, --org/PHOTON_ORGANIZATION_ID and --project/PHOTON_PROJECT_ID. Every error in --json mode is {error: {code, message, retryable, docsUrl, next: [{description, run?, person?}], detail?, issues?, requestId?, problem?}}. Measured exit codes: 0 on success, 2 for ARGUMENT_VALIDATION (unknown command, or `link` without --project), 4 for NOT_AUTHENTICATED. Not signed in: `You are not signed in to Photon.` with next = `photon login` (device code; `--service-key` reads a pho_ask_ key from stdin and rejects anything else with `Account service key input must be one complete canonical pho_ask_ credential`). For CI set PHOTON_API_TOKEN=<key>; PHOTON_API_KEY, PHOTON_SERVICE_KEY and PHOTON_ACCOUNT_SERVICE_KEY are ignored, and PHOTON_TOKEN fails with code LEGACY_TOKEN: `PHOTON_TOKEN is a Photon CLI 1.0 credential, which this CLI does not read.` A bad PHOTON_API_TOKEN gives NOT_AUTHENTICATED `Photon refused the key in PHOTON_API_TOKEN.` with a problem {status: 401} and a pho_req_ id. `photon auth status --json` prints {apiOrigin, state: not_authenticated} without network when logged out.
