dshapp/dsh-mobile-bridge

dsh-mobile-bridge serves a harness's /api to paired phones over a Noise-encrypted tunnel to a public dsh-proxy: it opens no port, writes no state file, runs no extra process and forges no cookie, authenticates by the Noise_IK handshake (the device's static key is its device id), default-denies exact plugin routes while opening the RPC channel, and refuses its own control plane, so the proxy copies bytes from a 37-byte routing preamble it cannot decrypt.

dsh-mobile-bridge serves a DeepSeek Harness server's /api to paired phones over a Noise-encrypted tunnel to a public dsh-proxy, so a phone can reach the harness without the harness opening a port. It is a cordis plugin that lives and dies with dsh server: it opens no port, writes no state file, runs no extra process and forges no cookie. End-to-end Noise_IK runs between the phone and this plugin, so the intermediate proxy only relays bytes it cannot read. Access is gated twice - by the handshake, which establishes identity, and by an allowlist, which limits what a given device may call - and the bridge's own control plane is refused outright, keeping the phone's reach to the routes it actually needs.

Infrastructure & Deployment ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add dsh-mobile-bridge

Copied verbatim from the README's Install block.

Compatibility

Authentication is the handshake: Noise_IK proves the device's static key (that key is the device id) and proves us to the device, and a device that is neither whitelisted nor carrying a live pairing token is dropped before any harness traffic is served, with a stalled handshake dropped after handshakeTimeoutMs. A phone reaches only what it needs - the handshake says who is calling while an allowlist decides what they may call, exact plugin routes are default-deny, the RPC channel /api/<namespace>/<method> is open and the bridge's own control plane is refused outright. The public proxy reads a 37-byte routing preamble and copies bytes, cannot decrypt and stores nothing on disk; the routing key is in the pairing QR code and is an identifier, not a secret. Config takes proxyHost, proxyPort, an optional pinned proxyPublicKey, deviceTtlDays, handshakeTimeoutMs and an apiAllowlist that extends rather than replaces the defaults (/api/file, /api/session/uploadFileBinary, /api/remote.mux, /api/changes.summary, /api/changes.diff).

Details

Alternatives

1m01m0/deepseek-harness-desktop · AIcivilization/dsh-vps-manager · AlliotTech/deepseek-harness-docker

More plugins in Infrastructure & Deployment

Browse more in Infrastructure & Deployment

Guides for Infrastructure & Deployment plugins