dsh-remote-qr-button

The phone pairing QR code for a DSH WebUI desktop session lives on a separate local port served by the dsh-remote-link gateway, forcing users to pop open yet another browser tab just to scan it. Making matters worse, the Electron window blocks cross-origin iframe navigation, so simply embedding the gateway URL in an iframe results in a blank render.

DSH-QrPairing builds a same-origin bridge. The host registers two routes: a config probe that reads the gateway port, short code, and TTL in real time, and a PNG proxy that fetches the pairing image back into the same origin. When the floating button is clicked, the client requests the probe, renders the QR code, and polls every five seconds to keep the short code and countdown current. If dsh-remote-link is not installed, the overlay displays a clear "gateway not detected" notice instead of a dead link; on non-local addresses the button stays hidden entirely.

The button id matches the one injected by remote-link itself, so the two are mutually exclusive and whichever mounts first takes effect. The plugin only appears when the WebUI is accessed from 127.0.0.1 or localhost. It is built for developers who pair a DSH desktop session with a phone daily: one click and the code is right there, no tab-hopping required.