Skip to content

See and run your workflows

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-14.

What workflows do I have?

Ask what workflows you run, then list, run and manage them from the terminal.

What you get: a straight answer about the workflows on your Quox, and the commands to list, run and manage them yourself.

Just ask, in your own words:

quox · talking to Quox

How many workflows do I have, and how many of them are active?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 5ms

◐ LIST │ workflows ✔ LIST │ workflows │ 124 total, 118 active, 6 inactive · 2.3s

⛓ AEE │ envelope opened · stream_success

You have 124 workflows, and 118 of them are active. The other 6 are inactive.

15.4s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.0, 16 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 16 Oct 2026 · test report mvb37f

Quox read your workflows through its governed workflow tool and answered with the real counts. Ask it to name the inactive ones, or to show what a given workflow does, and it will.

list workflows
quox workflow list# machine-readable, to pipe elsewhere:quox workflow list --json
Commands as quox workflow --help documents them at 0.3.0.

Each row carries the workflow’s id, name, and whether it is active. A workflow has to be published/active before it can run.

inspect a workflow
quox workflow get <workflowId>

This shows the workflow’s trigger, its steps and its current state, so you can see what it does before you run it.

run a published workflow
quox workflow publish <workflowId>quox workflow run <workflowId>
A workflow must be published/active first; see workflow publish.

Running a workflow leaves a receipt: each step it took is recorded as evidence you can check afterwards, which is the point of running them through Quox rather than a plain script.

For a new workflow, author it declaratively and apply it, or scaffold one with create:

create or apply
# apply a workflow from a YAML/JSON file (created if new, diff-previewed if it exists)quox workflow apply -f my-workflow.yaml# or scaffold one directlyquox workflow create --help
See quox workflow create --help and quox workflow apply --help at 0.3.0.

Quox answered a plain-words question by calling its governed workflow tool against your QuoxCORE, not by guessing. The same workflows it counted are the ones quox workflow list shows, so the conversation and the CLI agree.

quox workflow list is read-only and raises no approval. Compare its count with what Quox told you. Every run you start shows up in that workflow’s receipts.

quox workflow delete <workflowId> removes a workflow. Deactivating (rather than deleting) keeps it but stops it running: update its state with quox workflow update <workflowId> (see --help).