DeepSeek Harness Plugin

chjy090/dsh-pairing-gate

Category Security & Permissions Added 2026-10-29

Device-pairing gateway for DeepSeek Harness: by default it listens on 127.0.0.1:3443 over plain HTTP and reverse-proxies the local dsh at http://127.0.0.1:3080, so a loopback-only install works without any certificate. Production, cross-machine and app pairing require TLS: configure tlsCert/tlsKey plus an https publicUrl (self-signed is fine). A fronting Caddy/Nginx may terminate the public TLS, but the gate itself still needs tlsCert/tlsKey and the proxy must connect back over HTTPS. Features TOTP-authorised QR device pairing, username/password login, sliding sessions with absolute caps, device revocation, a WebUI admin panel and audit log, and a reverse proxy with WebSocket tunnelling. First-run setup is completed in the WebUI wizard. Tests: 171/171 unit tests, 29-step e2e.

Install

# from a prebuilt release tarball

dsh plugin --profile web add "https://github.com/chjy090/dsh-pairing-gate/releases/download/v0.7.5/dsh-pairing-gate-0.7.5.tgz"

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:chjy090/dsh-pairing-gate

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.