Configuration & Context

The CLI keeps a small amount of persistent state so you don't have to repeat yourself: your active context (space + workflow), your vault, and output preferences. This page explains that state and the commands that read and write it.

trickest status

The fastest way to see "where am I and who am I":

trickest status

{
  "authenticated": true,
  "auth_source": "TRICKEST_TOKEN",
  "space": "Solutions",
  "workflow": "eval-airixss",
  "base_url": "https://trickest.io"
}

This is the first command to run in any session — it shows your auth source, active space and workflow, and which backend you're talking to.

trickest config

Read and write persisted CLI configuration.

trickest config list

{"auth.vault_id":"e54ccb18-…","preferences.format":"json","context.space":"Solutions","context.workflow":"eval-airixss"}

Config keys

trickest config get auth.vault_id
# {"key":"auth.vault_id","value":"e54ccb18-…"}
 
trickest config set preferences.format json
trickest config unset context.workflow

The active context

Workflow-scoped commands read context.workflow (and sometimes context.space). You set the context with two commands:

trickest switch <path>

Set both the active space and workflow in one step. Accepts a path or a bare name/ID:

trickest switch /spaces/Solutions/workflows/"DAST v2"
trickest switch <workflow-id>

trickest workflow use <name-or-id>

Set just the active workflow:

trickest workflow use 7b4a4059-…
# Active workflow set to: DAST v2

trickest save

Save the current (context) workflow — handy in fast editor/build loops.

trickest save

Why stale context bites

If context.workflow points at a workflow that no longer exists (or you switched spaces), workflow-scoped commands fail clearly:

trickest node ls

{"code":"ERR_NOT_FOUND","message":"Workflow not found: eval-airixss","hint":"Use `trickest workflow ls` to see available workflows"}

This exits with code 3 (ERR_NOT_FOUND). The fix is to repoint context, then re-run:

trickest workflow ls                 # find a real workflow in the active space
trickest workflow use <workflow-id>  # repoint context
trickest node ls                     # now works

Choosing a backend (base URL)

Released installs always talk to https://trickest.io. You do not need to configure a base URL for normal use:

curl -fsSL https://trickest.io/install.sh | sh
trickest auth login

trickest status shows the active base_url so you can confirm where commands are going.

Related