CLI setup

Install an approved build, connect one environment, and verify read access.

Prerequisites and installation

Maintainer-approved test access and package tarball; @postede/cli is unpublished.
Node.js 24+ and an operator-registered environment. Stop if any prerequisite is missing.

Approved preview installation

npm install --global /path/to/approved-postede-cli.tgz
postede --version

Connect and verify

Choose local, dev, or production explicitly. The CLI discovers the registered client at /.well-known/postede-cli; do not invent a client ID or switch environments if discovery fails.

Read-only verification

postede auth login --env local
postede auth status --env local --json
postede projects list --env local --json

The user completes browser sign-in and chooses permissions. Credentials stay in the OS keychain. Success requires status and project listing in the selected environment; an empty project list is valid. Setup performs no content or delivery writes.

Connection recovery

Expired access: the CLI refreshes automatically. If refresh fails or consent is revoked, run auth login in the same environment with user approval.
Permission denied: check granted scope and project access; request only the missing access.
Rate limit: wait for retryAfterSeconds; do not loop or repeatedly reconnect.

Exit codes and exact retry rules ↗

Disconnect

Terminal

postede auth logout --env local

Revokes the refresh credential and removes local storage. --local-only removes storage without server revocation. A result with revoked: false does not prove revocation; report failures.

For immediate full-grant revocation, use Connected apps in the same environment. Never request passwords, cookies or tokens in conversation.