dsh-remote-dsh

Juggling DSH across multiple machines means constantly switching tabs, memorising URLs, and squinting at terminal output. dsh-remote-dsh adds a Remote row at the very top of the DSH sidebar; the moment you click it, the entire page becomes that remote host's DSH Web GUI - top bar, sidebar, session list, all of it belongs to the remote. No extra browser tab, no copying tokens around. A small status capsule at the end of the row keeps an eye on the remote for you: amber means a session is blocked waiting for your approval or reply, blue means something is actively running, green means a session finished a run since you last looked, and red means the peer on that side is not responding.

The status badge is powered by the same plugin running in peer mode on the controlled end. It publishes only anonymous session counts - no IDs, titles, or content - and requires no credentials of its own. Amber is the one state that will not clear just by looking: it is a blocker, not a notification. Open the remote view to see the pending approval or question, answer it, and the dot goes away. Colours and shape are borrowed directly from the remote's own sidebar status dots, so they look familiar rather than like a second, unrelated indicator.

There is one hard rule: the remote DSH must be reachable on a local loopback port (ssh -L, frpc stcp/xtcp + visitor, and the like). The session cookie is HttpOnly with SameSite=Strict, so a cross-site iframe gets an immediate 401. That constraint buys you zero configuration changes on the controlled end and no public domain requirement. Pairing is a one-time paste of the token printed by the remote's dsh web command; the cookie lasts 30 days by default and survives remote restarts, but the token is per-process, so a new process means a fresh pairing.

This plugin is for anyone running DSH on two or more machines who wants to hop between local and remote sessions in a single browser window and get at-a-glance awareness of whether a remote is idle, busy, or waiting on them. There is no build step - lib/ is the source, changes take effect on the fly - making it easy to tweak and extend.