NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
Ship with a team that never sleeps. Specialized agents, from any lab.
Latest stable
0.5.19
Last release 12 days ago
07 Nov 2026
Ships unpredictably
gaps range from 8 days to 10.6 years
Nearly every release is documented
notes for 27 of 28 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
28 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
…only in team doctor and team --about , and a deprecation warning only in team check and team doctor , with its repair. Colour reaches a terminal only…
The first release since 0.3.5, and the first on npm since it. The file in the clone is the
record: team approve is no longer a command, the commands read the file itself, and a seat
that is already running is written into this machine's registry so the rest can reach it by
name. A send says which channel it took; a team names the project
it sits in; each seat's state and the two sidebar lines beside it say what it is doing and where
that reading came from; and grants, delegates and holds put the owner's decisions where the
commands read them.
One output contract, and team --about. Every command prints under one contract across its
plain text, --json documents, --help usage and exit codes: a reading opens with
team <project>, session "<session>" (or the project line), prints an uppercase-headered
table, notes and any difference:/repair:/who: blocks, and closes with one summary line; an
action prints its plan steps under --dry-run and one summary line. --json prints one
document per command, its schema first (team.<command>, format 1) and a refusal as a
team.error document carrying the contract's exit id and repair; the schemas are published
under schema/. Output is quiet by default: stopped seats wait for --all, repeated notes
collapse to one line with (x<n>), the what 0.5.0 must not pretend block prints only in
team doctor and team --about, and a deprecation warning only in team check and
team doctor, with its repair. Colour reaches a terminal only — never --json, never under
NO_COLOR. team --about prints the version, the licence, the docs link and the block; watch
and broker keep their foreground loops and take no --json.
The registry, and team register. The machine keeps records of the agents it has seen, the
teams and the projects they sit in, under ~/.config/team/. team register <seat> writes the
record for one seat that is already running — a pane herdr places under that name, holding a
CLI at the seat's prompt — so team send, team seats, team watch and team down can
address it. It types nothing into the pane, and a pane change re-records the same agent rather
than a second one: a record's identity is the file's seat under its team, never the pane.
Records are appended, never deleted — a removed seat is marked ended and its history stays
readable — and a record confers no right. The record also carries the seat's pane, which binds
the sender: only a caller standing on the pane its own record names acts as that seat. A send
reads its delivery pane live, by the seat's name, so a pane that closed or was reused since the
record was written is never typed into; a claude-code seat's cross-session socket address is
recorded for team route.
team send, and the channels a seat is reached on. One message to one seat, ending in one
confirmed outcome: delivered, answered, held, not-submitted, timeout, unreachable
or refused. A send walks the receiving seat's delivery order — native, mcp-inbox, then
typed when no level of the seat's chain changes it: the entity, the project's registry
record, the team file's delivery_order and the seat's own each may drop a leg or reorder the
ones it keeps, never add one — and this build carries no mcp-inbox leg and opens no socket,
so every delivery it makes goes by the typed leg, and each leg the walk could not take is
recorded unavailable on the history line. A plain send gives the seat the body whole in a
mode-0600 drop file and types one short trigger line naming it — the body is never typed, and
never split — for every seat, Claude Code's included: a socket write to a busy session can land
at its held-message dialog, where the box is blocked, so no path opens a cross-session socket
at all. --wait, which would ride one, is refused for every seat — a Claude Code seat's
refusal names the native leg
(team route and the caller's own SendMessage) that will carry a waited send, and any other
seat gets its own reason — and nothing is written. A seat the receiving team file marks
stopped: true is not addressed at all: the send, its dry run and team route refuse it as
stopped, with its own exit id, before a drop file exists, a leg is walked or a history line is
written.
--json, --file, --dry-run and --list round it out. The native channel is the sender's
own half: team route <seat> answers the address a delivery from the sender's cross-session
tool uses — the recipient's agent id, session, CLI and pane, and its socket — and
team send --record <seat> --channel native --ms <n> writes that delivery down, one
via native history line, the body not passing through the CLI. A message's body is written
down in the project's history, which team feed reads, with the send-to-outcome milliseconds
and the path it took; the refusal for a seat no record covers names the command that writes
one (team up, team register <seat>).
A seat its file marks assistant: true — one per file, never a seat with count — is its
entity's assistant, and the routing admits it to the entity's main coordinator: the first mark
found walking the entity's teams in chain order, the entity's own team first and then its other
teams by team id, never a role's name. Send is denied by default: the owner may send to any
agent; an orchestrator to an orchestrator of its own team or of a team in its entity, never
across entities; a team's orchestrator or operator to any seat of its own team; an assistant
to its entity's main coordinator; any seat to its own team's orchestrator; and an owner-signed
send grant to what it names.
The send grammar: @<nickname>, <seat>@<team>, lead@<team>. One grammar answers
team send and team route: an agent id (agt_ and twelve hex), @<nickname>,
<seat>@<team>, <nickname>@<team>, lead@<team>, or a bare seat or nickname of the caller's
own team. <team> is a team's registry id, its project or its session, as the record spells
it. lead@<team> reaches the seat its file marks leads: true — never a seat merely named
lead, and never a role's name — and a team with no lead is refused, because there is no one
to deliver to; a roster marking two leads refuses the address, naming both. A nickname is the
file's nickname: line, unique inside its team and free to repeat across teams:
@<nickname> asks the caller's own team first, then the other teams of its entity, and from a
folder that is no team every team the registry holds. Exactly one match sends; several are
refused, each named by the <nickname>@<team> spelling that picks it; none points at
team send --list. A spec two roster entries answer — one seat's name and another seat's
nickname of the same team — is refused naming both, before anything is typed. Every form
resolves to one seat's registry record before admission runs, and admission judges that
record's seat: a nickname added or removed never changes who may reach whom. A full address
reaches another team from any folder — and from a folder that holds no team file, where that
send is the owner's — the receiving team's file judges it, and the drop lands under that
team's .agents; a bare name from a folder that is no team is refused with the forms that
need none. lead is reserved from this release on: no new seat and no nickname takes the
word, and a file written before it that declares a seat named lead still loads and answers
its bare name, team check noting the repair team rename lead <new-name>. A history line
keeps the address as written: where the caller wrote a form rather than the seat's name, it
carries spec and resolved (agt_…), and team send --list prints each seat's NICKNAME
— -, an @<nickname> in the file's own roster, a <nickname>@<team> in another's.
A lead from a 0.3.5 or 0.4 file is still the lead. A team whose lead seat still carries the
old role word coordinator is judged by its file, never the word: an orchestrator of the same
entity reaches it by lead@<team> or its seat address, exactly as for a file written for this
release, and team check notes the 0.5 word, role: orchestrator, without a difference or an
exit change.
A held send is retried, not abandoned. When a typed send leaves its drop because the
seat's composer held text, the seat did not take the trigger, or a dialog was up — held,
not-submitted, or an unreachable that is a dialog — send writes a pending record beside
the drop, and a running watch delivers it on a later pass: only when the pane reads idle or
done, its box is free or holds nothing but that send's own trigger line, and under the
seat's lock, so a retry cannot interleave with a new send. A trigger line the failed send left
unsent is submitted with the Enter and never typed over. The retry is bounded to three tries
within thirty minutes; a delivered retry is written into the history, and a give-up names the
sender and the recipient seat, says why, points at the drop while it is still there and asks
the sender to send it again. A record whose drop file was moved or removed is given up on
rather than typed, and the age bound is applied before the pane is looked for, so a vanished
seat's record still ages out. The send's held, not-submitted and dialog lines name the drop
and the retry — a dialog's reads unreachable now (the screen reads <kind>); a running watch retries it when the seat is idle; the drop file is at <path> — while a send through the
daemon keeps no record a watch reads, so its not-submitted line promises no retry.
Projects. Entity, then project, then team, then seat. A team names its project in its team
file, a team that names none is its own project, and a team two projects name is refused by
team check, naming both. team projects lists the registry's projects — immutable id,
display name, entity, lead and teams; team status --project <name> covers every team of one
project; team send --list shows each addressable seat's project. Settings inherit through
the four levels — a lower level may tighten, and loosen only where the level above allows it —
and the first project-level setting, seats_cross_teams, decides whether a seat may cross
teams within its project. Within a project the project lead and its teams' leads are admitted
to each other, by capability, never by a role's name.
The lobby, recorded per session. A team's seats work in its lobby: the file's explicit
lobby:, else the lobby the registry recorded for the session, else
~/.config/team/lobbies/<entity> for a team that names an entity, else
~/.config/team/lobby. The record keeps one entry per session — up --session alt records
its own, and neither replaces another's — and once a session is recorded, editing the file's
entity: never moves it; a record written before the map reads as one entry.
Seat state, and the words beside it. team seats prints the seat registry: one row per
seat with its stable handle (seat_<12 hex>), role, CLI, model, effort, status, state, source,
last active time and pane; --all adds the stopped rows, and --watch refreshes the table
every two seconds. STATE is the word — working, idle, blocked, done, held,
unreachable, unknown — and SOURCE is where it was read: the pane's screen, the CLI's own
hook files (cli-hook, valid 24 hours; a working reading carries the 120-second window),
herdr's word, the seat's newest trace (a commit, an ack or a message) or its process; a seat
no source has heard from past the blind threshold reads unknown (blind), and counts as not
working.
team status's rows end in the word a send would use — socket or typed — and
team status --all prints the expanded columns. The pane's two sidebar lines — its workspace
label and the display line under it — are the file's own text, re-applied from the file by
team register without a relaunch, and team check reports one that reads as neither.
team rename, and the seat numbering. team rename <seat> <new-seat> renames a seat in
the live team file and carries what the old name held: the file's references to it — the
coordinator: and operator: lines, a grant:'s seat: — the registry record under its
agent id, the herdr agent's name, its task leases, pending send-drops, mailbox messages (a
signature this machine can check is remade under the new name), its rules, queue and notes
files, the state's records and the message history, so nothing is left addressed to a name no
seat holds. Comments, order and every other seat stay as written: the edit is by the line,
never a rewrite of the file. team rename --renumber [--dry-run] rewrites every numbered seat
to the width and separator the seat-numbering setting in force asks for (builder-1 →
builder-01), leaves a name with no number plain and skips a seat written with count; a dry
run prints each from -> to (dry run) and writes nothing. A seat number is read as a number,
so a roster naming the same role and number twice — builder-1 beside builder-01 — is
refused at load rather than left for an address to pick between. The owner or leads renames;
a target already declared, a target another seat's nickname holds, a counted seat renamed
partially and a name outside the seat grammar are each refused with the reason. A verified copy
of the file this machine still holds is carried across the rename where the renamed digests
match it, so a rename alone reports no drift.
Three more launch profiles. grok, gemini and muse join claude-code, codex,
cursor and antigravity, each with its own screen reading, unattended flags, login check
where the CLI offers one, and tested range. The Claude Code profile is tested with CLI
2.1.288 to 2.1.302. The Antigravity profile is tested with CLI 1.2.16 to 1.4.1.
The Codex profile is tested with CLI 0.157.0 to 0.161.0.
Jules as a pane seat. jules joins the profiles with its 0.1.42 CLI: a send to a jules seat
still writes its drop file, and the body is typed through the CLI's own screens, so a new
remote session on the seat's own repo is the delivery. A seat sends only to the repo of its own
folder; when the account's repo list does not hold that repo, the send is refused with nothing
typed rather than sent elsewhere. The profile never deletes a session: a turn is ended with
ctrl+c alone, and every jules seat's rules carry Never delete a Jules session. herdr cannot
report a jules pane's agent, so the profile declares herdr_status: unreliable and the screen
is the reading — an idle session table is a free seat, a running card a working one — across
status, check, watch, list and down.
Grants, and delegates, the owner's alone. team grant <seat> --scope <acts> sets the team
file's one grant — the seat the file's orchestrator marks, and the complete scope it may run; a
later run replaces it exactly — and team revoke grant removes it. team grant <seat|@team> --capabilities <cap,...> writes a standing grant record in the shared grants folder — a seat
resolved to its registered agent's id, @team to the project's team id — out of the closed
vocabulary write, read, review, gate, merge, deploy, act-as and use-broker,
with --expires, --name and an optional --scope of paths; a team grant never carries
grant, create, agree or leads, and naming one is refused with the rule. The records
are signed and read fresh at every use: a revoked or expired grant admits nothing, and
revocation is its own appended record, never an edit of the grant — team revoke <name>
appends it. team delegate <session/pane> --commands <acts> records one pane outside the
team, up to eight, and team revoke delegate removes one. A create-grant — a record in
~/.config/team/grants/ naming its holder by registry identity, agent: an agent id (agt_
…) or team: a registry team id, with the paths or entity it covers and its expiry — admits
its holder to init, up, add and remove under those paths until the record expires.
The holder is the caller's own registry record while it is running, placed by the session,
pane and seat it stands as, and a team record admits an agent registered to that team; the
owner, an agentless pane and an unplaced process have no registry record, so no record admits
them. A record spelling a name, a seat, a pane, a session or a runner grants nothing, and one
naming both agent and team, or no holder, is skipped with the rule. Every one of these is
the owner's, from a terminal outside herdr, with a --dry-run, and none can widen its own
entry.
The work queue. team issues lists the typed records in the one file the team file names;
team next claims one, held by a lease in this clone (--mine, --release, and --wait at
the file's tasks.cadence); team plan prints the queue a claim would consider and claims
nothing, a passed deadline marked (overdue) and never dropped or reordered; and team broker
— the owner's foreground process, one per clone — holds the tracker credential and answers
team next over a local socket, with the
file's tasks.policy filtering every record before it crosses. A broker runs as the same OS
principal as the seats: that is integrity, not authenticity, and it isolates nothing.
The rebuilt team usage. team usage reads the machine rather than one project: every
team it keeps a store for, the caller's own project among them whether or not it holds one, in
one report — each account and window with what is left and used, when it was last read and from
which source, its reserve and its state, under the account table and a closing line that counts
the machine's teams, labs and accounts. Anyone may run it from any folder, and it changes
nothing: no check runs, nothing is written, no credential, key or CLI session file is opened. It
does read the seat panes herdr records and may run a CLI's own usage command where a seat runs
one, bounded by a fifteen-second timeout. The owner at a terminal reads the machine's
subscriptions and the caller's team, and --all adds every team's seat-to-account rows; every
other caller reads the restricted view, a closed list built before anything prints. --tree
adds the quota view between the account lines and the team tables — one block per lab and per
account, each window with its margin and state — while the one advice: line, printed either
way, names the accounts with headroom or where a walled seat should move. Shared machine
subscriptions live once in ~/.config/team/accounts.yaml, and --json carries the same report
as one document, format 1.
Around the seats. team list shows the herdr sessions on this machine — the running ones
unless --all, --seats for the active breakdown, --watch to refresh every two seconds;
team feed reads and follows the project's message history, --all merging every project on
the machine; team messages verifies a waiting message, prints its body and writes the
receipt; team proc keeps the processes the seats started as a register in the team's state;
team hold <reason> places a note on the team's work (--release clears it) that status and
doctor show; team tempo
sets the watch's pace; team lock and team unlock take and release a named machine lock, so
one heavy run holds it at a time; team mcp status and team mcp doctor read the MCP bridge's
legs; team ask-show prints one signed ask; team reload and team restart bring a later
model or effort edit to a seat already running; and team worktree list joins the worktree
set.
team check is integrity, not authority. It reads the file, the state, herdr, the
registries and the agents' records, and reports the differences alone, each with its repair: a
reading of whether the records agree, never a grant. No approval, no launch and no right
follows from a clean answer. The owner's --repair is its one write: it drops the state's
leftovers — a record for a seat the file no longer declares, with the pane it claims, and a
session the state holds with no seat of the team in it — re-checks each against the state on
disk, prints one repaired: line per drop and logs it. Herdr is not asked which records are
leftovers: the state's own claims are the subject. The repair still waits on the live read, so a
check whose herdr cannot answer drops nothing; a temporary seat is never a leftover, and neither
is the file's own session or the one the run checks.
The file in the clone is the record: the commands read it, and add, remove and down keep
going when no approval record exists. team up admits the owner or the team's lead seat; where
that refuses, a delegates entry whose commands include up or a seat the file's verified
grant names for up. Anyone else is told deny and exits 1, and a dry run says what the
real one would (! up would refuse: with the reason, ! to unblock: with the owner's run of
this folder, then the plan).
team up gains --serial, launching and waiting on one seat at a time, and a fresh
orchestrator or operator seat starts in the project folder and every other seat in the team's
lobby.
The watch runs in a herdr workspace of its own, labelled Watch · <project>: up ends its
plan by creating it and running the watch in its pane, and a bare team watch from the owner's
terminal hands itself there and returns — a --no-nudge or --no-notify run stays in the
caller's terminal. The state records the pane, the pid and the heartbeat; team status shows
them, and team check flags a heartbeat older than two in-force cycles.
team down --wait gives a working seat up to 120 seconds to come free and leaves one that
never does running; an agent still in the session keeps it up, and a pane is closed only where
the state records it for one seat.
team status is gated like the other commands (team status: this team is not yours to read),
prints a hold as its first note, and marks a rate-limited row (rate limit on <account>, resets at <time>); its drift line reports the effort on its own when the model matches and only the
effort differs (<seat>: effort <seen>, file says <effort>), and an effort the file never
declares is never a drift. team doctor prints a hold line and cleans every line it prints of
escape sequences and invisible characters.
team watch nudges any idle seat, not the operator's alone, and announces a waiting message
with Team: run team messages; it reports a seat stopped on its provider's connection error or
at a rate limit, naming the account and the reset time, and types into neither screen; a
temporary seat is left as it is for the owner to remove.
A report meant for the operator stays out of the panes. team watch writes it to
.agents/team.log and the desktop notification, never typing it into a free seat; the only
lines it types are a work drop's line naming its file and the message ring, and an attention
report a flickering screen shows is said once, not every other pass.
team add takes --model and --effort (the owner's, on a declared seat) and starts a
temporary seat from --temporary --like <seat> --until <end>; team remove <lead> --keep then
team add <lead> replaces the agent on a lead's seat without stopping the team, and a removal
by a caller other than the owner leaves the pane running, renamed <name>-left.
team list shows the registry beside discovery: a registered team and its seats join the rows.
team worktree gains list and remove --branch <name>, and reads the live file's workspace
values. team release check warns when npm's next dist-tag points below latest and prints
the exact npm dist-tag add command, without running it.
team check --repair settles every finding the file alone can settle, in one owner-signed
run: besides the state's leftovers, it re-records each seat an agent registered under dev
mode, clearing the mark the way an owner's team register <seat> does, and sets herdr's
drifted workspace label and display line back from the file through the same two writes
team register makes. Each written line is printed as repaired: and logged as its phase
finishes, and a sidebar write the session refuses prints the line it could not report. A
model drift keeps its relaunch advice: the repair never starts, stops or relaunches a seat,
and it stays owner-only. Under a governing dev-mode policy the check's rows still collapse to
one quiet count, and --repair clears the marks behind it.
team approve is no longer a command: team up admits from the live file, and add, removedown keep going when no approval record exists.Your coding agent can read these notes before it upgrades. Set up the MCP server →
A release about a seat whose screen nobody can read: a caller other than the owner can now let it go on herdr's word alone, and team status and team w
A release about a seat whose screen nobody can read: a caller other than the owner can now let
it go on herdr's word alone, and team status and team watch say so instead of staying quiet.
team remove <name> from a caller other than the owner: a seat herdr reports idle or done<name>-left (or -left-2, and so on), leaving the--keep marks it stopped with the same line instead. Aworking is never taken out.team status marks the row when the profile cannot read the seat's screen: an idle or done<state> (screen not recognised).team watch reports a quiet seat on an unrecognised screen instead of going silent.A release about reading a machine and reading a file: team usage reads every store this machine holds into one report, under one resolved view — the o
A release about reading a machine and reading a file: team usage reads every store this
machine holds into one report, under one resolved view — the owner at a terminal reads the full
one, every other caller the restricted one — and every line that carries a figure may carry its
pace; a pane the approved file names as a delegate may approve the ordinary changes, a roster or
a launch line or a rule, and can never approve a change to its own authority; and the credential
warning's path exemption is the filesystem's own verdict, so a path-shaped word that is not a
real directory warns.
team usage reads the machine: every store this machine holds into one report, under oneowner-no-tty and still--json render fromusage.outside is gone: a run outside every project is a note and exit 0,usage.store is the command's one refusal.team usage line that carries a figure may end with its pace:pace <n>%/h, used points per hour, signed, one decimal, or pace not known where the stateteam approve takes a delegate: a pane the approved file names in delegates: with approverules section and the seatthis change needs the owner: <what changed>), including any section a later version adds, so a delegate can never approvedelegates, limits, trust, budgets, the workspace whosesetup runs commands. An ordinary difference rejoins the owner's path — the same key guards,--confirm inert and no terminal read — and leaveslstat says it is a real directory — fail closed on an absent path, alstat, never stat), or any error — so a credentialA release about names and evidence: the bare team check reads the team itself and answers with its differences, a ref's check moves to team commits ch
A release about names and evidence: the bare team check reads the team itself and answers with
its differences, a ref's check moves to team commits check and a pull request's to
team pr check, the seat that leads is leads: true and its word is orchestrator, and
team usage reads one project's budgets and approvals back, read-only. The machine gate and the
watch leave their readings in the log, doctor and status say when the machine's total swap
sits under what the check asks, a refused run remembers nothing and a refused dry run exits as
the real run would, and the READMEs say plainly what the owner refusal is — and is not.
team check, bare — every word --session or --file, or none at all — reads the teamremember is false forteam usage: one project's block, read-only — the budgets in force as status prints its--json carries the samedoctor and status say when the machine's total swap sits under the figure the check asks:team up would refuse now, and the repair — setmachine.swap_free_min, then run team approve.up andadd logs the line and the figures it was decided on, and a watch pass logs what it read atunread where a figure was not taken.leads: true on that seat, and the word for it is orchestratorcoordinator: key still selects it, printing one notice per file, and andialogs.trust takes the new word too.team check <ref> becomes team commits check <ref>, and its --pr <file> half becomesteam pr check <file>, which checks one pull request body alone and needs no repository; everyteam approve: the paste guard reads the command's own terminal and answers three ways — onlyapprove.input-waiting), and a terminal that cannot be read refuses apartapprove.input-unreadable) — and is proven under a real pty. The signing key is created onlydown that finds the session lockA release about repairs, found on the first day of 0.3.1: down and remove stop a seat and clear what the stop leaves, a CLI's own exit question is ans
A release about repairs, found on the first day of 0.3.1: down and remove stop a seat and
clear what the stop leaves, a CLI's own exit question is answered in both the forms it draws
where its profile declares the key, every key follows a fresh check of the pane, a delegate can
start a team whose session is down, one run at a time takes a session, the lobby may hold the
files the shipped profiles declare, the watch's nudge waits for its text and is sent only as
the watch's own, up resumes its own interrupted launch, status shows no model it did not
verify, and a stop clears only the exit text it typed.
SECURITY.md: how to report a weakness in private — the repository's security advisories,down and remove stop a seat: the exit text is typed into a box read empty and idle, read--abandon closes a seat this run asked whose exit could not be typed or confirmed, and thedown clears the session it stopped itself: it waits until herdr lists the session stopped,session <name>: stopped and cleared. up clears a stoppedup, add, down or remove runs at a time per session: the run takes the .run lockup.run-lock,add.run-lock, down.run-lock, remove.run-lock), and a lock left by a dead run is taken.claude/scheduled_tasks.lock) no longer blocks a team with no Claude Code seat, up, adddoctor read the one set, and doctor names the profile each declared file presentup resumes its own interrupted launch: a seat whose pane was made but never renamed — a runstatus shows no model it did not verify: a row whose name does not match shows the model(unread), never the model from the file.down and remove clear only the exit text they typed: a box holding other text is notUnchanged by this release:
add on a stopped session still asks for a manual clear: herdr session delete <name>.--abandon.team down — theteam down --abandon.team up started within a second or two of a team down that left the session up can report aleft out: its pane has been back at its shell for <n> s and shows no CLI prompt; left at launched, and run team up again to resume it —team up again starts it.team approve still asks its question.up never answers a trust dialog or a vendor notice: the seat is left out —up refuses.team approve run by an agent on a machine that has no signing key yet still makesA release about delegation: a team's owner approves, once, which panes outside the team's own session may run up , down , add and remove for that team
A release about delegation: a team's owner approves, once, which panes outside the team's own
session may run up, down, add and remove for that team, and every delegated run is
matched on session and pane id against a file that is exactly the approved one.
delegates, a team-file section (owner section, one to eight entries): each entry names a<herdr session>/<pane id>, matched whole and case-sensitively — and the operationalup, down, add, remove it may run. Entry order and command order are partseat: or any other key.team approve prints one Delegate: pane <pane> may run <commands>. line per entry, beforedocs/team-file.md: the format page, with the delegates section.Not in this release: approve by a delegate — never, approval is the owner's, and a commands
list naming approve is a load error; --abandon by a delegate — never; restarting a running
seat (needs a team restart that changes no file); status, doctor and their JSON for a delegate
— next.
A release about setting a team up and upgrading it: one lobby per machine, signed approvals, a caller gate bound to the pane the team recorded, a laun
A release about setting a team up and upgrading it: one lobby per machine, signed approvals, a
caller gate bound to the pane the team recorded, a launch that reports one line per seat and waits
for its owner at a dialog, and, in the repository, the launcher package @teamcli/cli, published
in a later release. Three changes are breaking; read UPGRADE-0.3.md before upgrading a running
team.
~/.config/team/lobby instead of a.lobby folder beside the project's worktrees, and trust: entries must be absolute folders thatstatus, doctor), but team upteam add refuse it until trust: is migrated and approved again; team doctor andteam up print the whole block to paste.team approve runs once more; running seats aren't disturbed.add, remove, worktree, down andanswer are refused; the owner repairs it with team down, then team up. --session and--file on those commands are the owner's alone, from a terminal outside herdr, refused beforestatus and doctor read any team file without writing anything; watch --file is the owner's;watch.idle_repeat is off unless set.team worktree reads the approved copy of every value it uses.up refuses a launch line that can't run where its seat starts.doctor warns about a model-less launch only when nothing checks it; status gives a runnableversion is "0" (the placeholder init wrote) reads as unset; a wrong modelteam up reports one final record per seat, a vendor notice as a kind of its own, and cleanedteam up no longer closes a seat that stops at a dialog: it keeps the workspace, records that theo opens the pane, s skips the seat, q stopsteam answers nothing and types nothing at a dialog. An owner with no terminal is neverteam answer and the dialogs policy: a coordinator may answer a trust dialog when the ownerteam release check, its linear and activity checks, and --file for it.packages/teamcli: the launcher package @teamcli/cli (the same tool, typed teamcli), in theteam's own process is still in it; the repair is named.up --file starts no watch for it; start it by handteam watch --file <path> from the owner's terminal). The line "watch: started" can be printedteam started, and up closes it without input and launches it again. A seat stillup leaves it ("already ready"),remove refuses a bare shell, and status names team up as a repair that does not work for it.team remove <seat> --abandon (or team down --abandon), then team up.team down, then team up) removes the case.team down that cannot confirm the exit text it typed leaves that text in the seat's input box;down skips the seat ("holds unsent text"). Clear the box by hand.--file is the owner's. The owner runs them.team statusup leaves out because its screen's model family is not the file's ("left atteam up refuses the session until that pane is closed by hand, and team down does not close--until on the commands that take it is not validated.Three things in this release were checked by tests and by runs in process on a test host, not on a
real herdr session. They are due on the owner's own upgrade.
add, remove, worktree,down with no --session): covered by the caller and command tests; not typed in a real pane.team up (o, s, q): covered by the launch tests with an injectedteam up,team up again: run in process, where it ends with every seat ready;A safety patch: on Codex and Cursor the composer's input row is read only under the box's frame, so a person's text can no longer be submitted togethe
A safety patch: on Codex and Cursor the composer's input row is read only under the box's frame, so a
person's text can no longer be submitted together with team's; and Antigravity's and Cursor's
dialogs are recognised as the permission or question they are.
team typed under the glyph, the read-back held the typed text alone, and the Enter submitted theteam had typed. The input row is now read only under theunknown, with no typing and no Enter, closing the limitunknown; they are now read as the permission or question they are. team typedunknown, permission and question all refuse typing alike.A feature release: the budgets table falls back per window and names the source each figure was counted from; team doctor runs each account's approved
A feature release: the budgets table falls back per window and names the source each figure was
counted from; team doctor runs each account's approved budget check; overrides.yaml teaches a
shipped profile new dialog and quota patterns without waiting for a release; and every typing path
reads the input row from the captured frame and its prompt column, pressing Enter only when the box
reads back as exactly the typed text. Upgrade: a seat with no label is titled with its model and
version, and team down now clears the session it stopped.
cli; a pane herdr can't list keeps its figure — not knowing is not proofdown could type /exit into a running seat and remove refused it as unsent. Thedown --wait waits and removeteam had sent it; the watch's nudge and the exitdown and remove pressed Enter on an unread box the same way. Every Enter now waitsteam doctor runs each account's approved budget check once, for the owner only, and reports itsoverrides.yaml, beside the approval in ~/.config/team/<project>-<hash>, may add dialogteam approve records it. Until then thedoctor and status name the change.schema/team.schema.json describes the team file (draft 2020-12), assembled from the sameschema:check in CI keeping it current. The schema shipsteam init writes now opens with a# yaml-language-server: $schema=… line pointing at this version's copy.docs/reference/cli.md is a generated CLI reference — every command, flag and positional, fromcontract:check, with the same snapshot ascontract/cli.json. Help text is unchanged.bun run conformance checks an implementation of screen reading and the YAML subset against theteam conformance-adapter is the TypeScript implementation of that protocol. Itteam --help.bun run coverage prints the capture coverage matrix — for each CLI and screen kind, how manycoverage:check keeps contract/capture-coverage.json current in CI, failing on a difference orcapture claim counts whereignore_case: true beside its match — the flagexcept list too. Claude Code's trust question, spelled out in both cases letterprompt, rule, footers,"prompt" cannot ignore case: only a dialog pattern may).screen_module — a code module inside the package's profiles folder — for aworking, every dialog stage and unknown, so a hatch can only add caution, neverclaude opus 5.5). Ateam doctor warns when a seat's name or label repeats the project or the session. The warning(fallback) whenstatus line (fallback) — and status --jsonfallback field on each budget row. The fallback is per window, not perlast seen <age> — the room the figure last held. It never refuses a launch.team down now clears the herdr session it has itself just stopped, its line readingstopped and cleared, so up after down starts the team again instead of refusing on theherdr session delete <session>. up never deletes a session: one it did not stop keeps theteam down now stops a seat the file renamed after up launched it: the state records the CLIdown resolves the file's name first and the state's second,ὠ and a 0, so an\u{…} form.chrome pattern could hide the unmarked second choice of a dialog. The guard tested sixweekly 39% used\r\n broke the contract on its line[\D0-9][\s\S]; the positive class is now refused with the reason when the profile loads.[^\S\n] and a shorthand alone are unchanged.↑ N more lines and the tail; the box is now read as folded, and Enter is pressed only when the4.996 USD against a 5 USD floor printed "5.00 USD, at or below its 5.00 USD floor"; theA safety release: 0.1.1 could type a nudge or an exit into the shell left after Claude Code exited, and a seat could silence the watch's reports about
A safety release: 0.1.1 could type a nudge or an exit into the shell left after Claude Code exited,
and a seat could silence the watch's reports about itself. Upgrade.
down's and remove's exit) also needs herdr to report the agent'sremove --keep and add record the new digest when stopped is the only change, so--no-notify on the watch silenced a report addressed to the owner, and any caller--no-notify drops only the operator's notice — the log line stays, andteam status does not read the flag. The watch's own notices — the operator could not be--no-nudge and --no-notify are the owner's.account:, when one vendor's two accounts are twovendor, and the choice is part of the seat's fingerprint,budgets.accounts — a name the budgetswatch.checks edit is unapproved, the approved list stays in force: nothing new is turnedThese are standing rules, not a task: reply ready and wait for your brief.; a launch option that stays in force on every later--append-system-prompt) closes with only These are standing rules, not a task. A team file whose own rules: already end with that line doesn't get it twice.remove --keep, or parked by hand, since its last approvalseat X changed for each after upgrading, and up and add refuse until the ownerTry " rule.ctrl+c to stop.up, add andstatus count it: a fresh check inside its reserve refuses a launch after the watch has exited, asources decide which reading counts.up, add, status and the watchsources.A safety release: 0.1.0 could type into a Codex permission dialog, and could read a quota figure a seat wrote itself. Upgrade.
A safety release: 0.1.0 could type into a Codex permission dialog, and could read a quota figure a
seat wrote itself. Upgrade.
team could answer a Codex permission dialog. With the status line pinned belowstatus-last composer's pinned line. The dialog is reported and never answered, and rulescheck reading stays first, and a wrong figure can only refuse a launch orfloor refuses a launch: the watch keeps the money each spend check reads in theup and add refuse a seat whose account is at or below its floor. A reading that isbun run build empties dist/ first, so a file left by an older build can no longer end up in aThe first release: set up, change and watch a project's team of AI agents from one file, .agents/team.yaml . Runs on Node 22 or later, with no runtime
The first release: set up, change and watch a project's team of AI agents from one file,
.agents/team.yaml. Runs on Node 22 or later, with no runtime dependencies.
examples/team.yaml. (#2, #11)team init and team status: write the skeleton file and keep it out of git through.git/info/exclude; print the file's seats against the running session, each difference with its--json prints the same facts as one JSON document (format: 1) for scripts. (#3, #33)team approve: record the file, its ceilings and its seats on this machine after a read-back and--show prints the approved copy. (#4, #5)team check: check one commit, a range or a pull request body against the signature rule;team doctor: check this machine for what the file needs — herdr, each CLI, login, launcher,--login checks read-only that each declared CLI is signed in, using eachteam watch: report idle and blocked seats, unsent input and machine figures, and nudge the--no-nudge and --no-notify turn those off. (#6, #7,/proc, soteam answers there as on macOS. (#29)team up and team down: start and stop the session and its seats, each with its caller rule;--dry-run prints the plan and changes nothing. (#5, #13, #14)team up and team add: every machine: start limit — load, memory, disk, free swap and swap--dry-run prints the refusal too. (#26)claude-code, Codex, Antigravity and Cursor: approval flags added only atteam add and team remove: start one declared or temporary seat; stop a seat, then take it out--keep leaves it stopped, --abandon is the owner's. (#19, #20)team worktree new and team worktree remove: create a task worktree from an up-to-date base, ordocs/commands, every example run in CI. (#31)weekly N% left, for the OpenAI account.budgets is an owner section: marks, freshness, and each account's reserve or floor. A checkteam approve. watch.quota_marks is read, with a warning.team status prints a budgets table, and the same rows in --json, when an account is named orteam watch reports a budget: each mark a window crosses, an account inside its reserve or floorbudgets.check_every,status,up and add count it. watch.checks: { budget: off } turns the report off.watch section is an owner section, its timings included: an edit to interval,idle_first, idle_repeat, team_idle, nudge_wait or unsent_after needs a new approval, andwatch.checks keeps its own finer line inside the section.budgets section is an owner section too, its accounts and marks included: an edit tostale_after, check_every or the accounts needs a new approval, and untilup's and add's launch gate, and status's table — runs with the values ofmode: shared and works in worktrees starts in the lobby — the parent ofworkspace.path with .lobby beside the worktrees, inside trust and outside every protectedup and add maketrust or inside a protected checkout, and refuse a seat the fileNothing published for this version
One column per quarter.