Mission Control
Account-scoped fleet attention, constellation, machines and release preparation at /fleet.
Mission Control is the web app's account-scoped view of authorized machines, work and release preparation. It lives at /fleet — Mission Control in the sidebar, at the URL the product already used for Fleet. It is not a second project manager, not a scheduler, and not a replacement for the Floor.
What it is for
Use Mission Control when you need the cross-project picture: what needs a human decision, which machines are enrolled, which published sessions you may observe, and how a release's prepared scope compares to what is already approved.
Use the Floor when you need one project's run detail — what is waiting on you, what is running and queued, and each run's own page with Cancel and Run again.
Views
/fleet opens on the current workspace and offers four views:
| View | What you get |
|---|---|
| Constellation (the default) | The authorized work as a bounded graph, with an attention rail beside it — human decisions, unknown or blocked work, missing evidence, each row with a real next step rather than invented progress — and a release strip |
| Table | The same authorized work as an equivalent table, release by release; the layout preference may stay in local storage |
| Machines | Read-only enrollment inventory, for this workspace or across your account; publish/share prepares an exact target you confirm once |
| Agents | Agents and teams, when the workspace has an owner scope to read them in |
Selecting a release opens the release inspector: prepare a release execution, review scope diff and evidence gaps. Approve and Start stay off until delivery is actually qualified.
Agents / teams stays unavailable until its own backend contract qualifies. The Operator panel is live for an owner-scoped workspace — see below and Operator.
Approvals and the operator
The Attention rail carries an Approvals card (Approvals · <count>) whenever this owner has a pending approval — the same card, one per action, that Needs you and the operator panel show, with Approve and Reject on it.
Toggling Details opens an Operator tab for an owner-scoped workspace (not Account machines): the same owner-scoped conversation documented on the Operator page, reading and acting on this workspace with the full lifecycle tool set. On a wide layout the operator panel stays open beside the inspector instead of replacing it.
What stays honest
- A healthy machine is not a finished task. All deployed is not Shipped. Counts name their denominator.
- Private sessions stay hidden until an exact publication association exists — including for the machine owner when the session was never published.
- Selected live session output is unavailable in this base. Streaming and live WSS transport stay pending their own fleet/transport evidence.
- Every mutation goes through an exact target and a durable command receipt. If the response is lost, Check recorded request reuses the same command id and payload; it does not mint a new attempt.
Release pages and sharing
An authenticated release page can deep-link into Mission Control for the selected execution. A public shared release record does not gain operational ids or Mission Control links — its disclosure stays as it was.
Related
- The Floor — one project's live runs
- Operator — the owner-scoped conversation behind the Operator tab
- Running work from the plan — queue items and documents
- Runner setup — enroll a machine the inventory can see