System mode
System mode is the diagnostic view. The snapshot passes through untouched, so nothing LocalDocks can observe is hidden from you.
What it shows
Every process your account owns, every listening socket LocalDocks can enumerate, and every service derived from the two — regardless of how the Developer Registry classified it.

The classification chips
In System mode each service row carries its verdict, because the list is mixed and the chip earns its place. In Developer mode the chip is dropped — every row would say the same thing.
- Developer — recognised development work.
- System — recognised as something else.
- Unclassified — the registry has not seen it. A real answer, not a rendering gap.
Hovering a row shows the sentence behind the verdict; opening it shows the same reason in the detail panel.

When to reach for it
- A port is taken and you do not know by what. The owner may well not be development work — that is precisely the case Developer mode hides.
- Something you expected is missing. If a service is absent from Developer mode, System mode tells you whether it is unclassified, classified as system, or genuinely not running.
- You are auditing what listens on your machine. Every socket, with its owner where one could be attributed.
Sockets without an owner
Some rows in Ports cannot be attributed to a process you own — usually because the owner belongs to another account, or exited mid-scan. Those rows are informational: they are shown, because a socket that exists is a fact, but no actions are offered on them.
Switching back
The switch is in the title bar and your choice is remembered between launches. Because mode is presentation only, moving between the two never triggers a scan and never changes what was measured. See Developer mode for how the narrowed view is derived.