dsh-lan-uuid-fix

Accessing the DeepSeek Harness Web UI over a plain-HTTP LAN address (say http://192.168.1.66:3080) hits a subtle browser quirk: crypto.randomUUID is only exposed in secure contexts — HTTPS or loopback origins. On an insecure LAN origin the API is undefined, so the web client mintRpcId throws a TypeError, every unary RPC fails, WebSocket streams die mid-handshake, the console loops connection lost, retry #N, and the workspace browser is stuck on No sessions yet forever.

dsh-lan-uuid-fix takes the straightforward route: crypto.getRandomValues is available even on insecure origins, so the plugin injects a small inline polyfill into every served index.html that backfills crypto.randomUUID with a v4 implementation built on getRandomValues. It hooks in through a host plugin registered on ctx.webServer html-transform, runs before any app bundle executes, and only activates when the native API is absent — loopback and HTTPS pages are left completely untouched. The patch is applied live via HMR, so a running dsh web picks it up without a restart; a hard refresh on the remote client is all you need.

If you connect to dsh web through a LAN IP in the office or at home and would rather avoid spinning up TLS certificates or an Nginx reverse proxy just for one UUID call, this plugin is the lowest-friction fix. After installing, the workspace browser lists your existing sessions normally, the retry spam in the console disappears, and the LAN experience feels identical to local 127.0.0.1.