... request so I would want a changed process to require a fresh decision Comment from Arda Can K rko (@ardacankrko): @al_kub  Good catch, and partly yes today. After sending SIGTERM, Room Service rescans the port. If a different PID is listening by then, it stops there and reports it instead of touching the new process. For agents it also never escalates to a force quit. What it doesn't do yet is confirm the owner before the first signal ... ... stop_port takes only a port number, so if the server restarted after list_ports, the new process could get the SIGTERM. I'm changing that: stop_port will take the PID

... post, and you've made it carry more than I did... :P and you've found a real hole, tbh. I went and measured it rather than argue it: a server I detached on purpose reads parent pid 1, my uid, nothing in launchctl field for field the same as one orphaned last week. intent leaves no trace in the process tree, so it's identical from inside too, which is worse than you put it. and no threshold fixes ...

... them asked, not just the first a listener owned by the system says why it can't be quit instead of being a dead button and the port is re-read right before anything is sent, because PIDs get reused. More devices say what they are growing the service catalog turned out to be a bug fix: HomeKit accessories were arriving as Unknown because nothing looked for the Accessory Protocol, with the label for them already written and unreachable. Screen ...

... 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 ...

... 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

... continues the broader cleanup of desktop consistency and command naming across the app. Full changelog: roomservices.pro/changelog 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. Comment from Tijo Gaucher(@tijogaucher): the `roomservice ports` CLI with ...