YOLO-LZL/dsh-ssh-plugin
Lets a DeepSeek Harness agent run commands on a remote Linux server over the system ssh client, with connections you save once and bind to a workspace so ssh_exec uses them by default. The remote command travels through ssh stdin to bash -s with no extra quoting layer, hosts already defined in your local ~/.ssh/config need no manual save (the alias resolves, and ssh_connections list shows them read-only), and the dual-face package registers both the ssh-connections settings namespace and the ssh_connections tool on the host side and an 'SSH Connections' card in Settings → Plugins in the browser.
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
README: it adds the ssh_exec model tool plus persisted connections, is key-based only (BatchMode=yes, so a missing or unauthorized key fails fast instead of prompting), and runs the ssh client under the calling session's standing policy so danger-full-access runs it unconfined. All harness services except tools/shell are optional and profiles without settings or workspaceRegistry degrade gracefully; the README publishes a degradation matrix.
Details
- Repo: YOLO-LZL/dsh-ssh-plugin
- Category: Infrastructure & Deployment
- Stars: 0
- Version: Source install (no registry version asserted; repo 0★, MIT, last push 2026-08-14)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
The README documents the two tool surfaces, the data model, the config and a degradation matrix rather than a release-by-release table.
FAQ
- How do I install it?
- The README lists an npm form, a github:<owner>/dsh-ssh-plugin form and a local ./dsh-ssh-plugin form, but the profile field and git owner are placeholders; the local form needs pnpm install && pnpm bundle first.
- Does it support password logins?
- No — the README says key-based authentication only, using BatchMode=yes, so a missing or unauthorized key fails fast rather than hanging on a prompt.
- Do I have to save my servers?
- Not necessarily: per the README, hosts already in your local ~/.ssh/config are recognized — pass the alias as ssh_exec host and ssh resolves it, while ssh_connections list shows them read-only.