Safety

The owner

Owner, grants, policies. The owner is a person at a terminal outside herdr. Only the owner grants rights: team grant and team delegate record what a seat or pane may do, budgets and trust set what it may spend and reach. Agents move inside that envelope and stop at its edge. Approvals guard against mistakes, not against a hostile process running as the owner.

CallerMay
the ownerrun it, from a terminal outside herdr
a seat an active create-grant names by its own registry idrun it, on the paths that record covers and before it expires
a run with no terminala real run is refused: team up: only the owner or a `leads` seat runs this, from a terminal outside herdr or its own pane; --dry-run prints the plan and ! up would refuse: with that sentence, and launches nothing
a seat this team's record marks leads — its orchestrator, or a registry roster line that says leadsrun it on this folder's own team file, and the run does not relaunch or close that seat. --session and --file are refused before either is read
a caller the run admitsrun --dry-run, which reaches nothing and changes nothing
a caller the run does not admita real run is answered with the one word deny on stderr and nothing on stdout — no reason, and no plan — and exit 1. A --dry-run is never denied: it prints ! up would refuse: with that reason, ! to unblock: with a leads seat's own run of this folder from its pane (or the owner's, from a terminal outside herdr), and — when no flag kept the file unread — the plan, and exits 1
the orchestrator's seat, where the row above does not admit it and the file's grant lists uprun it on this folder's own team file, and the run is audited as the grant's. A lead the map admits is not constrained by a grant, and the grant or delegate path applies only to seats the map does not admit: a grant that names another seat or pane, or leaves up out of its scope, refuses this fallback run, and a run the map admitted asks it nothing and is audited only as the row's. A file with no grant section grants nothing. The run does not relaunch or close that seat. --session and --file are refused before either is read, in the grant's words
a seat of this team the record does not mark leads, or a pane of another sessionrun --dry-run only; a real run is refused, unless the live grant admits the orchestrator's seat or the live file's delegates section names that pane with up in its entry's commands, and a --session or --file it passes is refused before either is read

The team lives in the registry

The team lives in this machine's registry, not in the project: team init writes it there and team config get|set|unset|edit edits it, so nothing is committed and a fresh clone carries no team. A project that still has .agents/team.yaml from 0.5.3 moves it with team migrate.

Grants and delegates, the owner's alone

Records the grant the owner gives the orchestrator's seat. It is an owner section: only the owner writes it. Omitted, it reads as null.

Names panes outside the team's session that may run some operational commands as a delegate of this team's record. It is an owner section: only the owner writes it. Omitted, it reads as null and nothing is delegated.

What team never does

  • Nothing writes a lab's config or an AGENTS.md.
  • A write that does not validate is refused whole, and nothing is stored.
  • Approvals guard against mistakes, not against a hostile process running as the owner.

Launching a Cursor seat, like launching cursor-agent by hand, creates Cursor's own project record under ~/.cursor/projects for that folder; team writes no trust (.workspace-trusted) and no Cursor config.

A screen hatch is an escape hatch for a CLI whose screens the data primitives cannot express.

Who may run what

Who may run each command
CommandWho may run it
team initthe owner, from a terminal outside herdr; a seat an active create-grant names by its own registry id
team doctoranyone, in any terminal; the owner
team upthe 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 session
team downthe 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 it
team statusthe 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 entries
team seats
team send
team dropsOnly 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 watchAnyone, in any terminal.
team registerthe owner; a seat of this team; a caller the file's delegates section names for up
team nexta declared seat of this team, on the pane the state records for that seat
team checkthe 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 entries
team ackThe owner, or a seat of the team, from a terminal outside herdr or its own pane.
team addThe owner.
team answerthe owner, from outside herdr; the orchestrator, from its own seat
team archivethe owner, from a terminal outside herdr; the orchestrator's or the operator's seat; any other seat
team ask-showanyone who can read the key file
team briefThe owner reads any team file it names.
team brokerthe owner, in a foreground terminal outside herdr, one per clone
team busthe owner, in a foreground terminal outside herdr, one per clone
team clientanyone
team commitsanyone — a seat, an agent-run CLI, or the owner, from any folder; a seat, on its own branch, before it reports; CI, on a push
team config
team daemonstatus; run; install, uninstall; fault-watch
team delegateOnly the owner, from a terminal outside herdr.
team development-moderead, or set … --show / --dry-run; set <mode>
team feedAnyone in the checkout may run it.
team grantOnly the owner, from a terminal outside herdr, in every form.
team holdthe owner, from a terminal outside herdr; the orchestrator's or the operator's seat, on the pane the state records for it
team importthe owner, from a terminal outside herdr
team issuesAnyone in the checkout.
team listAnyone, from any folder.
team lockAnyone who can write their own home, from a folder whose team file loads.
team mcpanyone, in any terminal; a seat's own launch line
team messagesAnyone in the checkout.
team migratethe owner, from a terminal outside herdr
team owner-seat
team pausethe owner, from a terminal outside herdr; the team's orchestrator's seat, on the pane the state records for it
team plana declared seat of this team, on the pane the state records for that seat
team policyThe 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 pranyone — a seat, an agent-run CLI, or the owner, from any folder; CI, on a push
team procadd and done are for the owner and for a seat the team file declares.
team projectsAnyone may run it, from any folder.
team queuethe 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 caller
team raisethe orchestrator's seat or a lead's seat, on the pane the state records for it
team releaseanyone, from any folder; the Linear check alone
team reloadThe owner at a terminal may name any seat, including the operator.
team removethe 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 swap
team renamethe owner; a seat holding leads (or the orchestrator when no role holds leads); a seat an active create-grant names by its own registry id
team replyThe owner, or a seat of the team, from a terminal outside herdr or its own pane.
team restartthe owner; the orchestrator's seat — and any seat the record marks a lead: the map's leads
team resumethe owner, from a terminal outside herdr; the team's orchestrator's seat, on the pane the state records for it
team revokeOnly the owner, from a terminal outside herdr, in every form.
team routeA run with no terminal — an agent outside herdr, a detached script — is refused before the team file is read.
team seat
team sessionsAnyone on the machine.
team settings
team swapthe 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 it
team tempothe owner, from a terminal outside herdr
team unlockThe caller who took it.
team usageanyone — a seat, an unplaced agent, or the owner, from any folder; the owner at a terminal; every other caller
team workflowanyone — a seat, an agent-run CLI, CI, or the owner, from any folder
team worktreethe owner; the orchestrator's seat, the operator's seat

What this version builds

team is a small command-line tool with no runtime dependencies: you set the roster, the agents do the work in herdr panes, and you stay the one who decides. It is early and herdr only. Every command team --help lists is here. Node 22 or later runs it.