blowhorn stop

Stop everything, right now: on this machine, or on every machine sharing the store with --all.

blowhorn stop

Stop everything, right now: on this machine, or on every machine sharing the store with --all. A stop does what a pause does -- nothing new is claimed anywhere it covers -- and one thing more: work already running stops at its next safe point, never mid-post, so a pass mid-flight on another machine, or a manual or agent run there, ends the way a cancelled one does and its work returns to the queue. blowhorn stop --resume lifts a stop, and lifts only the pause the stop itself set: a pause that was already in place when the stop landed stays in place.

output

blowhorn stop [OPTIONS]

Flag	Type	Default	Description
`--all`	boolean	`false`	Stop every machine sharing this store, not just this one: no machine claims an activity, and work already running on any of them stops at its next safe point. Recorded in the store with who stopped it and why, so every machine reports the same reason. Without this flag the stop is this machine only
`--resume`	boolean	`false`	Lift a stop instead of setting one: this machine's, or every machine's with `--all`. Lifting a stop also lifts the pause the stop itself set, and no other pause
`--reason`	string		Short note stored with the stop and shown wherever the stop is reported
`--json`	boolean	`false`	Emit machine-readable JSON output
`--platform`	string		Accepted and ignored by `blowhorn stop`: this command never acts on a platform, so `--platform` has no effect here -- including a value inherited from `BLOWHORN_PLATFORM` or defaults.platform in .blowhorn.yaml
`--pace`	string		Accepted by `blowhorn stop` because `--pace` is a global flag, but this command does no paced work -- it sleeps between nothing -- so the value changes nothing about how it runs and appears only in the Pace column of the -v summary. Resolved as CLI flag, then `BLOWHORN_PACE`, then defaults.pace in .blowhorn.yaml (normal when none is set); an unrecognized value is rejected before anything runs
`--risk-profile`	string		Accepted by `blowhorn stop` because `--risk-profile` is a global flag, but this command does no gated work -- no Risk Profile hold, cap or pace applies to it -- so the value changes nothing about how it runs. A value after the command word wins over one before it; an unrecognized value is rejected before anything runs

Also takes the shared flags: --config, --log-dir, --profile, --exclude, --headless, --chrome-launch, --headed, --dry-run, --verbose.

Examples:

terminal

$ blowhorn stop
$ blowhorn stop --all --reason "a post is going out wrong"
$ blowhorn stop --resume --all
$ blowhorn stop --resume
$ blowhorn stop --all --reason "a post is going out wrong" --json

Output: json with --json, text otherwise.

Last modified October 27, 2026

blowhorn stop

blowhorn stop

Cookies