dsh-maestro-remote

A DSH session is tied to the terminal it was launched in, so walking away from that machine means losing the thread. dsh-maestro-remote bridges that gap with a Cloudflare tunnel and a LAN remote proxy, surfacing your local DSH session to the outside world so you can pick up right where you left off.

The core capabilities fall into three buckets: tunnel lifecycle management (start, stop, and status for both quick and named cloudflared tunnels, plus automatic restore of a previously running named tunnel on boot); a remote proxy request handler that enforces PIN authentication via constant-time comparison and supports hot-reloadable configuration; and a cloudflared binary fetcher that resolves the executable from PATH or installs it into a cache directory automatically. Access is gated by a dual-PIN scheme with QR-based provisioning, keeping secrets out of URLs and request headers.

It is built for developers and small teams already working within the Maestro suite who need to keep operating a local DSH session from another location—say a long-running job at home while you are at the office, or turning a dev box into a shared remote terminal. Configuration and runtime state are deliberately stored separately so that a casual edit to settings.json can never silently flip the tunnel on or off.