Run a workflow
termorq-cli workflow is Pro. A Free binary omits these lines from --help and refuses the command with the same Pro sentence as the app. There is no edition flag.
The path after --workspace is absolute or starts with ~. The commands below use a sample checkout at ~/src/acme-apis.
termorq-cli workflow list
termorq-cli workflow list --workspace ~/src/acme-apis
termorq-cli workflow run refresh-acme-users
termorq-cli workflow runs refresh-acme-users| Command | What it prints |
|---|---|
workflow list | Each workflow’s name, id, and source: included, yours, or workspace |
workflow run <id> | Starts that workflow and waits in this process. The desktop app does not wait |
workflow runs <id> | Each run directory under workflows/runs/<id>/ |
A file with an unknown property prints the same sentence as Save on the page, and workflow run does not start:
Line 19: property 'foo' is not recognised.Included workflows ship with the app and stay read-only. A workspace file is .ai-terminal/workflows/<id>.yml while --workspace points at that checkout. A raw token in that file is refused by the same scrubber as the rest of the team workspace. A sample workflow uses mock:// and a secret name. It does not contain a key.
workflow run blocks the CLI process. The window, when it is open, still receives the run on a background task. Quit the app and this process stops with it. Schedules and the HTTP listener are the desktop app’s. The CLI starts the run you named.