dsh-remote-control

DSH’s web interface binds to loopback by default, so opening the panel from a phone or another workstation on the same network used to mean editing source code or spinning up an ad-hoc tunnel. dsh-remote-control collapses that into a single toggle in the settings panel: flip it on, the plugin auto-detects your LAN IPv4 addresses, renders a QR code carrying a one-time signed token, and a quick scan authorises the device. From then on the browser rides on a session cookie, so you scan once and are done. Turn the switch off and everything reverts to stock single-machine behaviour.

Security and edge-case compatibility are handled silently underneath. Unauthorised clients receive a 403 page (WebSocket handshakes are intercepted as well). Authorised devices are written to a persistent whitelist (capped at 32 entries, individually revocable at any time), so a dsh restart does not force re-scanning. The reverse proxy runs in a dedicated Node child process that rewrites Host and Origin headers to satisfy DSH’s browser-trust checks and injects a crypto.randomUUID polyfill for non-secure contexts. On Windows the plugin creates the inbound firewall rule automatically the first time you enable the feature, and the child process is terminated cleanly on uninstall.

It is built for developers who trust their local network and simply want to glance at the DSH panel from a phone, tablet, or second monitor without leaving the office or living room. Enable the toggle, scan the code, disable it when finished—three steps, no persistent extra service, and no changes to dsh’s own startup flags.