Fleet board

A board for the whole fleet, sorted by what needs you.

One agent is a chat window. Ten need a control surface: who is running, who is blocked, what each has changed and spent.

acme-shop · /agents

Attention is a lane, not a notification

An agent that needs a decision stops and says so, with the reason on its card. A fleet of ten reads as a short list of things only you can do.

Question for you · Approval needed · Land conflict, each with the one action that clears it
Everything else keeps running while you answer

Model, branch, turns, tokens in and out, dollars spent, and the diff so far. No opening a transcript to find out where your money went.

Each agent gets its own git worktree off your base commit. They never write over each other, and nothing reaches your tree until you land it.

One base commit, one branch each

agent/checkout-stripe

its own worktree, its own checkout

agent/soft-deletes

its own worktree, its own checkout

agent/latency-p99

its own worktree, its own checkout

land, one at a time, after you have read the diff

Your working tree

untouched until you land, and still yours to amend or revert afterwards

An automation starts an agent on a schedule or an event, as a fresh session with its own transcript. The nightly dependency audit arrived that way.

Push

GitHub · GitLab

Alert

Sentry

Payment

Stripe

IMAP

Message

Discord

Schedule

cron

guard, then run

A fresh agent session

Its own transcript, its own worktree, the same review before anything lands.

It proposes, you approve, then it works