zhu1090093659/dsh-web#packages/dsh-ssh
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.
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.
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.
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 6d agoon DeepSeek Harness 0.2.1-rc.5.
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
pnpm skipped these dependency build scripts, and the plugin registered without them:
cpu-features@0.0.10ssh2@1.17.0Under pnpm 11 the install stops and asks you to approve them instead; an approved script runs with your user account's permissions.
Source: our sandbox install on DeepSeek Harness 0.2.1-rc.5, 6d 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.
Neither shell commands nor credentials.
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 — A DSH plugin that exposes a web terminal, progress-tracked SFTP, local port forwarding, and the same command across many hosts, with agents on that shared host config.
Who it is for — You run DeepSeek-V3 or DeepSeek-R1 in dsh web and want an agent to inspect a Linux box, move files, or open a local forward; stock dsh web has no server-ops surface. Keep it off if jump hosts and runbooks already live outside Harness and you only open DSH to write code or talk.
Watch out — It installed on a clean profile and DeepSeek Harness registered it. Live SSH to a real host was not exercised. No obvious pit showed up in that pass.
The verdict — This one goes on the profile by itself; I would not pull in the rest of dsh-web just to get an ops panel.
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-ssh is a DeepSeek Harness plugin that provides a web SSH operations panel for terminal access, SFTP transfers, local port forwarding, and one-command execution across multiple hosts.
DeepSeek Harness loads dsh-ssh through the web profile mechanism used by the dsh-web plugin family. The panel and agents use the same host configuration, so a host added for the panel is also available to agent-driven SSH operations. The plugin reaches configured remote hosts through SSH and exposes four operation types: an interactive web terminal, SFTP file transfer with progress, local forwarding tunnels, and concurrent cluster commands across hosts. The README does not name the host-configuration file, configuration keys, environment variables, or additional command-line commands.
dsh-ssh is intended for developers and operators who need agents to inspect or operate remote Linux servers from a DeepSeek Harness web interface, or to run the same command across a group of hosts. It is not a suitable choice for a local-only workflow with no SSH hosts, or where sharing host configuration between the panel and agents is not acceptable. It also adds remote-system access to the agent’s available permissions: installation should be assessed with the SSH credentials and host scope configured for the DeepSeek Harness web profile.
DeepSeek Harness loads dsh-ssh as part of the web profile through the official profile mechanism used by the dsh-web plugin family. The web panel and agents share the same host configuration. This allows a host configured for panel operations to be used by an agent, rather than maintaining separate host lists. The README does not identify the configuration file or expose named configuration keys.
The plugin provides these remote operations:
| Capability | Behaviour |
|---|---|
| Web terminal | Opens an interactive terminal session to a configured SSH host. |
| SFTP transfer | Transfers files through SFTP and displays transfer progress. |
| Local port forwarding | Creates a tunnel from a local port to a remote service. |
| Cluster execution | Runs one command concurrently across multiple configured hosts. |
The same host configuration is used by the panel and by agents, so these operations can be initiated through the web interface or delegated to an agent with access to the relevant host.
DeepSeek Harness must provide the web profile for this installation model. The repository’s compatibility badge identifies DeepSeek Harness >=0.2.0-rc.2. Remote operations also require SSH host configuration and credentials that can reach the intended systems. The README does not specify supported operating systems, environment variables, configuration paths, or standalone command names.
dsh-ssh can expose remote terminals, file transfer, port-forwarding tunnels, and multi-host command execution to an agent. Its effective reach therefore depends on the SSH hosts and credentials available through the shared host configuration. Limit the configured hosts and account permissions to the scope required for the agent’s tasks.
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
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
ZSeven-W
A live iOS Simulator or USB-connected iPhone inside the conversation: 22 agent tools for booting, building, driving the UI by accessibility identity or OCR text, list-row actions and SwiftUI preview hot reload, plus a streaming sidebar panel you can tap and drag on.
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