chant run
Synopsis
Section titled “Synopsis”chant run <name> [flags]chant run list [flags]chant run status <name> [flags]chant run signal <name> <signal> [flags]chant run cancel <name> [flags]chant run log <name> [flags]Description
Section titled “Description”chant run starts and manages Op workflows — named, phased workflows defined in *.op.ts files.
chant run <name> runs local by default: the Op executes in-process with no Temporal server, worker, or built worker.ts. Pass --temporal to run against a Temporal cluster instead (worker spawn + workflow submission). One flag selects the runtime — no config is inspected. See Local vs Temporal for the trade-off.
Local mode covers phase sequencing, retries, activity profiles, and onFailure compensation. Gates, schedules, durable resume, and the run-management subcommands (list / status / log / signal / cancel) require --temporal and a reachable Temporal server. Connection settings come from chant.config.ts under temporal.profiles; see Worker Profiles.
Subcommands
Section titled “Subcommands”run <name>
Section titled “run <name>”Run an Op. Local by default — executes in-process, rendering each phase and step as it runs. With --temporal, spawns the compiled worker and submits the workflow to Temporal, polling status every 3 seconds until it completes or fails.
chant run alb-deploy # local executor (default)chant run alb-deploy --json # structured result on stdoutchant run alb-deploy --temporal # run via Temporalchant run alb-deploy --temporal --profile cloudchant run alb-deploy --temporal --report # print deployment report instead of runningA gate or schedule in the Op fails fast in local mode with an actionable message — re-run with --temporal.
run list
Section titled “run list”List all discovered Ops (*.op.ts files) with their current Temporal run status. Requires --temporal.
chant run listOutput columns: NAME, PHASES, TASK-QUEUE, DEPENDS, OVERVIEW, STATUS.
run status <name>
Section titled “run status <name>”Show the current state of an Op’s latest workflow run.
chant run status alb-deployrun signal <name> <signal>
Section titled “run signal <name> <signal>”Send a named signal to unblock a gate step in a running workflow.
chant run signal alb-deploy gate-dns-delegationThe signal name must match the signalName passed to the gate() builder in the Op definition.
run cancel <name>
Section titled “run cancel <name>”Cancel the active workflow run. Requires --force.
chant run cancel alb-deploy --forcerun log <name>
Section titled “run log <name>”Show run history for an Op.
chant run log alb-deploy| Flag | Description |
|---|---|
--local | Run with the local in-process executor — the default (run <name>) |
--temporal | Run via a Temporal cluster: gates, schedules, durable resume (run <name>) |
--json | Emit the structured run result as JSON on stdout (run <name>) |
-p, --profile <name> | Temporal worker profile to use (from chant.config.ts); implies Temporal mode |
--report | Print a deployment report instead of running (run <name> --temporal only) |
--force | Required for run cancel |
Exit Codes
Section titled “Exit Codes”| Code | Meaning |
|---|---|
| 0 | Success (workflow completed or command succeeded) |
| 1 | Error (workflow failed, Op not found, Temporal unreachable) |
See Also
Section titled “See Also”- Ops guide — define
*.op.tsfiles - Local vs Temporal — choose the runtime
- Worker Profiles — configure Temporal connection
chant graph— visualize Op dependency graph