Commands
Each command has its own page in docs/commands: the synopsis, what it reads and
writes, who may run it, every flag, the refusals with their exact text, the exit codes, and examples
that bun run ci runs against a fixture team.
team initWrites the team file: a skeleton for this project, or the copy of .agents/team.yaml you last approved on this machine.the ownerteam approveThe owner approves the team file: reads it, shows what changed since the last approval, asks for the number of seats, and writes the record this machine holds it to.the owner (--show: anyone)team checkChecks a commit, or a range of commits, against the team file's rules: every commit must carry a seat's signature where the file says, no line of its message may match a forbidden pattern, and, with --pr, a pull request's body is held to the same rules.anyone; read onlyteam doctorReads the machine and says what the team needs before it can run: whether this file is the one the owner approved, whether herdr and each seat's CLI are installed, at the tested version and logged in, whether each launch names the model the file says, whether a watch has run for the session, and what each approved budget check reads right now.anyone; read onlyteam statusShows the team as it stands: one line per seat with what the session's herdr shows of it, and one difference for each way the file, the state and the live session disagree.anyone; read onlyteam upStarts the team: the herdr session when it is not up, a workspace and a seat for every seat the file declares and this machine can run, and the watchdog pane that runs team watch.the ownerteam downStops the team: asks every running seat to exit, closes its workspace, stops the watch, and stops the herdr session.the owner, the coordinator or the operator seatteam watchWatches a running team.anyone, one per session; it types only its fixed nudge, into an empty idle promptteam addStarts one seat of a running team: a seat the file declares but nothing runs for — team up started the others — or a temporary seat beside the team, which the file does not declare at all.the owner, the coordinator or the operatorteam removeTakes one seat out of the team: asks it to exit, waits for its pane to come back to its shell, closes its workspace, and edits the file so the seat is not started again.the owner, the coordinator or the operator; only the owner removes the coordinator or the operatorteam worktreeCreates and removes a task worktree: a second checkout of the project on a branch of its own, where one seat does one task.the owner, the coordinator or the operator