ds tower
On this page
Defined in cli/commands/tower.ts. The release tower: one production release at a time, across every machine and account (Release: one release at a time explains why). Each command runs the installed devstride Claude Code plugin's release-clearance provider and hands back its verdict and exit code unchanged. It needs the plugin at the release this repository requires (PLUGIN_MIN_VERSION in cli/commands/machine/claude.ts), gh signed in, and push access to the repository; it skips the wrapper's AWS gate. Without the plugin it prints the install command and exits 1.
/devstride:release claims and hands back the clearance for you. Use these by hand to see the tower, or around a release step you do yourself.
ds tower status#
ds tower status [--short] [--json]
Prints CLEAR, or who holds the clearance (user, machine, since when, phase, last check-in, branch and pull request), then On final: #<n> <branch> for the oldest open release pull request into master, Waiting: #<n> <branch> for each later one, and Hotfix landed: #<n> <branch> <time> for each hotfix merged into master since the release started. A release that is still checking in but has sat in one phase past its time budget shows as STUCK, naming its machine, session and phase (see If a clearance is stale). It ends with a Close-out owed: … line for each release this machine handed back whose close-out work (documentation, customer replies, teardown, a release note) is not yet done. Exit 0; exit 1 with UNKNOWN (…) when the clearance cannot be read, which never means clear. --short prints one line for the status line: the holder, or when clear a close-out owed · … line while this machine owes any, otherwise nothing; --json prints everything as one JSON object.
ds tower claim#
ds tower claim [--wait] [--purpose <text>]
Takes the clearance: CLEARED, exit 0. When another release holds it, prints BUSY held by …, exit 2; with --wait it checks every minute (for up to three hours) and takes it the moment it frees. A wait that finds the holder STUCK ends once with exit 5, so you can tell the owner; --wait --ignore-stuck then waits on. A stale clearance is taken over when its release never opened a pull request or closed it unmerged; one whose pull request is open, or merged but not closed out, exits 3 with STALE … so a person can decide whether to adopt it. Exit 1 is an error: never proceed without clearance. A claim keeps itself alive in the background for as long as the session that made it is running. Typed from a Claude Code session that runs an older copy of the plugin than the one installed, it warns first (type /reload-plugins) and claims anyway.
ds tower heartbeat#
ds tower heartbeat <phase> [--branch <branch>] [--pr <number>]
Records the phase the release is in and its branch or pull request. Exit 4 with NOT HOLDER means another session holds the clearance now: stop.
ds tower release#
ds tower release [--force] [--owed <item>]
Hands the clearance back: RELEASED, or CLEAR (nothing to release). A release hands it back once its deploy is confirmed and the branch work is done (release.clearance.scope: "cut-to-deploy"), and its post-deploy check runs afterwards as owed work; --owed <item> records close-out work still to run after that, which ds tower status and ds tower owed then list on this machine. Exit 4 when another session holds it. --force releases it whoever holds it, printing the record first; it is the owner's command, for a clearance that cannot be released any other way.
ds tower adopt#
ds tower adopt --yes [--original-stopped]
Takes over a stale clearance whose release must be resumed, and prints the branch, pull request and phase to resume from. Exit 2 when it is not stale, 4 when nothing is held. /devstride:release asks the owner before it does this. A STUCK clearance, whose session is still checking in, is adopted only with --original-stopped, on the owner's word that its session has stopped.
ds tower owed#
ds tower owed [--done <item>] [--clear] [--release <name>] [--pr <n>]
Lists the close-out work this machine still owes after a release handed its clearance back: documentation, owed customer replies, local teardown or a release note, one OWED line per release, or NONE. --done <item> settles one item, and the entry goes once its last item is done; --clear drops a whole entry. --release and --pr pick the release when the machine owes work for more than one. It never fails: the record is local to this machine.