Desktop: remote host mode — thin client for an existing dsh web deployment

[DZQZDK]

Use case

We run dsh web as a long-lived service on a Linux box (WSL2, managed by systemd). Sessions, skills, plugins, credentials and storage all live in that machine's $DSH_HOME, and headless automation (dsh CLI) runs against the same data. From our Windows workstations, the only client shape available today is a browser tab pointing at the web host.

What we'd love: the Desktop app's native experience (own window, tray, native file dialogs, auto-update) as a thin client to the existing host — backend stays on the server, zero local $DSH_HOME.

Current behavior

Desktop always boots its own bundled Host (Electron RunAsNode child from app.asar) and loads dsh-app://app/. We checked apps/desktop/src — there is no env/argv override to point the shell at a remote host URL.

Proposal

• A "Connect to existing host" option (welcome screen or app setting), or a launch flag like --host http://<host>:<port>
• Reuse the web host's existing auth (account sign-in / token admission)
• Shell loads the remote web app exactly like a browser client would; no local host, no local data writes
• Bonus: multiple saved hosts (e.g. dev + prod) in a host switcher

Why it matters

• Server-side deployments (always-on, multi-user, automation-heavy) get a first-class native client instead of a browser tab
• Hybrid setups (backend on Linux for sandboxing/NAS/toolchain, desktop on Win/macOS for daily driving) keep one source of truth for sessions and data
• Matches how many teams already deploy dsh web behind SSH tunnels or reverse proxies today

Environment

• dsh web v0.2.2-rc.1, source build, Node 24
• Workstations: Windows 11

---

中文摘要:桌面端目前只能自起本机 Host,没有连接已有远端 Host 的模式。希望增加 remote host mode:桌面壳作为瘦客户端连到服务器上长期运行的 dsh web(会话/数据/自动化都在服务端),本地不落 $DSH_HOME。这对「后端跑 Linux(沙箱/挂载/工具链),前端用 Windows/macOS 桌面 App」的混合部署是刚需,现在只能用浏览器顶。