providers¶
Configure and inspect the credentials behind workflow lanes. status reports
presence and source only; configure writes values to the owner-only secret
store. A key is never accepted as a command-line argument, so it cannot land in
shell history or a process listing.
Usage¶
mini-ork providers status [--workflow <workflow.yaml>] [<lane> ...]
mini-ork providers configure [--workflow <workflow.yaml>] [--replace] [--from-stdin] [<lane> ...]
status¶
For each lane it prints whether a credential resolves and which source supplied
it — never the value. With --workflow, the lane set is derived from the
workflow's node lane assignments, so you can audit exactly the credentials a
recipe needs before dispatching it.
configure¶
By default the value is read from a hidden terminal prompt. If no TTY is
available, pass --from-stdin and pipe NAME=value lines:
Never pass keys as flags
There is deliberately no --key option. A key on a command line is visible
to every local process and is usually captured by shell history and CI logs.
Options¶
| Flag | Meaning |
|---|---|
--workflow <path> |
Configure every lane the workflow uses |
--replace |
Overwrite existing credentials; without it, configure refuses |
--from-stdin |
Read NAME=value lines instead of prompting |
<lane> ... |
One or more lanes; omit only when --workflow supplies them |
Lanes¶
A lane is a named provider + model + transport entry in
$MINI_ORK_HOME/config/providers.yaml. agents.yaml maps roles to lanes; a
workflow may pin a lane per node. Credentials resolve by provider family, for
example:
| Family | Environment variable |
|---|---|
| Anthropic | ANTHROPIC_API_KEY (or the claude CLI session) |
| GLM | GLM_API_KEY |
| Kimi | KIMI_API_KEY |
| MiniMax | MINIMAX_API_KEY |
| DeepSeek | DEEPSEEK_API_KEY |
Provider-specific names live in providers.yaml; the names above are the
families mini-ork doctor preflights.
Where values are stored¶
configure writes to the vault's writable backend — by default the owner-only
$MINI_ORK_HOME/config/secrets.local.sh (mode 0600). Set up a different backend
in vault.yaml; see Vault and secrets.
Check what resolves:
mini-ork providers status --workflow recipes/code-fix/workflow.yaml
mini-ork vault status
mini-ork vault which ANTHROPIC_API_KEY
Exit codes¶
| Code | Meaning |
|---|---|
0 |
Status printed, or configuration written |
2 |
Usage error (bad lane, missing --workflow value, refusal without --replace) |