witr CLI
witr identifies the process holding a port or file and shows its startup chain, supervising service or container context.
- 22,941 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- witr reads system and process details; its interactive actions can control selected processes.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/pranshuparmar/witr/main/install.sh | bashFirst Quick Install method for Linux, macOS and FreeBSD. Review the script before executing it.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- witr reads system and process details; its interactive actions can control selected processes.
This is third-party code. Review the repository files before installing.
What it does
witr traces a process to its launch source. Supply a name, PID, port, container or open file to get ancestry and service context. An agent can see what keeps it running before proposing a stop. Results are available as human-readable reports or JSON. With no target, an interactive process and port dashboard opens. An official agent skill explains exit codes and calls for approval before stopping programs.
Who it is for. On-call engineers investigating occupied ports or processes that keep reappearing.
Good fit when
- A development server cannot start because its port is occupied.
- A stopped process reappears and its supervisor must be identified.
- An open file blocks work and its owning process is unknown.
- An agent needs a structured container and startup-chain report.
Not a fit when
- You want to stop another user’s service without identifying ownership.
- You need long-term metrics without a monitoring system.
- You expect identical process visibility on every operating system.
Example request
Use witr to identify port 8080’s owner and startup source. Show JSON without environment variables and stop nothing.Limitations
Inspecting other users’ processes may require elevated privileges, and macOS SIP can still hide details. Container inspection needs the relevant runtime CLI on PATH. Platform features differ; Windows lacks file-lock views and interactive process actions. Environment-variable output may reveal sensitive values, so choose only necessary fields before sharing a complete report with an agent or colleague.
How to disable. Exit the interactive view and uninstall witr using the original method. Remove the agent skill separately if installed.
FAQ
How do I inspect a port?
Run `witr --port 8080 --json` with the desired port and inspect the process and launch source.
Does exit code 1 mean failure?
No. The process was found with warnings. Read them before acting.
What if a name is ambiguous?
Identify the PID and retry with `--pid` to avoid selecting the wrong process.
Why does a targetless CI run fail?
The dashboard needs a terminal. Supply a process, port or other target; `--json` alone is insufficient.
Does the skill install the binary?
No. Install witr separately; the skill guides command selection and result interpretation.
Discussion
No questions or reviews yet.
Related
CLI toolsSearchable processes and configurable columns help locate CPU load, listening ports and child commands from a terminal.
Terminal diagnostics combine traceroute and ping so agents can compare routes, latency and missing probe responses.
bottom displays processes, CPU load, memory, network and disks in the terminal with graphs, search and configurable widgets.
PM2 is a process manager that saves background app lists for restart after reboot and displays their status in the terminal.
The terminal interface presents Docker containers, services and images for user-led investigation with agent assistance.
A native macOS terminal built on Ghostty with vertical tabs and notifications when an agent needs your input
README in short
witr supports Linux, macOS, Windows and FreeBSD. Multiple target types can share a request and retain input order in the report.