proc
Semantic CLI tool to manage processes by port, PID, name, or path.
Tested on Linux
Use it
Linux x86_64
install proc via npm
npm install -g proc-clifirst run downloads verified binary
proc --version
Check that it works
proc --versionThe output should contain “proc”.
First thing to try
python3 -m http.server 3000proc on :3000Run proc on :<port> to see which process is using a port.
What it does
- Find which process is using a portTested
How to use it
- Run
proc on :<port>to see the process using that port.
- Run
- Kill processes by port, name, or other targetsTested
How to use it
- Run
proc kill :<port> :<port> <name> --yesto kill all matching processes at once.
- Run
- See why a port is busy and trace its process ancestryTested
How to use it
- Run
proc why :<port>to show the process using the port and its parent chain.
- Run
- Watch processes in real timeTested
How to use it
- Run
proc watch -n 1to refresh the process list every second.
- Run
How far pickfit got
Linux x86_64
- Installs
- Starts
- 4 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- find what process is using port 3000
- kill process using port 3000
- find processes running a program file
- list node processes in current directory
- free a busy port and verify it is free
An alternative to lsof.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 2.0.2
Differences the test machine hit
- README: npm install -g proc-cli
In the test: first proc invocation downloads the Linux binary to ~/.local/lib/node_modules/proc-cli/proc and verifies checksum (requires network) - README: proc kill :3000 :8080 node
In the test: append --yes (proc kill :3000 :8080 node --yes) when stdin is not a terminal, otherwise exit 4 needs_confirmation and nothing is killed