AI Agent Hub
Back to plugins
🖥️

dsh-mobile-access

Client Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install kk99668/dsh-mobile-access

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install kk99668/dsh-mobile-access in DeepSeek Harness to install this plugin; full source is available at https://github.com/kk99668/dsh-mobile-access

About this plugin

The DSH web GUI listens on localhost by default. Want to check agent status or send a command from your phone during a subway commute, yet have no safe way to surface a local service to the internet -- third-party tunnels hand your traffic to someone else, while opening a port naked exposes the configuration plane. dsh-mobile-access closes that gap.

It starts a token gate as the sole authentication boundary, then opens a supervised ssh -N -R reverse tunnel that plugs the web server into Caddy behind your own domain. The tunnel reconnects with exponential backoff on every drop; WebSocket event streams negotiate permessage-deflate compression, and the browser client retries at 500 ms doubling to a 10 s cap, so a flaky signal does not blank the UI. Once the tunnel is up, the terminal prints the public URL and an optional QR code -- scan it and the GUI is on your phone, with no device registry to maintain.

Built for users who own a domain and have a reachable VPS, and who want the full chain on their own HTTPS without touching a third-party relay. A single script provisions Caddy and a restricted SSH user on the relay side; privileged configuration-plane methods stay pinned to loopback and are never reachable through the tunnel.

Use Cases

  • Check agent status and send commands from a phone browser during a subway commute
  • Reach the local DSH web GUI via your own domain when the field signal is flaky
  • Avoid third-party relays by keeping the entire chain behind your own Caddy TLS

Best For

  • Developers who own a domain and a reachable VPS and want to self-manage the full chain
  • Users who distrust third-party relays and want all traffic through their own DNS and TLS
  • Ops or developers needing secure mobile access to a local agent without a device-registry service