dsh-ssh
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
wenbin-wb/dsh-bridge
Remote and mobile access for DeepSeek Harness: provides LAN QR code connection, Cloudflare/custom tunnels, WeChat, QQ, Feishu, Telegram bot integration, and security authentication.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 11d agoon DeepSeek Harness 0.2.2-rc.1.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 11d ago.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
shell commands (bash, exec, spawn …); API keys, tokens or passwords
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — dsh-bridge provides remote connection and mobile access for DeepSeek Harness.
Who it is for — When you need to remotely use DeepSeek Harness from your phone via QR code scan, you can install dsh-bridge. If you mainly run it locally without needing remote or mobile support, you can skip the installation.
Watch out — Sandbox test passed: it can be installed and registered in a fresh profile. It requires providing an API key or token and will execute shell commands. No obvious pitfalls found.
The verdict — I would install it because it supports LAN QR code connection and Cloudflare/custom tunnels.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

dsh-bridge is a DeepSeek Harness plugin that exposes a local DeepSeek Harness instance to LAN devices, mobile browsers, public tunnels and supported messaging platforms.
DeepSeek Harness loads dsh-bridge in the web profile, where it starts a LAN reverse proxy with QR-code access and detects available network interfaces. The proxy forwards remote requests to the local service and injects the loopback session cookie required by DeepSeek Harness, so remote clients do not need the startup ?token= URL. dsh-bridge can also start a Cloudflare tunnel, use a Cloudflare Token for a fixed domain, or connect to a self-managed public tunnel. Its remote page provides workspace selection, while WeChat, QQ, Feishu and Telegram integrations provide multi-workspace sessions, approvals and file transfer. Access is protected by a QR token, an external access password and a separate administrator lock; reset-auth is the terminal recovery command.
This is intended for operators who need to continue DeepSeek Harness work from another device or through an IM bot. It is a poor choice when access should remain local, or when exposing an agent with terminal and workspace permissions is unacceptable. The plugin reaches the DeepSeek Harness service, its workspaces and task-execution surface because remote clients can schedule tasks, approve operations and manage workspaces. Cloudflare and bot integrations also require their corresponding credentials. Node.js 22.19+ or 24+ and a working dsh CLI are required.
DeepSeek Harness loads dsh-bridge as a web-profile plugin. When the service starts, dsh-bridge starts a LAN proxy, detects physical and virtual network interfaces, and presents a QR-code connection address. Its reverse proxy forwards remote requests to the local DeepSeek Harness service and adds the loopback session cookie required by DeepSeek Harness. Remote access therefore uses the plugin’s entry point rather than the DSH startup URL containing ?token=.
The plugin can expose the proxy through a temporary Cloudflare domain, a fixed Cloudflare domain configured with a Cloudflare Token, or a self-managed public tunnel. The tunnel path uses SSE and includes idle keep-alive handling. dsh-bridge also checks public reachability through /ready and reports DNS, TLS, edge and origin results in its settings panel.
Open the DeepSeek Harness settings panel and select Remote Access. The documented settings cover LAN access, Cloudflare tunnels, authentication, IM channels, workspace access and operational controls. dsh-bridge can export and restore its global configuration as JSON. The README does not specify the individual configuration key names or storage paths.
Authentication has separate layers:
127.0.0.1 retains the highest privilege.The terminal command reset-auth resets authentication when recovery is needed. Remote clients can use /addworkspace to register a workspace. The /diff action exports the current round’s file changes as a .patch file. IM integrations support session persistence across restarts, approval cards and two-way file transfer.
DeepSeek Harness requires Node.js 22.19.0 or later in the 22.x line, or Node.js 24.0.0 or later, plus an available dsh CLI. The plugin supports DeepSeek Harness web profile installations and requires a separate installation for the desktop profile. Cloudflare fixed-domain access requires a Cloudflare Token, and each bot channel requires its platform credentials. Exposing the service remotely also exposes the agent’s task, terminal and workspace capabilities to authenticated clients.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
zhu1090093659
Remote control of a dsh web workspace from phone or PC: QR-code pairing through a token-gated channel, SSE real-time sync, and separate mobile and full desktop GUI modes.
Installed cleanly when we ran it
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
liguobao
Multi-device remote access for DeepSeek Harness and supported coding workspaces through an end-to-end encrypted channel, with adaptive Relay/WebRTC transport, device authorization, workspace files, read-only previews, terminals, and optional Codex Remote.
Installed cleanly when we ran it
liguobao
Multi-device remote access for DeepSeek Harness: continue an active session from your phone, tablet, browser, or another computer over an end-to-end encrypted channel (Noise IK + adaptive relay/WebRTC transport), with device authorization, ApiProxy-only remote capabilities, and read-only file preview via dsh-file-viewer — no shell, remote desktop, or write access.
Installed cleanly when we ran it
saya-ch
Access DeepSeek Harness from the Android app or a mobile browser with secure LAN and remote connections, persistent device pairing, and a customizable mobile interface.
Installed cleanly when we ran it