Commands
One page per command team --help lists. Each page gives the synopsis, what the command reads and
writes, who may run it, every flag, the refusals with their exact text, the exit codes, and examples.
team initWrites a new team into the registry: a skeleton record for this project, at ~/.config/team/team-config/<team id>.json, or with --restore the copy this machine stored.the owner, from a terminal outside herdr; a seat an active create-grant names by its own registry idteam doctorReads the machine and says what the team needs before it can run: 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 recorded budget check reads right now.anyone, in any terminal; the ownerteam 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 watch, in a workspace of its own labelled Watch · <project>.the owner; a seat an active create-grant names by its own registry id; a seat this team's record marks leads — its orchestrator, or a registry roster line that says leads; a caller the run admits; a seat of this team the record does not mark leads, or a pane of another sessionteam downStops the team: asks every running seat the live file names to exit, closes its workspace, and stops the herdr session — unless something was left in it: an agent still running at the end keeps the session up, and the last line says it is not stopped and counts what is left in it.the owner; the orchestrator's seat — and any seat the record marks a lead: the map's leads; the approved delegate, when the file's delegates section names itteam 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, each naming the command that repairs it.the owner, from a terminal outside herdr; a seat of the team, placed in the file's session, on the pane the state records for it; a pane outside the team that the live file names in its delegates entriesteam seatsShows the seat registry for the team: one row per seat whose STATUS is not stopped, or every seat when --all is given, with its human name when the file writes one, its stable seat handle (seat_<12 hex>), role, CLI, model, effort, status, state, last active time, and pane.team sendWrites one message to one seat.team dropsLists the drop files waiting in the calling seat's own drop folder.Only the seat itself, on the pane the state records for it: a drop folder is one seat's mailbox, and the command answers from the caller's own placement.team watchWatches a running team.Anyone, in any terminal.team registerWrites the record for one seat that is already running, without touching it.the owner; a seat of this team; a caller the file's delegates section names for upteam nextClaims one record from the file the team file names, and holds it with a lease in this clone.a declared seat of this team, on the pane the state records for that seatteam checkOne answer to one question: is anything wrong with this team that someone should act on? It reads the team file, the record this machine holds of it, the state, herdr and the registries, and changes nothing except the repairs the owner's --repair makes — the state's two leftovers dropped, the dev-mode mark an agent's registration left cleared, and herdr's drifted sidebar lines set back from the file — no git is needed, so it answers as well in a plain folder as in a repository.the owner, from a terminal outside herdr; a seat of the team being checked; a pane outside the team that the live file names in its delegates entriesteam ackMarks a message record read without printing it.The owner, or a seat of the team, from a terminal outside herdr or its own pane.team 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.team answerPresses the one recorded key of a folder-trust dialog, and only that key.the owner, from outside herdr; the orchestrator, from its own seatteam archiveSnapshots the team as it is — the team file, the state and the send queues — into one archive folder, then stops the team.the owner, from a terminal outside herdr; the orchestrator's or the operator's seat; any other seatteam ask-showPrints the question from a signed ask when the marker's HMAC matches that question and the request id, and expires_at is not yet past.anyone who can read the key fileteam briefteam brief rollout delivers TeamCLI's general seat brief — the built-in first text every seat gets, held in this build — to the team's declared seats without a launch.The owner reads any team file it names.team brokerRuns the one process that holds the tracker credential and answers team next over a local socket.the owner, in a foreground terminal outside herdr, one per cloneteam busRuns the foreground process that owns the project's event log (events.jsonl), runs the periodic reconciliation pass over durable message and seat records, and serves publish and subscribe over .agents/bus.sock.the owner, in a foreground terminal outside herdr, one per cloneteam clientThe app-key side of a client grant.anyoneteam commitsChecks 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, and no line of its message may match a forbidden pattern.anyone — a seat, an agent-run CLI, or the owner, from any folder; a seat, on its own branch, before it reports; CI, on a pushteam configTwo things: the team's own record, read and edited with get, set, unset and edit — what .agents/team.yaml used to hold, before [team migrate](migrate.md) moved it into the registry — and the settings registry, printed with keys.team daemonThe one machine-wide TeamCLI daemon.status; run; install, uninstall; fault-watchteam delegateAdds or replaces one external delegate in the current team file.Only the owner, from a terminal outside herdr.team development-modeOne name, one machine-wide setting, above every team and project.read, or set … --show / --dry-run; set <mode>team feedReads the project's message history from ~/.config/team/<project>-<hash>/messages.jsonl (mode 0600, inside the project's state folder and never in a lobby or the repository), together with any briefs/<from>-to-<to>.md files and Desk audit lines when present.Anyone in the checkout may run it.team grantWrites an authority record for the current team, in one of three forms.Only the owner, from a terminal outside herdr, in every form.team holdA hold is a note on the team's work: why it was placed, who placed it and when, and when it lapses.the owner, from a terminal outside herdr; the orchestrator's or the operator's seat, on the pane the state records for itteam importMakes a team file this team's registry record: .agents/team.yaml when no file is named.the owner, from a terminal outside herdrteam issuesLists the typed records in the one file the team file names.Anyone in the checkout.team listShows the herdr sessions on this machine: the running ones, unless --all is given.Anyone, from any folder.team lockTakes a named lock on this machine, so one heavy run holds it at a time.Anyone who can write their own home, from a folder whose team file loads.team mcpReads the MCP bridge's local state — the helper under its install root, every bridge config in the lobby, the seat guards beside them, and the public front the connector dials — and reports it without touching it.anyone, in any terminal; a seat's own launch lineteam messagesShows a message that is already waiting and writes the receipt that says it was shown.Anyone in the checkout.team migrateMoves this team's definition from .agents/team.yaml into the registry, and retires the file.the owner, from a terminal outside herdrteam owner-seatThe owner seat is the human owner's own seat.team pauseA pause stops a seat taking new work: the whole team's, or one seat's own.the owner, from a terminal outside herdr; the team's orchestrator's seat, on the pane the state records for itteam planPrints the queue a claim would consider, in the order team next would consider it, and claims nothing: no lease, no renewal, no state write, no tracker write.a declared seat of this team, on the pane the state records for that seatteam policyReads and resolves the effective policies for the current team (or a named seat) across the tighten-only inheritance chain (entity → project → team → seat), or sets and unsets owner-signed policy declarations (team policy set and team policy unset).The view (team policy) may be run by the owner, a seat of the team, or an approved delegate pane that may read the team.team prChecks one pull request body against the team file's rules: the body must end with the signature the file's pullRequests rule writes, and no line may match a forbidden pattern.anyone — a seat, an agent-run CLI, or the owner, from any folder; CI, on a pushteam procThe processes a team's seats started, kept as a register in the team's state: one record per name, each naming the seat that recorded it, when, the process id to watch and one line about what it is.add and done are for the owner and for a seat the team file declares.team projectsLists the projects this machine's registry holds, from ~/.config/team/projects.yaml (mode 0600, under ~/.config/team/ beside the team records).Anyone may run it, from any folder.team queueAdds one record to the team's local task queue, or lists it.the owner; a declared seat of this team, on the pane the state records for that seat; the seat the approved team file names in installer:, on its recorded pane; any callerteam raiseA raise is a lead's own line to the owner, delivered the moment it is written rather than waiting in the watch's next digest.the orchestrator's seat or a lead's seat, on the pane the state records for itteam releaseChecks the public npm and GitHub records of one release: the exact version and its checksums on npm — with a provenance attestation when the file declares trusted publishing for the package — the tag and where it points, the GitHub release, and the changelog entry.anyone, from any folder; the Linear check aloneteam reloadCloses one running seat and launches it again when the team file's model, version or effort differs from the model, version and effort recorded at its last launch — or when a seat that takes its rules as a first message has a per-seat rules file that no longer holds the rules text the live team file gives it.The owner at a terminal may name any seat, including the operator.team 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; a seat an active create-grant names by its own registry id; the orchestrator's seat — and any seat the record marks a lead: the map's leads; the approved delegate, when the file's delegates section names it; the orchestrator's seat, when the file's grant lists swap; the approved delegate whose entry lists swapteam renameRenames a seat in the team's configuration — or with --renumber, renumbers every numbered seat to match the seat_numbering in force — and carries over the seat's identity and records across the team file, the approval record, the state, the registry, herdr, and on-disk seat files.the owner; a seat holding leads (or the orchestrator when no role holds leads); a seat an active create-grant names by its own registry idteam replyAnswers the sender of a message record, or closes its thread.The owner, or a seat of the team, from a terminal outside herdr or its own pane.team restartRestarts one declared seat in place without editing the team's configuration: prints the seat's input-box, turn and context facts, asks a free seat to exit and waits for its pane to return to its shell, closes its workspace, and launches the seat again in a fresh workspace.the owner; the orchestrator's seat — and any seat the record marks a lead: the map's leadsteam resumeteam resume clears the pause that team pause placed and restarts the queue: team next claims again and the watch dispatches work to idle seats again.the owner, from a terminal outside herdr; the team's orchestrator's seat, on the pane the state records for itteam revokeRemoves the grant or one external delegate from the current team file, or ends a standing grant.Only the owner, from a terminal outside herdr, in every form.team routeAnswers one seat's address for the native channel: the pair's rule, the recipient's live pane, and the socket its session listens on.A run with no terminal — an agent outside herdr, a detached script — is refused before the team file is read.team seatOne seat as an object: the settings it holds and where each value comes from, the row team seats reads for it (status, state, source, pane, last active), its last turn as the CLI hook wrote it, and the newest session TeamCLI recorded for it in this session — the conversation, when it started and ended, and its cost when one was measured.team sessionsLists the sessions TeamCLI recorded for each seat: one append-only record per CLI session, written by the launch and stop commands themselves — up, add, restart, reload, down and remove — and never from an agent's word.Anyone on the machine.team settingsOne seat's settings, each with where its value comes from: a signed settings record at the seat, team, project or entity level; the team file; the team's own order standing under a seat that writes none; the release default; or unset.team swapThe entity's model rule says which labs may run on which seats (Policies rule 10).the owner, from a terminal outside herdr; the orchestrator's or the operator's seat, on the pane the state records for it; any other seat of the team, on the pane the state records for itteam tempoSets the team's tempo.the owner, from a terminal outside herdrteam unlockReleases a lock team lock took, and only that caller's lock.The caller who took it.team usageShows what this machine holds: every team it keeps a store for, read as one report — each team's accounts and windows, with what is left and used, when each figure was last read and from which source — then one SEAT CLI ACCOUNT table per team.anyone — a seat, an unplaced agent, or the owner, from any folder; the owner at a terminal; every other callerteam workflowChecks, dry-runs, or replays a workflow definition (version: 1): - team workflow check <path> [--json] checks one workflow definition and its transition graph: structural schema rules, reachability, transition ordering and ambiguity, hook effects, and resolved role references (owner, lead, integrator, and the role: strings declared on seats in the team's configuration (.agents/team.yaml on the legacy file source), read from the working directory first and from <path>'s folder when the working directory has no team file).anyone — a seat, an agent-run CLI, CI, or the owner, from any folderteam 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 orchestrator's seat, the operator's seat