portnannylisted

# Freeing ports with PortNanny Never run `kill -9 $(lsof -ti:PORT)`: other AI agents may be using that port, and PortNanny knows who owns what. - `portnanny free <port>` frees the port (SIGTERM, verified; exit 0 if it was already free). `portnanny kill <port> --dry-run --json` shows what would happen first. - Exit code 3 means the port belongs to another agent's running session, to nobody PortNanny can name (most likely a person's server), or someone holds a lease on it. The refusal is on stderr. Do not retry with `--force`; tell the user, or pick another port. "Another Claude Code session" is still another session: it is not you. - Exit code 6 means a supervisor (pm2, launchd, Docker, a reloader such as nodemon) would undo a plain kill and its tool is not on PATH; stderr names the command to run instead. - `portnanny exec --free-port --prefer 3000 -- npm run dev` picks a free port, exports PORT, leases the port for the run, and attributes the server to you. `portnanny reserve <port> --for 10m` leases a port you are about to use by hand; `portnanny release <port>` gives it back. - `portnanny free-port --prefer 3000` prints the first free port nobody has leased. - `portnanny whois <port>` explains who started a server and why PortNanny thinks so, and what `kill` would do for you. - `portnanny drift` lists servers running off the port their project's .env, package.json, or vite.config names, and who holds that port. - `portnanny kill --orphaned` st