Getting started
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.
Install
npm install -g teamYour first team in five minutes
mkdir hello && cd hello && git init
team init # writes the team into this machine's registry
team config edit # name your seats; any CLI fits any role
team doctor # what this machine still needs
team up --dry-run # every command it would run, and every refusal
team up # starts the session and its seatsThe 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.
The few ideas
Team configuration. The team's record in the registry holds the roster and the owner's
sections — budgets, trust, grant, delegates — and the commands read it as the record.
team config reads and edits it. The whole format is in
team configuration.
Seats. A seat is one role, one model, one launch command, in its own pane. Any CLI fits any
role: vendor, model and version name what it runs, count adds instances, and parked
or stopped keeps it out of reports or out of up. Swap a seat with team config set.
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.