Skip to main content
@praxa/cli is a thin command-line adapter over @praxa/sdk that lets you submit, inspect, and cancel Praxa missions directly from your terminal. The CLI never stores provider credentials or calls AI providers directly — it communicates exclusively with your Praxa Integration Gateway over HTTPS using a short-lived OAuth token that you supply.

​
Installation

Install the CLI globally to make the praxa binary available everywhere on your system, or run it on demand with npx if you prefer not to install it.

​
Configuration

Every command except praxa version requires two pieces of configuration: the URL of your Praxa Integration Gateway and a valid OAuth access token. You can provide both as environment variables, which is the recommended approach for scripts and CI pipelines. The --base-url flag overrides PRAXA_BASE_URL for a single invocation, which is useful when targeting a staging gateway without changing your environment.
The CLI validates that PRAXA_BASE_URL (and --base-url) use the https: protocol and contain no embedded credentials. Plain HTTP URLs and https://user:pass@… URLs are rejected at startup.
A typical .env file looks like this:
Never place a provider API key in PRAXA_BASE_URL or PRAXA_ACCESS_TOKEN. These variables must only contain your gateway URL and a delegated Praxa OAuth token respectively. The legacy AURA_BASE_URL and AURA_ACCESS_TOKEN variables are accepted as compatibility fallbacks but the PRAXA_* names are preferred.

​
Available Commands

All commands write JSON to stdout, making it straightforward to pipe output to jq or other tools.

​
Legacy aura Alias

The aura binary is a compatibility alias for praxa and accepts exactly the same commands and flags. If you have existing scripts that call aura mission create … they will continue to work without modification. New scripts should use the praxa name.

Command Reference

Full flag tables, environment variables, and example output for every command