CLI
Authentication
Authenticate the CLI via browser OAuth or long-lived CI/CD tokens in headless environments.
Overview
The CLI supports both interactive browser-based OAuth authentication for local developers and token-based authentication for automated CI/CD runners.
Interactive Browser Login
asiyst loginThis boots a temporary localhost callback listener, opens your default browser to authorize the session, and receives a secure, short-lived JWT token.
Headless CI/CD Token Authentication
For Docker containers or remote SSH servers where no browser is available, export your administrative API token:
export ASIYST_API_TOKEN="sk_live_9f8a2b3c4d5e6f7a8b9c"
asiyst status
Credential Storage Security
On macOS and Linux, the CLI stores tokens in the OS Keychain / Secret Service API. On Windows, credentials are encrypted using the Windows Data Protection API (DPAPI).