... client logins Anyone who's tired of the login-logout dance What you can do Launch an isolated browser for any URL in one click Name each profile and reuse the same login state anytime Watch live status: running, PID, start time Restart, stop, or delete any process even all at once Everything persists, so your setup reloads on next start How it works A tiny local backend (Python + Flask) starts each Chrome window with its own independent profile directory ...

... listener, with a count of how many processes sit behind it, and each row keeps the full process name (not truncated to nine characters the way the usual command-line tools do it) plus the pid. What the rows are grouped by today is reach, not process: loopback-only on one side, anything reachable from the network on the other. That's deliberate, because it's the axis that answers the question the panel exists for did I leave something ...

... health issue is resolved, the suggestion should not keep routing you back to an outdated view. If a server or watcher is stopped, the app should verify what actually happened instead of assuming the process is gone. If a PID or port is reused, the tool should not accidentally act on the wrong thing. The bigger idea is simple: developer utilities should not just detect problems. They should keep their understanding of the machine fresh. Curious how other makers handle ... ... will ignore all of them. At this point, the system will have conditioned you to disregard all of its warnings, which is not at all what you would want from a security tool. The example you gave of PID

... rigging with lsof + awk way too often. does it show which process started each listener too? Comment from Arda Can K rko (@ardacankrko): @tijogaucher  haha yeah, the CLI is kind of a sleeper feature here it shows the pid and process name, and when we can resolve it reliably, the project path too. the whole point was to avoid having to do the usual `lsof` + `awk` dance every time ...