Skip to content

CLI flags

Flags override config and defaults for a single run. This page lists the global flag and the common per-command flags for pipemason start and pipemason program start.

Global flags

FlagMeaning
--max-tier <haiku|sonnet|opus|fable>Set the model-tier ceiling for this run. Overrides the cost_controls.max_model_tier ceiling in config; the runner applies whichever ceiling is more restrictive. The tier ladder is haiku < sonnet < opus < fable.

Common run flags

These apply to pipemason start (a single feature) and, except where noted, to program runs as well:

FlagMeaning
--base <branch>Override base-branch detection and branch from the given branch.
--prOpen a pull request at the finalize phase. Implies --push.
--pushPush the branch at finalize (off by default).
--stashAuto-stash a dirty working tree instead of refusing to start.
--no-cloudRun without registering the run with the cloud control plane (no live dashboard).
--use-api-keyUse ANTHROPIC_API_KEY from the environment for agent execution instead of your subscription.
--scope <scope>Constrain the run to a specific scope.
--stop-after <phase>Stop the pipeline after the named phase rather than running to completion.

Program flags

Additional flags for pipemason program start, which drives a multi-story program:

FlagMeaning
--mode <mode>Program mode: greenfield-system, greenfield-mobile, brownfield-upgrade, or brownfield-extension.
--parallelism <n>How many stories may run concurrently.
--branch-strategy <strategy>How story branches relate (stacked by default).
--max-cost <usd>Cumulative program spend ceiling; pauses the program once reached.
--max-daily-cost <usd>Per-day spend ceiling (resets at midnight UTC); 0 disables it.
--dry-runPlan the program (story DAG) without executing the stories.
--force-newStart a fresh program rather than resuming an existing one.

Examples

# Open a PR and cap the model tier at sonnet
pipemason start "add a /version endpoint" --pr --max-tier sonnet

# Plan a greenfield program with a daily spend cap, without executing
pipemason program start "build an issue tracker" \
  --mode greenfield-system --max-daily-cost 40 --dry-run

Note

Flags persist only for the run they are passed to. To make a setting permanent for a repo, put it in .pipeline/config.yml instead.