Teams

Spawn several agents on the same task, each in its own worktree, with explicit dependencies between them.

The shape

agents teams create pricing
agents teams add pricing claude "rewrite endpoint" -n be
agents teams add pricing codex  "build route"      -n fe
agents teams add pricing claude "run tests" -n qa --after be,fe
agents teams start pricing --watch

Each teammate gets its own isolated copy of the repo (a worktree) and runs independently until its dependencies are satisfied. --watch streams a live status board to the terminal.

Why DAG dependencies matter

Real refactor work doesn't parallelize cleanly — the test pass usually needs the backend and frontend done first. --after tells the runner not to start qa until both be and fe are green. The runner schedules everything else as it can.

Coming soon

The full reference — boundary contracts, retry semantics, output capture, disband behavior — is being written. For now see agents teams --help.

Related: Worktrees, Sessions.