jsdvjx/dshn

dshn (DeepSeek Harness Network) exposes a locally running DSH web UI to the public internet under a *.ds.hn subdomain gated by a login: the plugin's Settings form takes a subdomain prefix and password as the whole credential (trust-on-first-use, scrypt-hashed on the relay), several machines can bind one subdomain as named devices with a browser-side switcher, an optional end-to-end password (PBKDF2-SHA256 then AES-256-GCM) encrypts API bodies and the event stream so the relay sees only ciphertext, and response bodies are gzipped before the narrow agent-to-relay hop.

dshn (DeepSeek Harness Network) exposes a locally running DSH web UI to the public internet under a *.ds.hn subdomain, gated by a login. Install the plugin, open dsh locally, and a form in Settings asks for a subdomain prefix and a password - those two are the credential, with no tokens, environment variables or provisioning. Several machines can bind one subdomain with the same credential, each showing up as a named device: with two or more online the URL offers a device picker and a sidebar-footer switcher, the choice sticks per browser through a routing cookie, and switching is a clean reload against the other machine. An optional end-to-end password encrypts /api bodies and the event stream so even the relay operator sees only ciphertext. Response bodies are gzipped before they enter the tunnel because the agent-to-relay hop is the narrow one (a cold app load drops from roughly 12.5 MB to 5.0 MB on the wire), and the data plane is self-hosted, needing no per-user Cloudflare account or NS delegation.

Infrastructure & Deployment ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add @dshn/agent

Copied verbatim from the README's 'Install the agent (user's machine)' block. npm package @dshn/agent at 0.4.0 (registry check 2026-10-15; the registry repository field resolves back to this repo). The README also documents a local tarball form.

Compatibility

The README carries an explicit security warning: dsh ships bash and filesystem tools, so a publicly reachable dsh UI is a remote shell - the relay's login gate is not optional, a strong password is required, and end-to-end encryption is recommended for anything sensitive. The credential is a (subdomain, password) pair set once in Settings and persisted to ~/.dsh/settings.yaml, claimed trust-on-first-use with the password scrypt-hashed on the relay; squatting is therefore protected. The optional e2e password is never sent to the relay (PBKDF2-SHA256 at 210k iterations, then AES-256-GCM) and can be remembered per device in localStorage but is never transmitted.

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