localghost v3.2.0

Localghost 3.2 stops foreground runs from waiting silently behind a URL that cannot work, and fixes the most common cause outright: a dev server that binds only loopback, or lands on the wrong port, is now relayed to without exposing it to the LAN.

Upgrade

uvx --refresh localghost --version

Highlights

• Loopback dev servers just work. On a native Linux Docker daemon, an application bound only to 127.0.0.1 or [::1] — Vite's default, or any dev script that drops --host — is relayed to from the Docker gateway address alone. The hub reaches it; the LAN does not. Vite and Astro are no longer asked for --host 0.0.0.0 where the relay can stand in. Under tailnet hosting a relayed application is reachable by your tailnet, like every routed one.
• Wrong-port servers are caught. A dev script that drops --port leaves the server on its own default. The run relays the planned port to it when it can tell which listener is the application, and otherwise stops after 30 seconds with an error naming every address it is listening on.
• Busy ports are refused, and named. run no longer starts behind a port something else holds; on Linux the error names the process and its working directory. Ports are checked over both IPv4 and IPv6, and a port the run walks past is announced along with its holder.
• No silent spinner. The readiness probe sees IPv6-only servers, a loopback bind no longer counts as ready on its own, and the watching continues with --no-status-bar or piped output.
• Terminal fixes. The status bar no longer sends output back to the top of the screen over the run configuration, and ^C gets a line of its own before teardown messages.
• Tidier hub pages. The welcome page lists remembered projects as rows with type, directory and last start, and every hub page shares a footer with the dashboard and documentation links.

The full list is in CHANGELOG.md.