dsh-remote-development: Let DeepSeek Harness Develop on SSH Remote Machines

What Does It Do?

It is a DSH plugin for DeepSeek Harness that turns an SSH machine into a workspace the agent can work in directly. It solves the problem of code and compute living on different hosts: register an SSH machine, pick a remote directory as the session workspace, and the agent works there with the exact same file, shell, and search tools it uses locally. The plugin adds no model-facing tools and no third-party UI plugin; instead it replaces the filesystem, subprocess, and bash providers with routing versions that translate local tool calls into remote execution. It is maintained by CJYLZS under the MIT license and written in JavaScript.

Core Features

• Identical toolset: remote workspaces add no tool calls, so the agent keeps using the same file, shell, bash, and search tools while the plugin routes those calls to the remote host underneath.
• Zero remote dependencies: the remote machine needs no server-side component, just an SSH connection.
• Connection management: password, private key, and SSH agent authentication, plus jump hosts, host-key TOFU, and connection testing.
• Visual workspace distinction: a custom per-machine color makes remote workspaces easy to tell apart in the interface.
• Anchor-based routing: setting a remote workspace creates a local anchor directory that records the remote coordinates and decides where that session's tools execute; anything outside the chosen directory keeps local behavior, so existing sessions are untouched.

How to Use This Plugin?

After enabling it in the DSH Web GUI, setup takes three steps. First, in the plugin's settings section enter host, port, and username, choose password, private key, or SSH agent authentication (with an optional jump proxy), and click test. Second, in the workspace directory flow open the Remote tab, browse the machine's directories, and set one as the session workspace. Third, work as usual: file tools, shell, bash, and search run through the same tool calls as before, only now they execute on the remote machine, and the model's working directory is the remote path, so it needs no special instructions. If that machine is later deleted, operations on the workspace fail with an explicit "machine is no longer configured" error; re-add the machine to resume.

How to Troubleshoot This Plugin?

When a remote workspace operation fails with a "machine is no longer configured" message, the machine recorded by that workspace anchor has been deleted and the plugin will not silently run elsewhere; re-add the same machine as described in the official documentation, or delete the workspace directory. If the connection test fails, check the host, port, username, and authentication method (password, private key, or SSH agent) as well as any jump proxy settings.