A Port Number Is Not an Identity

Description and use

Dev Server Activity helps macOS users quickly identify running local servers and safely terminate them, avoiding accidental process kills.

Problem

Developers often have multiple local development servers running simultaneously and cannot easily identify which project owns which listening port, leading to uncertainty about whether to stop a process.

Outcome

The app reduces friction in managing local servers, prevents accidental termination of unrelated processes, and encourages safe shutdown practices.

Workflow

• Scan system for listening sockets owned by current user
• Group sockets by process and identify likely dev server types (Node.js, Vite, Next.js, Python, Ruby, PHP, Bun, Deno)
• Display each process with project folder, command line, PID, and listening ports
• When user selects stop or force stop, re‑read current command line and listening sockets
• Validate that the process still matches the original scan and owns expected ports
• If validation passes, send SIGTERM (stop) or SIGKILL (force stop); otherwise refresh list and do nothing

Evidence

The app looks for likely local development servers owned by the current user, groups listening sockets by process, and shows the process context beside the stop controls.

Source

Immediately before sending either SIGTERM or SIGKILL, Dev Server Activity checks the target again…

Source