The dashboard

After the wizard, the box's address is its control plane. Everything the box can do is on one page, one view per item in the side panel (a bottom tab bar on a phone) — and these docs are on the box too: the Docs view works offline.

overview	the cockpit: last boot verdict, uptime, disk, CPU load and temperature, plus an alerts strip when something needs attention. re-check now runs a read-only health check on demand; the full boot report lives under Services
streaming	the video pipeline and its providers — streaming
assistant	pick the assistant backend the box runs (Claude, Hermes, or Antigravity), chat with the box, and manage the browser terminal
files	a file explorer over /work and any mounted external drives — files and backup
services	one switch per service. Switches write the persistent config and start or stop the service immediately; what is on here is what starts at boot
users	admin only: dashboard accounts with the admin or viewer role — users and access
network	addresses and live throughput, with 24-hour history charts
system	CPU, memory and disk as 24-hour charts, save state now to write config to the media without waiting for the 15-minute autosave, reboot, and a repair action for remote access
docs	this manual, served from the box itself — readable with no internet at all

Alerts

The overview's alerts strip is the box telling you what it would otherwise DM you: a disk filling, a service that failed to start, state that has not been saved, an overlay running behind. Green means the last self-check passed; a warning names the check that did not. Every boot also self-checks and, when pipe is on, DMs you the report.

What a viewer sees

Every view is readable by every account. A viewer sees live charts, logs and status exactly as an admin does — the greyed-out controls are the visible difference, and the server enforcing their absence is the real one.

Next

Streaming · files and backup · users and access · persistence and updates · the agent and the fence