Skip to content
LocalDocks

Getting started

LocalDocks starts scanning as soon as it opens. There is no project to create, no workspace to choose and nothing to configure first.

First launch

The window opens on the Overview in Developer mode. A background sampler in Rust owns the cadence and pushes a new snapshot every second by default; the interface never triggers a scan itself.

If the list is empty, that is a real answer rather than a failure: it means no process you own is currently classified as a running development service. Start a dev server, or flip the switch to System mode to see everything that is listening.

Reading the Overview

The LocalDocks Overview in Developer mode with four stat tiles, a running services list and the system telemetry section below.

Top to bottom, the Overview answers four questions.

  1. What is running? Four tiles: how many services, how many distinct listening ports, how many port conflicts, and how much memory those services use between them.
  2. On whose authority? The meta row states the active mode, the sampler interval, what the last tick cost, and how much of the machine the current mode is showing — 4 of 26 services rather than a bare 4.
  3. What are they? The RUNNING list, one row per service, with its port, process, PID, CPU and memory. Clicking a row opens the detail panel.
  4. What is the machine doing? Six telemetry cards, kept visually separate because they measure the whole machine rather than the services above.

Switching modes

The switch sits in the title bar because it changes every screen at once. Push it right for Developer, left for System. Arrow keys set a side rather than toggling, so holding one does not oscillate.

Your choice is remembered between launches, along with the theme and the sampler interval.

Finding what holds a port

The common task, end to end:

  1. Switch to System mode, so nothing is hidden.
  2. Open Ports and type the port number into the filter.
  3. Read the owning process and PID from the row. If LocalDocks could attribute the socket, the service name is there too.
  4. Click the row to open the detail panel, which shows the executable path and the full command line — usually enough to recognise what started it.
The LocalDocks Ports table filtered to loopback addresses, showing 38 of 101 sockets with port, protocol, address, PID, process and service columns.
Filtering the Ports table. Counts always read “N of M”, so a filtered view is never mistaken for the whole set.

Keyboard

KeyAction
Ctrl + KOpen the command palette. Covers services: show, open in browser, copy URL.
EscClose the command palette, the detail panel or a dialog.
← / →On the mode switch, select System or Developer directly.

Where to go next