dsh-relay-phone
Verifieddsh-relay-phone Β· v0.18.0 Β· Apache-2.0 Β· Web UI
Remote-control your local DeepSeek Harness from a phone through your own zero-knowledge relay: phone-first page, QR pairing, end-to-end encryption, approvals, full desktop UI fallback.
Install
dsh plugin add dsh-relay-phone Confirm the layer applied with dsh --profile default --dump-config β see the install guide.
Source
Tags
Creators
Readme
dsh-relay-phone
DSH plugin that makes your local DeepSeek Harness reachable from your phone through a relay you host yourself.
It owns the device identity, the outbound connection to dsh-relay-server, the pairing handshake, the encryption layer, and a phone-first page for chatting with the agent and answering its approvals.
Part of dsh-relay. Read the main README for the architecture, security model and deployment steps.
Try it without running a relay: https://dshrelay.com:8443/ hands out a free 50 MB/day key (10 a day, resets at 00:00 UTC). Self-hosting is free too β that is what the rest of this repository is for.
Install
From the desktop app (no terminal): Plugins page β Add plugin β type
dsh-relay-phone β Enter β Enable now β restart DSH when it asks.
From a terminal:
dsh plugin --profile web add dsh-relay-phone
From a checkout of the repository, point at the package instead:
dsh plugin --profile web add link:./packages/plugin
Restart dsh web afterwards (the plugin is host-side code). Configure it from the sidebar's Phone Entry card β Open console; in the desktop app that navigates inside the window, so the port does not matter. Through the relay only the phone page and the documents/assets it loads are plaintext; every
other request must carry a sealed envelope or it is refused with 403. A relay that could forward
plaintext /api/* with the host cookie attached would be able to act as you, which would make the
end-to-end encryption decorative. The desktop UI works under that policy, because the injected boot patch seals its fetch/XHR/WebSocket traffic (a WebSocket handshake carries no data; its frames must open). { "allowDesktopPlaintext": true } remains for clients that bypass the patch.
The panel is deliberately desktop-only: it prints the pairing link, which carries the device key, so requests that arrive through the relay are refused.
Configuration
Saved by the panel to ~/.dsh/plugin-data/dsh-relay-phone/config.json, which overrides the defaults in cordis.patch.yml:
| Key | Meaning |
|---|---|
relayScheme |
http or https |
relayHost, relayPort |
Relay address for phones |
agentPort |
Relay port for agent connections |
relayKey |
The key this deployment was given: a tenant key from dsh-relay-server tenant add, or the server's admin --key |
autoStart |
Connect on startup (default true) |
A paired phone opens the mobile page; the full desktop UI stays reachable at /c/<id>/?desktop=1 (or the drawer's "Open full desktop UI"), which is also how the entry link works in a desktop browser.
Tests
npm test # hermetic: no relay, no dsh web, no network
npm run check # syntax check every source file
npm run test:ui # CDP-driven UI test against the mock host (needs Chrome)
License
Apache-2.0