Skip to content
LocalDocks

Filtering and search

Every table has a free-text filter, a set of chips and sortable columns. The command palette is a separate, faster route to a service.

Per-screen filters

ScreenChipsFree text matches
ServicesAll · Node · Python · DatabasesLabel, process name, framework, PID, any port
ProcessesAll · Services · OtherName, PID, parent PID
PortsAll · TCP · UDPPort, protocol, address, PID, process name, service label

Filtering is instant and local to the snapshot already on screen. It never triggers a scan, so typing in a filter box costs nothing.

The LocalDocks Ports table in System mode with a loopback filter applied, showing 38 of 101 sockets and the row count in the header.
A filtered table still reports the total: 38 of 101.

The chips and the text filter compose: a chip narrows by kind, the text box narrows within it.

The LocalDocks Services table filtered by the text 'node', showing the matching services and a row count reading 2 of 4.
Text filter on Services. The header keeps the total in view.
The LocalDocks Processes table in System mode with the Services chip active, narrowing hundreds of processes to only those holding a listening socket.
The Services chip on Processes — the same relationship the Services screen is built on, seen from the process side.

Counts stay honest

Every table header reads “N of M · sorted by …”. A filtered view is never presented as the whole set, and the navigation badges count what the current mode will show, so a badge always agrees with the table you land on.

Sorting

Click a column heading to sort by it. Services and Processes default to memory, because that is usually the column that explains a slow machine. Ports defaults to port number, ordered so that IPv4 precedes IPv6 within the same port and a dual-stack pair reads as one thing.

The command palette

The LocalDocks command palette listing show, open in browser and copy URL actions for each running service.

Ctrl + K opens it, Esc closes it. You can type a command or a port number. Each service offers three actions:

  • Show — open that service’s detail panel.
  • Open in browser — launch its localhost URL, validated against an http/https allowlist first.
  • Copy — put that URL on the clipboard.

In V1 the palette covers services only. It does not search processes or ports, and it does not run navigation commands beyond opening a service. Broader coverage is on the roadmap rather than implemented.

When nothing matches

The table says so in words — “No services match the current search or filter” — rather than collapsing to a hairline, which would read as a rendering fault instead of an empty result.