AI Agent Hub
Back to plugins
🖥️

dsh-cloud-connector

Client Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install gzr123166/dsh-cloud-connector

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

Run dsh plugin install gzr123166/dsh-cloud-connector in the DeepSeek Harness terminal to install, see source at https://github.com/gzr123166/dsh-cloud-connector

About this plugin

Juggling multiple cloud servers used to mean cycling through a terminal, memorizing IPs, and re-typing SSH commands after every reboot. dsh-cloud-connector folds all of that into a single SSH Connections panel inside DSH Settings: add hosts with a quick form, toggle each one on or off with a switch-style button, persist the list to a local JSON file so nothing is lost across restarts, and set per-server auto-connect on launch.

On top of the connection manager, the plugin adds an SSH port-tunnel layer that exposes services bound to 127.0.0.1 on a remote box (Jupyter, a database, a local web app) directly into your browser, with per-tunnel start/stop toggles and optional auto-start. The other core piece is a set of cloud_* chat tools spanning remote command execution, scp file transfer, nvidia-smi GPU monitoring, conda environment management, Slurm job-queue queries, and full CRUD on server configurations. You simply state what you want in chat and the plugin drives the SSH session for you.

If you operate several GPU cloud instances, frequently pull inner-network ports into your desktop, or submit Slurm jobs and want the entire workflow to stay inside the DSH chat rather than bouncing back to a terminal, this plugin is built for exactly that.

Use Cases

  • Visually manage multiple cloud server SSH connections from the DSH chat panel
  • Map a remote 127.0.0.1-bound Jupyter or database port to your local browser via SSH tunnel
  • Run remote commands, transfer files, monitor GPUs, and submit Slurm jobs directly in chat

Best For

  • Researchers managing multiple GPU cloud instances simultaneously
  • Developers who frequently pull inner-network services into their local desktop
  • Users who prefer to stay in the DSH chat window instead of switching back to a terminal