sorsama/deepseek-harness-relay

Authenticated remote access to a DSH web profile: password sign-in, QR device pairing, TLS, mDNS, and a transparent proxy of the whole UI.

The harness serves its browser API on loopback and refuses dsh web --host 0.0.0.0 on purpose, because that would expose remote code execution to the network. This relay is the authenticated front door instead: password sign-in with a scrypt hash and a signed HttpOnly, SameSite=Strict cookie plus per-address lockout; QR and passcode pairing that mint revocable single-use bearer tokens, issuable only from the machine running the harness; a device list with per-device revoke and a sign-out-everywhere that rotates the signing key; TLS from your own certificate or self-signed with a published SPKI pin; and mDNS advertisement on _dsh._tcp so a client finds it without sweeping the subnet. The proxy is transparent, so the browser app works from a phone exactly as it does locally, with a Relay link for the pairing pages. Loopback requests never have to sign in — whoever is at the keyboard already has a shell.

Infrastructure & Deployment ★ 10
View on GitHub ↗

Install

dsh plugin --profile web add github:sorsama/deepseek-harness-relay#v0.2.1

This pinned tag is the 0.2 line, which the README scopes to Harness 0.1.2 through 0.1.5 — its table also states the 0.2.1 tarball on npm shipped a stale runtime that cannot authenticate, which is why the GitHub tag is the documented form. On Harness 0.1.7-rc.2 through 0.2.x the README points at the 0.3 line instead (dsh plugin --profile web add dsh-relay). Either way, first remove any 0.0.0.0 bind row from ~/.dsh/profiles/web/cordis.patch.yml — the relay refuses to start in front of an already-open server — then open /relay/password from the machine running the harness to set the password.

Compatibility

The supported range is declared as engines.dsh and the harness reads it before a profile starts, so an out-of-range release is refused with a message naming the range instead of loading half-working. The author documents two silent-failure traps on the 0.1.7+ settings plane: the settings namespace is the loader entry id (relay), and form fields must be .volatile() — get either wrong and you get no configuration page and no log line.

Details

Alternatives

sorsama/deepseek-harness-mobile · starsqvq/deepseek-harness-desktop · evanmormmm/deepseek-harness-desktop

More plugins in Infrastructure & Deployment

Browse more in Infrastructure & Deployment

Guides for Infrastructure & Deployment plugins