Proc-CLI：面向智能体与脚本的语义化进程与端口管理工具

Target processes by port, PID, name or path.

proc is a semantic CLI tool for process management on macOS, Linux and Windows. Find what's on a port, why it's there, and stop it, in one command you'd guess on the first try.

~proc kill :3000

Ends whatever is listening on port 3000 immediately (SIGKILL). Asks first, and --dry-run previews.

A leading colon means a port: proc acts on whatever is listening on it.

Command

Target

A dev server won't start because port 3000 is taken. proc finds the old tmux session holding it, frees the port, then cleans up what else was left running.

One command instead of a pipeline

The same jobs, without remembering which flags lsof needs or piping PIDs into kill.

What's on port 3000?lsof -i :3000 -P -nproc on :3000

Why is it there?lsof -i :3000, then ps -o ppid= up the chainproc why :3000

Free the portlsof -t -i:3000 | xargs kill && sleep 1 && lsof -i:3000proc free :3000

Wait for it to exitwhile ps aux | grep node | grep -v grep; do sleep 5; doneproc wait node

Pause a processkill -STOP $(pgrep node)proc freeze node

Find leftoversNo standard toolproc orphans --in .

Nineteen commands, three jobs

Every command takes the same targets, and almost all take --in to stay inside one project, --json for scripts, and --dry-run before anything changes.

All commands and options

Made for scripts and coding agents

Every command prints one JSON document with --json, and exit codes always mean the same thing. An agent can read proc the way you do, without parsing tables.

0 success, 1 error, 2 not found, 3 permission denied, 4 invalid input
--dry-run shows what would be touched, and nothing else
The agent skill teaches Claude Code, Codex, Cursor, Gemini CLI and others when to reach for proc

❯ proc on :8080 --json | jq '.process | {pid, cwd, uptime_secs}'
{
  "pid": 177,
  "cwd": "/home/dev/code/shop",
  "uptime_secs": 35
}

Posts

All posts