What people actually open it for.
Not personas — situations. Each of these is a thing that was annoying enough to build a feature for.
Show a client the branch, right now
Agencies and freelancers
Open a tunnel on the port the feature branch is running on and send the URL. No deploy, no staging environment to keep in sync, and no explaining why staging is three commits behind.
Keep a build running while you leave
Anyone with a long build
The terminal is tmux. Close the laptop, open the phone app, and reattach to the same session. The build never knew you left.
Find out what is on port 3000
Anyone with more than one machine
Scan a port range and see what answers. Scan a folder tree and register the projects you forgot you had. The dashboard then checks those ports on every load.
Watch a fleet of coding agents
Anyone running Claude Code, Codex or Grok
One list of every AI session on every machine, showing which are working and which are waiting on a reply. Get a push when one needs you, rather than checking four terminals.
Hand a teammate read-only access
Small teams
Share a project. They see it, they can comment, and they get a terminal only if you grant one. They never see an edit path, because the API does not have one for them.
Work from a machine you do not own
Anyone travelling
The dashboard is a URL. Terminals, ports, files and AI sessions on your own machines, from a borrowed browser or the phone in your pocket.