Fleet board
The home screen: every thread across your open projects, grouped by status, with the evidence you need to decide what to open next.
The Fleet board is home. Every thread across your open projects is a row, so you can supervise several agents without opening each one.
What a row shows
| Field | What it tells you |
|---|---|
| Agent | Which ACP agent the thread runs. |
| Diff stat | Lines added and removed in the thread's worktree. |
| Verify evidence | Whether the named verify command passed at the current commit. |
| Merge readiness | Whether the thread can merge yet. |
| Overlap | Other running threads that touch the same files, for example OVERLAPS 3 THREADS. |
Statuses
Rows are grouped into four bands, with a count for each in the header.
| Status | Meaning |
|---|---|
| Needs attention | The thread is blocked on you: a permission request, a failed verify, a merge conflict, or a crash. |
| Running | An agent turn is in progress. |
| Unreviewed | A turn ended and nobody has opened the thread since. See Unreviewed turns. |
| Idle | Nothing is running and nothing is waiting for you. |
When more than one applies, Palisade picks the first match in this order: permission request, running, problem, unreviewed, idle. A problem is a failed verify, a conflict, or a crash.
Starting work from the board
The composer on the Fleet board starts new threads.
Pick spec or go, choose an agent and model, and select Start run.
See Your first thread.
Playbook runs appear on the board like any other thread.
The dock badge
The dock icon shows a count of threads that need attention or are unreviewed.