I've got a design background, started building a lot more lately, couldn't stand how opaque the process is to see what ports are occupied and what local servers are running. So I built WhatThePort.
It shows you:
- what local servers are running
- how long they've been running
- their resource use
- notifies you if one spikes
- auto-kill old servers (opt-in)
- give easy ways to launch the local urls
- add shortcuts to my Vercel preview url, or Codex/CCode sessions that created it, and shortcuts to resume in my terminal of choice
- has charts to see spikes
- allows you to resume sessions in the terminal
- auto-tags stale servers if your workspace is cold
- and more.
Also added a TUI for it today since I know many devs will prefer having access to it.
tomjohndesign•55m ago
I've got a design background, started building a lot more lately, couldn't stand how opaque the process is to see what ports are occupied and what local servers are running. So I built WhatThePort.
It shows you:
- what local servers are running - how long they've been running - their resource use - notifies you if one spikes - auto-kill old servers (opt-in) - give easy ways to launch the local urls - add shortcuts to my Vercel preview url, or Codex/CCode sessions that created it, and shortcuts to resume in my terminal of choice - has charts to see spikes - allows you to resume sessions in the terminal - auto-tags stale servers if your workspace is cold - and more.
Also added a TUI for it today since I know many devs will prefer having access to it.
Enjoy, share feedback.