ddtcorex/dsh-maestro-remote ↗★ 1
@ddtcorex/dsh-maestro-remote
Maestro remote — tunnel + remote-proxy + PIN + QR for DeepSeek Harness 适合需要从外网安全访问本地DSH服务,并进行PIN码验证的用户。
インストール
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:ddtcorex/dsh-maestro-remoteドキュメント
README 全文を読む ↗@ddtcorex/dsh-maestro-remote
Remote access plugin for the DeepSeek Harness: a Cloudflare tunnel (quick or named) plus a LAN remote proxy so a DSH session can be reached from outside the machine, gated by a second PIN with QR provisioning.
Part of the Maestro Harness suite (dsh-maestro-*). Three Cordis patch rows:
dsh-maestro-remote-rpc (loopback RPC), dsh-maestro-tunnel (the tunnel and LAN proxy provider)
and maestro-patch (the zero-fork patch shim absorbed from dsh-maestro-patch).
What it provides
- Tunnel lifecycle (
maestroTunnelservice): start/stop/status of a cloudflared quick tunnel or a named tunnel with a single ingress to the PIN-gated remote proxy, which exempts/hooks/gitlab-mrand/hooks/gitlab-mr/triggerfrom the PIN so GitLab can post webhooks; auto-restore of a previously running named tunnel on boot. - Remote proxy: request handler for the tunnel target with PIN auth (constant-time comparison), reloadable config.
- cloudflared fetcher: resolves the binary from PATH or installs it into a cache dir.
Settings
Config persists through the embedded settings store: a committed, hash-sealed copy of
dsh-maestro-core's store (src/host/vendor/store.ts), reading and writing the shared
namespaced document ~/.dsh/dsh-maestro-config/settings.json through a flat
MaestroUserConfig adapter, see src/host/config-store.ts. This package does not depend on a
published settings library. Machine runtime state
(lastTunnelRunning) deliberately lives in this package's own sidecar
(~/.dsh/dsh-maestro-remote/runtime.json) so editing settings can never silently flip
tunnel state.
Requirements
- Node.js
^22.19.0 || >=24.0.0and pnpm 11+. A shell that defaults to Node 20 fails withNo such built-in module: node:sqlite; put a Node 22binfirst onPATHbefore runningdshorpnpm. - DSH 0.1.x or 0.2.x (peer range ``.
Installed with link: from a checkout? After every git pull, run pnpm install && pnpm build
(lib/ is gitignored) and restart dsh web.
Putting the PIN in front of a tunnel
The proxy listens on port 3081 by default (proxyPort in the settings store; it walks up
to 9 ports if that one is busy). A named tunnel whose ingress still points at the raw
dsh web port bypasses the PIN, so point the tunnel service: at the proxy port instead.
The 8-digit PIN lives in ~/.dsh/dsh-maestro-remote/pin (created on first use); rotate it
from Settings > Maestro Remote. The PIN cookie lifetime is pinSessionTtlHours.
Development
pnpm install
pnpm verify # tsc --noEmit
pnpm test # vitest run
pnpm build # tsc host + tsc client + esbuild bundle -> lib/ and lib/client.js
A tunnel change must be validated live (real start/stop + proxy round-trip), not just by unit tests — see AGENTS.md.
License
MIT