dsh-coding-remote-kit

DeepSeek Harness ships without a first-class phone companion, and the usual community workaround — mirroring the entire Web UI into a mobile browser — means publishing a wide, unauthenticated API surface on top of whatever link the phone is on. dsh-coding-remote-kit takes a more disciplined route: after a one-time QR-scan or PIN pairing, the phone receives only a narrow, end-to-end-encrypted data channel. The management plane stays locked to the desktop loopback, unauthenticated sockets never touch session content, and every write is constrained to an explicit RPC allowlist — observe a session, answer an approval prompt, send a short reply, or cancel a run; everything else is refused. Heavy editing remains on the desktop. The data-plane port binds to the LAN by default; an optional Cloudflare Quick Tunnel forwards only the /m data endpoint and never port 3080, and an opt-in self-hosted rendezvous Worker lets both sides connect outbound while business frames stay end-to-end encrypted.

It is a good fit for developers who want to glance at DSH session progress between meetings, tap approve on a pending question, or nudge a stalled response without opening a laptop — especially in team LAN or Tailscale environments where publishing the full Web admin UI to the public internet is off the table, while pulling out a single minimal encrypted data channel hits the sweet spot. The plugin follows the standard Cordis shape, pairs once and survives restarts, cleans up fully on unload, and remains completely independent of the @deepseek-ai/dsh core.