The fleet in one look
Five machines, four model calls running, 215 tokens a second across the estate, and where the next scan goes. Every count names its unit.
One line for the whole fleet, in the order you choose
Nine scans across six modes, four running at once on different machines. One pool, one order, and you set it: Top, Down, or Move to the position you type on any waiting scan, Pause and requeue on a running pass loop, Kill or Cancel on any row. The machine that holds the scan carries out the change and reports back. The page says which pass a scan is in and never claims a phase it cannot see.
LLM Status: the model and the machine under it
Model and quantization, memory held and what is left, context window, decode and prompt-reading speed today against the prior six days, by prompt size, hour by hour, and the model server's own log scrolling live.
When something needs attention, it says why
A 19 percent fall in decode speed on the week and two failed calls, each with its evidence. On a laptop hub the drift is thermal throttling before anyone notices scans taking longer.
Points of Interest
Health score with its trend, coverage stated in files and passes, findings verified against the source before they are printed.
Pre-Engagement Recon
A sizing estimate that says it is one: what a full scan would read, how long it would take, where to start.
Blast Radius
What a change reaches, and what it would take with it.
Conflict Detection
Where the code disagrees with itself: contracts, schemas, and the seams between components.
Pre-Sprint Planning
Risk before the sprint starts, from the code as it is today.