AI Agent Hub
Back to plugins
🧰

dsh-ssh-bridge

Web Tools Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install lance-kanglu/dsh-ssh-bridge

Paste the following prompt into your AI chat to install this plugin:

Install this plugin in DeepSeek Harness by running dsh plugin install lance-kanglu/dsh-ssh-bridge; source at https://github.com/lance-kanglu/dsh-ssh-bridge .

About this plugin

Running commands on remote hosts from inside an agent loop usually means either hardcoding a fleet of targets in config or pasting passwords into the chat history—neither is secure nor flexible. dsh-ssh-bridge collapses that into one step: you type user@host[:port] and a password into a local browser page, an SSH-encrypted channel is established, and the credential never touches the conversation log or disk.

Once mounted as a DSH plugin, the agent gains three tools—router_exec, router_disconnect, and router_reconnect—letting it run one-shot commands, write lines into an interactive terminal, and disconnect or re-authenticate with stored in-memory credentials. The browser page renders ANSI colors, shows a live status log, and behaves like a standard SSH client: typing exit tears down the whole session. The bridge core runs standalone without DSH, so it also works in pure-script or local-debugging setups.

Built for developers and SREs who need their agent to operate on arbitrary SSH targets without baking logins into prompts or config files. Any host speaking standard SSH is in scope—no preset list, no extra client, just a browser tab and a tool call.

Use Cases

  • Agent executes commands on any SSH host via a tool call, no pre-configured target list required
  • SRE opens a local browser page, authenticates, and debugs production servers interactively
  • Scripts or automation securely invoke remote commands through a loopback API with credentials kept in memory only

Best For

  • Developers running DSH agents that need to operate over SSH
  • SREs who want to keep credentials out of chat logs and route them through a local encrypted channel
  • Ops engineers who need to debug remote services locally without hardcoding hosts into prompts