engini CLI is machine-first: human-readable output on a TTY, JSON when piped or with --json, stable exit codes, and agent-resumable flows. Two distributions, identical behavior:
Commands at a glance
Quickstart
Universal flags
Every command accepts:Authentication & configuration
Two ways to authenticate:engini login --api-key eng_…- stores the credential in a0600TOML config file (~/.config/engini/config.toml;%APPDATA%\engini\config.tomlon Windows), alongsideapi_url(defaulthttps://api.engini.io).- Environment variables -
ENGINI_API_KEY(preferred) orENGINI_API_TOKEN; no login needed. Useful for CI and agents.
engini whoami (exit code 3 means the credential is missing/invalid). Point at another environment with engini login --api-url <url>. What the two credential types mean: Authentication.
Errors & big results
- Failures print a structured JSON error (with a
hintwhere applicable) and exit with a stable code -2usage,3auth,4not found,5needs-input,124timeout. Full table: machine contract. - API rate limiting surfaces as an error - honor
Retry-Afterper the rate-limit rules. - List commands return complete results (pagination is handled for you). Large tool outputs become a result handle - drill in with
engini tools result <handle>instead of re-fetching.