mast

Overview ¶

Command mast is the entry point for the mast agent runtime.

mast one-shot mode: `mast --task=<class> [--model=...] [--provider=...] [--session-db=...] "<prompt>"`. A positional prompt switches the binary from serving to running exactly one turn to completion and printing the result on stdout (logs stay on stderr). Serve remains the no-prompt default — scripts/demo-spike2.sh's flag-only invocations are untouched.

mast sessions — the v0.1 operator-facing session surface (docs/durable-execution-design.md, "Operator-facing surface").

mast sessions list   --session-db=... [--user=...] [--state=paused|aborted|interrupted|idle]
mast sessions show   <session-id> --session-db=...
mast sessions resume <session-id> --interrupt=<iid> --response='{"approved":true}' [--addr=...]
mast sessions abort  <session-id> [--reason=...] [--addr=...]

list/show read the SQLite session DB directly (works with or without a running daemon). resume/abort go through a running daemon's /resume and /abort endpoints — resume must be executed by the runner that owns the workflow, and routing abort through the daemon keeps a single SQLite writer.

Design deviation, recorded: durable-execution-design sketches `resume --token=<token>`. Resume tokens are the v0.2 programmatic- pause surface; the v0.1 pause is a HITL RequestInput, whose verified resume contract (docs/spike-findings.md, Q2) is keyed by interrupt ID. Hence `--interrupt` + `--response` here.