Back to directory

deepseek-harness-relay

In a curated listMaintenance: Active

sorsama/deepseek-harness-relay

Authenticated remote access for a DeepSeek Harness web profile: TLS, QR/passcode device pairing, password sign-in, and per-device revocation in front of an untouched loopback harness.

View on GitHubHomepage
$ dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay

17

stars

6

forks

TypeScript

Language

MIT

License

2026-08-21

Created

2026-11-09

Last push

MIT TypeScript plugin that fronts an untouched loopback DeepSeek Harness with HTTPS, password sign-in and QR / 8-digit-code device pairing — plus mDNS discovery, per-device revocation and one-click linking between two computers.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-16

License

MIT

01What can it help you accomplish?

  • Reach the harness from a phone or another computer without opening it to the whole Wi-Fi

    TLS on the relay port plus a password check and device pairing in front of a harness that stays on 127.0.0.1 — and when the relay dies the harness is unreachable rather than exposed

    Anyone running the harness web profile on a laptop or desktop who wants it on a phone or tablet on the same network (or forwarded from outside) without binding it to 0.0.0.0

  • Pair devices one by one and cut any of them off later

    A named device under `/relay/devices` holding its own token, per-device revocation, and a sign-out-everywhere button that rotates the signing key

    People who share one relay with a phone, a tablet and a second computer and want each of them revocable on its own

  • Link two computers so either one opens the other's harness in one click

    The pair listed on both Computers pages, and **Open** handing this browser a one-time sign-in on the other computer with no password to retype

    Developers with a desktop and a laptop both running dsh-relay, working in a browser rather than the desktop app

02How to install into DeepSeek Harness

Prerequisites

  • DeepSeek Harness with the web profile — the relay is a plugin for that profile, and the desktop app runs the same profile
  • The harness still on loopback: delete the row in `~/.dsh/profiles/web/cordis.patch.yml` that binds it to `0.0.0.0`, because the relay won't start in front of a harness already open to the network
  • `dsh` on your PATH, or run every command as `npx @deepseek-ai/dsh ...`
  • A relay build that matches the harness — 0.3 for harness 0.1.7-rc.2 through 0.2.x

Installation steps

  1. 01

    In the harness: **Plugins** in the sidebar → **Add plugin** → paste `https://github.com/sorsama/deepseek-harness-relay` → **Install**

  2. 02

    When pnpm asks about the git package's build script, choose **Allow these scripts and retry**; when the build finishes, choose **Enable now**

  3. 03

    Terminal alternative: `dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay` — for the desktop app `dsh plugin --profile desktop add https://github.com/sorsama/deepseek-harness-relay`

    $ dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay

  4. 04

    Prebuilt package instead: `dsh plugin --profile web add dsh-relay` — the same code with `lib/` in it, and no build script runs

    $ dsh plugin --profile web add dsh-relay

  5. 05

    On the machine running the harness open `https://127.0.0.1:3443/relay/password` and set the first password, then pair the phone at `https://127.0.0.1:3443/relay/pair` with the QR code or the 8-digit code

Verify the integration

  • `https://127.0.0.1:3443/relay/health` answers once the relay is up
  • The harness prints the relay's address as it starts; in the desktop app quit and reopen it after enabling the plugin
  • The paired phone shows up under `/relay/devices` with the name you gave it

03DSH integration and capability boundaries

DSH integrationNative runtime

Native DSH plugin for the harness web profile — installed with `dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay` it adds its own :3443 listener, a **Relay** action, a `/relay/*` page set and a **Plugins → dsh-relay → Configure** settings page

  • TLS termination and password sign-in

    an HTTPS request from a phone or browser on the network→a session only once the password (or a paired device's credential) is accepted; too many wrong guesses lock that address out for a while

    the harness stays on loopback while the relay runs as a second listener next to it
  • QR / 8-digit code device pairing

    a QR scan, or the 8-digit code typed on the phone, plus a name for the device→a named device under `/relay/devices` that holds its own token

    a paired device is recorded under `/relay/devices` and can be revoked on its own
  • mDNS discovery on `_dsh._tcp`

    the relay is advertised on `_dsh._tcp`, so apps find it without scanning the subnet

  • Relay pages inside the harness UI

    the unchanged harness UI with a corner **Relay** link and a **Relay** action at the sidebar foot

    pressing **Relay** switches the running app to the relay's pairing, device and password pages in place, in the same window
  • Computers: one-click linking between two PCs

    the other computer's address, its pairing code and its certificate pin→the pair listed on both Computers pages, and **Open** landing this browser on the other harness with a one-time sign-in

    the pair is recorded on both computers, and **Unlink** on either one ends it

04Who is it for? When not to use it?

Good for

  • Anyone running the harness web profile on a laptop or desktop who wants it on a phone or tablet on the same network (or forwarded from outside) without binding it to 0.0.0.0
  • People who share one relay with a phone, a tablet and a second computer and want each of them revocable on its own
  • Developers with a desktop and a laptop both running dsh-relay, working in a browser rather than the desktop app

Not for

  • The relay only makes sense in front of a loopback harness: it refuses to start if the harness already listens on a network address, and it treats loopback as you — so a loopback proxy (Tailscale Funnel / Serve, nginx, Caddy) in front of `127.0.0.1:3443` never asks anyone for a password.
  • In the desktop app, never add a redirect from the harness's own port to the relay's origin: the app window cannot complete a navigation to the relay's self-signed certificate and that failure is fatal to the app. The desktop app also cannot load a remote harness at all.
  • Harness and relay versions have to match: the README pairs harness 0.1.7-rc.2 through 0.2.x with dsh-relay 0.3, and the harness refuses to load a plugin whose range doesn't fit.
  • Clients older than DSH Mobile 0.8.0 send no credential at all, so the relay lets them in by remembering the phone's network address — which the README calls not real authentication. The separate plain-HTTP listener (`DSH_RELAY_PLAIN_PORT`) has no sign-in or pairing pages and can never reach harness settings or credentials.

05Compatibility, maintenance and safety notes

  • The relay only makes sense in front of a loopback harness: it refuses to start if the harness already listens on a network address, and it treats loopback as you — so a loopback proxy (Tailscale Funnel / Serve, nginx, Caddy) in front of `127.0.0.1:3443` never asks anyone for a password.
  • In the desktop app, never add a redirect from the harness's own port to the relay's origin: the app window cannot complete a navigation to the relay's self-signed certificate and that failure is fatal to the app. The desktop app also cannot load a remote harness at all.
  • Harness and relay versions have to match: the README pairs harness 0.1.7-rc.2 through 0.2.x with dsh-relay 0.3, and the harness refuses to load a plugin whose range doesn't fit.
  • Clients older than DSH Mobile 0.8.0 send no credential at all, so the relay lets them in by remembering the phone's network address — which the README calls not real authentication. The separate plain-HTTP listener (`DSH_RELAY_PLAIN_PORT`) has no sign-in or pairing pages and can never reach harness settings or credentials.
2026-08-212026-11-09v0.4.0

MIT · latest release v0.4.0 (2026-11-09) · active, README tested against harness 0.1.7-rc.2 through 0.2.x

06Frequently asked questions

How do I install dsh-relay into DeepSeek Harness?

Open **Plugins** in the sidebar, choose **Add plugin**, paste `https://github.com/sorsama/deepseek-harness-relay` and press **Install**. The first install builds the plugin in a temporary copy, so allow the pnpm build script when asked and then choose **Enable now**. From a terminal the same URL works with `dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay` (use `--profile desktop` for the desktop app), and the prebuilt npm package installs with `dsh plugin --profile web add dsh-relay`, which runs no build script.

Which harness version does it match?

The README's table pairs harness 0.1.7-rc.2 through 0.2.x with dsh-relay 0.3 (tested on 0.2.1-rc.3, 0.2.0-rc.2 and 0.1.7-rc.2). If you install a version that doesn't match, the harness refuses to load it and tells you which range it needs — 0.3 depends on the settings system added in harness 0.1.7, and 0.2 hangs the web app on 0.1.7 and later.

Can someone on the network claim the relay before I set a password?

No. Until a password exists, the password page only works from the machine running the harness. That machine is never asked for a password either: the relay treats loopback as you, because anyone sitting at that keyboard already has a shell.

What can a paired device do, and how do I cut it off?

Each paired device gets its own token and shows up under `/relay/devices`, where you can revoke it on its own. Codes are single-use, expire after five minutes and can only be created on the machine running the harness. The **sign out everywhere** button rotates the signing key and logs out every browser and device at once.

Can I put it behind Tailscale, nginx or Caddy?

Don't. Those proxies connect from loopback and the relay treats loopback as you, so it asks nobody for a password. For internet exposure the README says to forward the relay's port and never the harness's, use a real certificate, and set `compat.addressGrants: false` with `privilegedMethods: loopback-only`. Don't add a redirect from the harness's own port to the relay's origin either: the desktop app's window cannot complete a navigation to the relay's self-signed certificate, and that failure is fatal to the app.

08Data and sources

  • Author-claimedgithub.com62d7315bce02…

    dsh-relay is a plugin for the harness's web profile.

  • Author-claimedgithub.com62d7315bce02…

    dsh plugin --profile web add https://github.com/sorsama/deepseek-harness-relay

  • Author-claimedgithub.com62d7315bce02…

    A settings page at **Plugins → dsh-relay → Configure** on the machine running the harness. Changes apply when you press…

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-16. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.