Machines overview
The machines panel is the cabinet’s read-only inventory of every machine registered to the fleet. Admin actions (rename, retag, deregister, move fleet) are exposed for Owners and Admins, but you do not open shells from here.
Primary surface is desktop and CLI. To open a session against any machine on this list, click into ../../desktop/machines-tab or run cmdop connect <machine>.
Machine list
Each row shows:
- Name — friendly label, defaults to hostname.
- Hostname — OS-reported, may include
.localon macOS. - Status —
ONLINE,DEGRADED,STARTING,OFFLINE. - OS — kernel and distribution.
- Agent version — semver of the running daemon.
- Last heartbeat — relative time since the last keepalive.
- Tags — fleet-defined labels (e.g.
env:prod,team:platform).
Filters and search
Filter by status, OS, or tag. Search by name, hostname, or UUID. Filters persist per member as a saved view.
Machine detail
Drilling into a machine reveals:
- System info — CPU model, RAM, disk capacity.
- Uptime — kernel uptime and daemon uptime.
- Network interfaces — addresses, MTU, MAC.
- Tags and last edit time.
- Last seen — host timezone-aware timestamp.
Real-time metrics
Charts cover the last hour / 24 hours / 7 days for:
- CPU usage.
- Memory used.
- Disk used (per filesystem).
- Network throughput.
These metrics update in real time as machines report in.
Admin actions
Owner and Admin only:
- Rename — change the friendly label without affecting machine ID.
- Retag — bulk-edit tags.
- Move fleet — migrate the machine to another fleet; confirms with the receiving fleet.
- Deregister — soft-delete the registration. Agent keeps running locally but stops reporting in.
What is not here
- Opening a terminal —
../../desktop/machines-tabor../../cli/connect. - Running a single command —
cmdop connect <machine> exec .... - Editing
permissions.yaml— that lives on the machine and is managed via../../cli/permissions.
The cabinet does not register machines. Run cmdop connect on the host. The cabinet only shows machines that already reported in via the daemon.
Where this data lives
Machine registrations and metrics are stored server-side and update in real time — the same machine state backs the desktop and CLI.