transiliencectl is a command-line tool that talks to the Transilience.ai API. It turns the everyday loop — list apps, run one, watch it, pull the outputs — into short commands, so you can drive the platform from a terminal or a script instead of writing curl by hand.
It authenticates with an API key you mint in the app. Because the key is bound to one organization, the CLI always acts in that org — there's nothing extra to pass.
pipx install transiliencectl # recommended (isolated)
# or, for development from a checkout:
pip install -e .transiliencectl config set base-url <your-api-host>
transiliencectl auth login --api-key <YOUR_API_KEY>
transiliencectl auth status # → Authenticated. base_url=...Settings live in ~/.transilience/config.json. Values can also come from the environment
(TRANSILIENCE_BASE_URL, TRANSILIENCE_API_KEY) or per-command flags (--base-url, --api-key);
the order of precedence is flag → environment → config file.
| Command | What it does |
|---|---|
config set <key> <value> |
Store base-url or api-key. config get / config path to inspect. |
auth login --api-key <key> |
Save your key. auth status checks it; auth logout clears it. |
projects list / projects get <id> |
Browse the apps you can run. |
run <project_id> -q "..." [--follow] |
Start a run; --follow waits for it to finish. |
sessions list / sessions get <id> [--follow] |
List past runs; inspect one. |
files list <id> / files get <id> <path> -o out |
List a run's outputs and download one. |
Add --json to any command for machine-readable output (handy for scripts and AI agents).
"How is this different from the raw API?" — It's a friendlier front-end to the same API: no curl, no headers to remember, tables instead of raw JSON (unless you ask for --json).
"Where do I get the key?" — In the app under Settings → API Keys. See API keys.
"Which org does it use?" — The one your key is bound to. To act in another org, create a key there and auth login with it.
- Use the CLI — step-by-step walkthrough.
- API keys — minting and managing keys.
- Use the API — the underlying HTTP endpoints.