Discussion

Search code, repositories, users, issues, pull requests...

Bradd3rs: love this, i get tired of spamming lsof -i tcp:xxxx

Doublon: The README made me realize I just needed a simple `alias local-tcp-listeners='lsof -iTCP -sTCP:LISTEN'` in my `~/.bash_aliases` :)

raskrebs: I always have a bunch of local projects running, particularly during the weekend where I'm rarely working on one thing at a time. A big pain of mine was constantly running into port: Redis from one project blocking another, orphaned dev servers from old worktrees, Docker containers I forgot about. The usual fix is lsof -iTCP | grep ..., then figuring out what the PID actually is, then killing it. But I always forget the command, and it doesn’t really include all the information that I like.So I built this lightweight CLI. Single binary, no dependencies. It shows everything listening on localhost with process names, Docker container info, clickable URLs etc.Sure there are workarounds, but none that satisfied my need for a short, easily rememberable command. Also nothing really has the same satisfaction as running sonar kill 3000 — it just feels nice. I’ve already been approached by a few agent orchestration tools that have been struggling with the same thing. It's really useful when you have multiple agents running, but it's not built for just that use case, I have also find it handy when killing off all containers after a failed cleanup and so on. Also know that MCPs are dead and CLIs are the new thing in agentic coding, this might be a useful tool for Claude, particularly when a compose process exits before all containers are stopped.Open for contributions, ideas and feedback.

pluc: Have a look at Evan Hahn's murder util: https://codeberg.org/EvanHahn/dotfiles/src/commit/843b9ee13d...

deadbabe: Same, not sure why a whole cli app is needed.

klaushardt: Would be nice to have a flag to customize the URL displayed for Docker containers. I connect to my host via Tailscale, but I can’t open links with localhost. It would be helpful to have a parameter that allows us to choose a network device or specify an IP address to display. 3000 wud (getwud/wud:latest) wud getwud/wud:latest 3000 http://localhost:3000 3001 dockhand (fnsys/dockhand:latest) dockhand fnsys/dockhand:latest 3000 http://localhost:3001

raskrebs: Developers are nitpicky, atleast i am and i know a lot of others that are as well. So don't underestimate the value of a nice tool with good developer experience, one that's intuitive, clean and easy to use means a lot when juggling so many things during a workday. So having a clean and light implementation to make job even easier is in my opinion worth it (and thus needed) :)

raskrebs: True, but as i write their are workarounds, the problem is that they are unintuitive, difficult to remember and don't provide all that much usability beyond listing. So these lack useful features like getting process stats, killing ports easily without having to remember the the pid after lsof and so on. I often have to kill multiple process at once after a failed cleanup. If you are into agentic coding, then having your agent create a profile for all the processes it stats, which it can easily kill of when finished is a lot easier for me atleast.Some features on the way are: next available port; wait (wait for a host to return a successful health check before proceeding - good for migrations etc.). And lots more. It's not just about listing running ports, but a tool for managing them.But to each their own, that's what's lovely about the many options available. But if you have anything in relation to this you think is neat, feel free to open an issue. It may be able to convince you that a simple alias won't suffice.

frankdenbow: love this, happens too often

moezd: Sonar as in SonarQube? That's an interesting choice for a name :)

chwzr: i have this in my .zshrc which provides same functionality: lk() { if [ $# -eq 0 ]; then local output=$(sudo lsof -iTCP -sTCP:LISTEN -n -P) elif [ $# -eq 1 ]; then local output=$(sudo lsof -iTCP -sTCP:LISTEN -n -P | grep -i --color=always $1) else echo "find and kill processes listening on ports. Usage: lk [pattern]" return 1 fi if [ -z "$output" ]; then echo "No listening processes found." return 0 fi # Show header + results echo "$(sudo lsof -iTCP -sTCP:LISTEN -n -P | head -1)" echo "$output" echo "" # Extract unique PIDs (skip the header row if no grep was applied) local pids=($(echo "$output" | awk '{print $2}' | grep -E '^[0-9]+$' | sort -u)) if [ ${#pids[@]} -eq 0 ]; then echo "No PIDs found." return 0 fi echo "PIDs to kill: ${pids[*]}" echo -n "Kill these ${#pids[@]} process(es)? [y/N] " read -r confirm if [[ "$confirm" =~ ^[Yy]$ ]]; then for pid in "${pids[@]}"; do echo "Killing PID $pid..." sudo kill -9 $pid done echo "Done." else echo "Aborted." fi }

raskrebs: Good point. Could you add an issue, then i'll have a chance to look into it :)https://github.com/RasKrebs/sonar/issues

mfkrause: I always find myself going through my zsh history for `lsof`. Will definitely check this out, seems interesting (even though I'm generally reluctant of installing third-party tools for such jobs).

clutchski: Mine is called “porthole”https://github.com/clutchski/dotfiles/blob/main/home/bin/por...

raskrebs: Any features you are missing or ideas for the use case?

raskrebs: Exactly, really hates it as well. Please post any issues you may have

raskrebs: I think a cli tool that detects objects beneath the surface is a pretty intuitive name, but i was also reluctant in the beginning. But they are pretty keen on always using the qube part, i believe theirs is sonar-qube.