Understanding the dashboard
The window is four regions: a title bar, a navigation rail, the active screen, and a status bar. Each one is doing a specific job.
Title bar
- Version chip — read at runtime from the application itself, not hard-coded into the interface.
- Mode switch — the global Developer/System control. It lives here rather than inside a screen because it changes every screen at once.
- Search — opens the command palette, same as
Ctrl+K. - Settings — theme, sampler interval and the About card.
Navigation
Five working screens and one preview. The number beside each entry counts what the current mode will show, so the badge always agrees with the table you land on.
| Entry | Shows |
|---|---|
| Overview | Summary tiles, the running services list and machine telemetry. |
| Services | Processes holding a listening socket, grouped by process. |
| Processes | Every process your account owns. |
| Ports | One row per listening socket, unmerged. |
| Projects | Labelled V2 and disabled. It is in the navigation so the roadmap is visible, not because it does anything yet. |
Overview stat tiles
| Tile | Meaning |
|---|---|
| SERVICES | How many services the current mode is showing, and how many distinct runtimes. |
| LISTENING PORTS | Distinct port numbers, with the socket count and how many services are dual-stack beneath it. Ports and sockets differ whenever something binds both IPv4 and IPv6. |
| CONFLICTS | Ports bound by more than one process. Detection is not implemented in V1, so this reads — rather than a confident zero. |
| SERVICE MEMORY | The summed working set of the services shown, with their summed CPU beneath. Not machine memory. |
The meta row
The line under the page title states what you are looking at and where the numbers came from: the active mode and its one-line description, the sampler interval, the cost of the last tick, and three “N of M” counts for services, processes and sockets.
Hovering the tick figure breaks it down into process enumeration, socket enumeration and telemetry. It is published rather than logged because the cost of a monitoring tool is the user’s business.
The detail panel
Clicking any row in Services, Processes or Ports opens the same panel. It shows the endpoints the process holds, its classification and the reason for it, live CPU, memory, uptime and thread count, and then a process block fetched when the panel opens: executable path, full command line, working directory, parent PID and start time.
Status bar
- Service count with a dot that turns red while scans are failing.
- Conflicts —
—until detection exists. - Mode, with a tooltip naming how many processes and sockets are currently hidden.
- Sampler interval and how long ago the last scan completed.
- unelevated — a standing reminder of why some rows and fields are absent.
If a scan fails, LocalDocks keeps the last good snapshot on screen behind a warning rather than blanking a working interface over one bad tick.