Docs
Workflows
Chain models with > and +. Steer with /frontier, /team, /repeat, /parallel, /oss, /deterministic, /btw, /interrupt. Captain still routes bare prompts and owns handoff and memory.
Control words (steer without leaving the thread)
| Word | Effect |
|---|---|
/team <task> | Director plans an ensemble on one task, one reviewed answer. /team /frontier … binds a member. |
/frontier <task> | Claude at maximum effort; fallback depends on availability |
/cheap /save /speed /quality | Preference for this turn; the director chooses inside it |
/oss | Open-weight models only; composes with other modifiers in either order |
/deterministic | ADI-green serving tuple only; pins the stack for the run. See ADI |
/repeat N <task> | Rounds until N or until /repeat stop; /repeat status, /repeat abort |
/parallel <task> | A second task beside this chat; show, status, stop |
/wf <english> | Compile English into a workflow, preview, then /run wf_id. /wf save|run|list for named workflows |
/claude /grok … | Force a specific leg for this turn |
/context | Inspect or shape conversation context for the current turn |
/captain | The cheat sheet, in the TUI (also /captain <helm> to switch director live) |
/btw <note> | Steer the worker already running (mid-turn on claude/opencode legs) |
/interrupt | Stop the running worker; keep a handoff note or marked partial |
Workflow chaining syntax
One line. > (or then, ->) advances a stage; + (or and, &) runs legs in parallel inside a stage. A connector counts only when a leg prefix follows it, so prose is never misread.
/grok analyse @src/queue.ts > /cursor review it for missed cases > /codex red-team it + /claude red-team it
/grok draft the migration > /frontier harden it + /codex write the docs
/claude fix the flaky test gate: go test ./... > /codex review the fix
- A bare leg (
> /codex) requests a refinement of the previous output - One task per line also fans out in parallel
gate: <cmd>must exit 0 for that worker’s result to count as successful; one repair retry. Other successful workers can still feed the next stage- Preference words (
/cheap,/quality) are rejected inside a chain: name the legs - Max 4 stages, 4 legs per stage, 8 declared worker slots. Retries and the final director review add executions. The review combines the findings into one answer
Loop compiler
State intent ("until tests pass", "while coverage < 80%"). Use /repeat N to bound rounds and gate: <command> in a workflow to check a result. A natural-language target alone is not a machine-verified completion condition.