ONE DECK.
THE WHOLE FLEET.
Command a legion of autonomous agents from a single console — every loop, every fault, every token, one source of truth. Issue one order, route it through each agent's own gateway, watch it execute. Nothing claims all-green while a backend is down.
A concept for teams running 5–50 always-on agents.
IT'S NOT FIVE TOOLS. IT'S ONE DECK.
Every navigation group is a station on the same console, drinking from the same shared health model — and in every one, the fix sits next to the evidence, not three tabs away.
Every station reads the same probe output. The snapshot, the CLI table, and the live fault map are the same function called twice — they cannot disagree.
You give the order. Every agent's own gateway carries it out.
Type one prompt. Broadcast it across the fleet or one-shot a single agent. The order streams through each agent's native gateway — not a hand-edited backdoor, not a side channel.
“The HUD never reaches behind the curtain. It pulls the same levers you would — just faster, and on the whole fleet at once.”
EVERY FAULT CARRIES ITS OWN FIX.
A fault isn't a notification you chase in another tab. The deterministic fix sits right next to the evidence that justifies it — one click, executed through the agent's own adapter, and audited on the way out.
NOTHING CAN CLAIM ALL-GREEN WHILE A BACKEND IS DOWN.
Most dashboards report. This one cannot be wrong about whether your fleet is up. The collector doesn't compute health — it reuses the exact probes the live Faults view reads. And the model probe is fail-closed: it sends a real prompt through the agent's model path and requires a completion back. A green light that's six hours old is not green.
2 VIEWS · 1 CODE PATH · 0 WAYS TO DISAGREE.
OK means a model answered. Not that a port did.
A SUB-HOURLY LLM LOOP WITHOUT A PRECHECK GATE IS REJECTED AT CREATION.
This concept models a runaway loop consuming ~25% of a sample fleet bill: a loop firing every 15 minutes with no no-LLM precheck gate — 96 cold model calls a day, zero of them needed. Fleet doesn't warn you after the burn. It refuses to let you create it.
~25% of a sample fleet bill, burned by one runaway loop:
The production design reads collector datasets; this concept uses simulated sample values.
TIMERS IN. ONE MODEL OUT. EVERY SURFACE AGREES.
launchd timers run the collector and the economics jobs on a cadence; they write one shared state. The CLI, the HUD, and the MCP server all read it — so no two surfaces can ever tell a different story.
A COMMAND DECK WITH NO DOOR TO KICK IN.
Cloudflare Tunnel + Access identity at the edge means zero inbound ports — nothing to scan, nothing exposed. The architecture is the guarantee: you don't have to trust the vendor — you can read the probe.
THE WHOLE FLEET, ONE COMMAND.
FLEETNEXUS IS COMING SOON.
EXPLORE THE COMMAND DECK.
This is a working product concept, not yet a commercial service. Explore the vision now; access will open later.
One collector · live probes · MCP server · CLI · browser HUD — one shared health model.