dsh-remote-access

The dsh WebUI intentionally listens on localhost only, so once dsh runs on a remote server you cannot open the management console from a public browser. Switching it to bind 0.0.0.0 manually would leave you exposed to unauthenticated access. dsh-remote-access steps in to close that gap: it makes the WebUI reachable over the public network while gating entry behind a password check, giving you remote access without weakening the original security posture.

The plugin is intentionally minimal. You configure a forwarding port and a access password, and a password-verified tunnel is established. The password is encrypted at rest in $DSH_HOME/settings.yaml so it never sits in plaintext. Configuration can be done through the Remote page in the DSH settings UI, or declared in a profile cordis.patch.yml file, or supplied via a --patch overlay, catering to both GUI-first and config-file-first workflows.

It is best suited for users who run dsh on cloud VMs or headless Linux boxes and want to check Agent sessions, tweak patches, or manage profiles from a laptop browser across the network. If you need something lighter than ngrok or Cloudflare Tunnel and prefer a solution that stays close to the dsh ecosystem, this plugin is a low-friction option.