bro

bro fleet status + bro fleet serve

The compact live board in one read, and the loopback HTTP facade for thin clients.

bro fleet status

One read returns everything a thin client (pi extension, TUI, dashboard) needs per refresh tick β€” active beads, fleet workers, the drill frame, git state β€” where N shell calls per tick used to be the only way. All state is read, never mutated; bead-less or registry-less checkouts still answer, with the absent sections empty or null.

CommandWhat it does
bro fleet statusCompact human board β€” beads, fleet, drill, git
bro fleet status --jsonThe same board, machine-readable β€” the thin-client contract
bro fleet status --deepPlus the act exit gate for the current branch's PR (network β€” the fast path stays local-only)

Sources: bd (in-progress + ready, capped), the shared agent registry (<git-common>/bro/agents.json β€” shared across linked worktrees), the drill stack, git porcelain, and the heartbeat file (<git-common>/bro/heartbeat.json β€” rewritten by every bro review watch tick; the watch: row is the rig's liveness read).

bro fleet serve

bro fleet serve [--port N] is the write-capable counterpart: a foreground, loopback-only HTTP/JSON facade so thin clients never shell out to bd/gh themselves. The 127.0.0.1 bind is the trust boundary β€” no --host flag. The bound URL and session token are printed and written to <git-common-dir>/bro/serve.json (mode 0600); every mutation requires Authorization: Bearer <token>.

RoutePurpose
GET /Service index
GET /fleetFleet web UI
GET /api/v1/healthLiveness
GET /api/v1/snapshotWatch snapshot
GET /api/v1/agentsAgent plane
GET /api/v1/agents/<ref>One agent by ID or molecule step
POST /api/v1/agentsSpawn an agent
DELETE /api/v1/agents/<ref>Stop an agent

On this page