pranshuparmar

Quick update: witr now supports Linux, macOS, Windows, and FreeBSD.

Thank you, mac is already supported, only with the very first release it wasn't. You can install it via brew.

Just to update, witr is currently available on brew and AUR. deb, rpm and apk packages are also available in the release, and can be run directly via nix without installation.

Thanks a lot for the input, I ended up using it.

Haha, go for it!

Not sure if you're the one who created it but the AUR for this is present and needs update for the latest version - https://aur.archlinux.org/packages/witr-bin

Totally. Just to clarify, witr isn’t limited to ports. You can run it directly on a process too, like `witr mysql`. I used the 3306 example to emphasize this use case.

Quick update, witr now supports macOS as well. You can install it using brew - https://github.com/pranshuparmar/witr?tab=readme-ov-file#81-...

Thanks! Funny enough, that was my thought too when creating it.

Thank you, please feel free to share any feedback/ideas.

Thank you, please feel free to share any feedback/ideas.

Thanks for the feedback! I’ll look into showing who and why in a more distinct way. The default output is human-first, hence some extra line breaks, but the JSON flag is already there for automation. We can also see if it can be made more easily greppable.

Thank you.

Thank you, please feel free to share any feedback/ideas.

Thank you.

`witr` is trying to be a bit different. Here are few use cases to consider: - When a process started. - Which ports a process is using. - Which user started it. - From which directory it started. - env flag to list all the variables attached to the process. - json flag to use it programmatically.

Yes, this is a bug. Planning to fix it soon.

Thank you, yes I added it in jest and still keeping it for sometime. It was always meant to be removed in future.

Haha, glad you like it! Maybe "responsibility chain" will catch on.

Thank you, yes coming soon - https://github.com/pranshuparmar/witr/pull/9

Thanks! Really appreciate it. No qualms at all — an AUR entry would be awesome!

Thanks! Glad you like it Trying to make this a swiss army knife for PID information.

Yes, that's correct! It walks up from the process’s working directory looking for a `.git` folder to detect the repo and branch. Thanks.

Thanks! Glad you like it Thanks to @sestep, Nix support is already added, so no need to worry about binaries.

Thank you, glad you liked it. Since this is the first release, I intentionally kept it simple. Now that the tool is gaining some traction, I can definitely plan proper packages for future releases. Thanks for your inputs.

Fair enough! That line was meant tongue‑in‑cheek, and to be transparent about LLM usage. Rest assured, they were assistants, not authorities.

I understand that installing via `curl` isn’t for everyone, but since this is the first release, I intentionally kept it simple. Now that the tool is gaining some traction, I can definitely plan proper packages for future releases. Thanks for your inputs.

Thanks, glad you liked it! As @darrenf mentioned, `whatis` can help with that use case. For now, I’m keeping `witr` focused on explaining PIDs.

Thanks everyone for the feedback on the GIF! I though it looked good but when I went back to see it from a user's POV, it was really miserable, haha. I've already switched it to a static image, appreaciate everyone's input and suggestions.

A quick note on scope: this is not meant to replace existing monitoring or observability tools. It’s designed for those moments when you SSH into a box and need to quickly understand “why is this running” without digging through configs, cron jobs, or service trees manually.

Happy to answer questions or adjust direction based on feedback.