Skip to main content
@airctrl/cli lets you work with from a terminal and inject records into a process without creating a local .env file.

​
Install

You can also run it without a global installation:

​
Human login

The command asks for:
  • API base URL.
  • Personal Access Token.
  • Optional default project ID.
It saves this human configuration in ~/.airctrl/config.json. For non-interactive jobs, use:

​
Service Account execution

An active Service Account requires AC_TOKEN, AC_API_BASE_URL, AC_SA_CREDENTIAL_ID, and AC_SA_CAP_PRIVATE_KEY_B64 from one credential bundle. AC_SA_SERVICE_ACCOUNT_ID carries the bundle identity when available. Do not mix fields from different bundles. An incomplete Service Account environment fails instead of falling back to human mode. Service Account mode exposes a smaller command set for unattended record and Gateway work. Human-only commands fail before an SDK or API call. See CLI commands for the exact list.

​
Inject records

The CLI:
  1. Reads accessible records in that project.
  2. Decrypts them locally.
  3. Converts record names to uppercase environment keys.
  4. Removes control variables from the child environment.
  5. Starts the child process with the record values in memory.
It does not write a .env file. The CLI login belongs only to the CLI. SDK applications and MCP servers must receive their own explicit configuration. See Combine tools for safe mixed workflows.

​
Output and errors

Read commands print JSON or the requested value to stdout. Operational messages and stable errors use stderr. A failed command returns a non-zero exit status. See CLI commands and Errors and retries.