... started A test run finishes, you close the terminal, and something it started is still holding port 3000. Netfox couldn't see it not because it wasn't looking hard enough, but because a server bound to the loopback address isn't on your network at all. It listens to your Mac and nothing else, so no network scan was ever going to find it. 0.20.0 looks in the other direction and tells you when one has been left behind ...

... says so and counts those networks toward congestion, since spectrum doesn't care whether a name is published. And: free a port on your Mac, no terminal Local Services every port your Mac is listening on, including the loopback-only ones Netfox already showed you that something was holding 3000. Now each row can ask that process to quit politely first, so a dev server saves what it was holding; force only offered if it ignores that. Three details that ...

... Small release, but it fixes something that was quietly making a whole column useless. If your Mac's hosts file has a line like 127.0.0.1 shop.local, Local Services was showing shop.local next to every local port that answers on loopback Raycast, Google Drive, mysqld, all of them. Every line was true. Not one of them told you anything. A hosts name points at an ADDRESS, not at a service. So now it is said once, above the group: "On this ... ... 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

... error. Cross-Origin-Opener-Policy: same-origin quietly severs window.opener, so a popup callback completes and the parent never hears about it. Google validates redirect_uri strictly enough that a hosted callback is rejected outright, so the loopback URL has to be copied back by hand. There's a live demo where you can sign in with your own account and chat. The docs and the code are both public, and the launch is here . Happy to go into ...

... asks the system directly, then splits the answer in two: The Local Services tab: this Mac's listening ports, split into the ones only it can reach and the ones the network can Only on this Mac bound to loopback. Nothing else on your network can reach them. Dev servers, database engines, helper tools. Reachable from the network anything on your Wi-Fi can connect. Usually intended. Occasionally a surprise. And names instead of numbers. 3000 tells you nothing. shop.local:3000 ... ... that way: The Ports tab on a network device, grouped by category Also fixed: a closed port now says closed. A port that actively refuses a connection was being reported as filtered and those mean different things. Nothing listening, versus

... hosts-file alias appeared on seventeen rows of a list the same name beside a Raycast helper, beside Google Drive, beside a database. Every line was true. The name really does reach all of them, because it names the loopback address and they all listen there. No line to blame, exactly as you put it: each row individually correct, the set implying a relationship that doesn't exist. And the fix landed on the shape you describe. The test pinning ... ... asserts a property of the whole that every loopback

... just shipped v1.6.0 for Windows . This one is focused on making it easier to connect, especially for in-car use. Hotspot Without Internet A new "Hotspot with loopback interface" mode lets your PC broadcast a hotspot even when it has no internet connection. Great for Tesla setups where you just want to extend your display without needing to tether your phone. Connection Mode Selector Three connection modes to choose from: Same network, Hotspot with internet, or Hotspot with loopback

... been away. Faster, by a lot Spawning a Claude agent on macOS used to stall for ~23 seconds when more than one came up at once. We moved the PTY off Tauri's IPC channel onto a loopback socket, so now ten agents start near-instantly. Windows got its own overhaul in 0.25.0. The "Not Responding" freezes when you opened several projects or switched branches are gone, because every git and filesystem call now runs off the UI thread. Large ... ... batch your agent runs and dread spinning up a new one. Near-instant means you just do it, ten times a day, without thinking. The fix was moving the PTY off Tauri's IPC onto a loopback