januory/dsh-remote-workspaces

Opens folders on remote SSH hosts as first-class DSH workspaces, so file tools and shell commands run on the remote machine, with no mirroring.

Makes a remote directory a workspace rather than a sync target. Once a remote folder is opened, the agent's file tools — read, write, edit, grep, glob — and its shell commands land directly on the remote host over SSH, in real time, with no mirroring step and nothing to drift: there is no local copy to go stale, and no sync to fail halfway. You pick the directory by browsing the remote filesystem, and the harness adopts it as if it were local. A multi-machine registry covers adding, editing and removing SSH hosts, and it can import ~/.ssh/config so existing host aliases do not need to be retyped — the practical difference between trying this on one box and using it across a fleet. The reason to care is the shape of the work it enables: a harness session that can edit a remote deployment, read a remote log or grep a remote tree without a tunnel or an rsync loop, while every local workspace keeps the sandbox rules it had before.

Infrastructure & Deployment ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add dsh-remote-workspaces

The README documents the repository form (dsh plugin --profile web add github:januory/dsh-remote-workspaces) and the released-package form dsh plugin --profile web add dsh-remote-workspaces, phrased as "once published to npm" — the package is now served by the registry at 0.3.6, so the npm form is what ships here. A source install is also documented (pnpm install for the ssh2 transport dependency, then dsh plugin --profile web add .).

Compatibility

Needs a DeepSeek Harness installation — the plugin resolves its host services at runtime — and Node.js >= 18, with the note that the harness itself runs on Node 22+. ssh2 is the only transport dependency and no external ssh binary is needed, which is what makes it work on a machine that has no OpenSSH client configured. Host entries carry alias, host, port, user, and a key or password, and credentials are AES-256-GCM encrypted at rest and never sent back to the browser. Local workspaces keep their full sandbox behaviour, so opening a remote folder does not loosen anything for the local ones. The README also documents a remote API and a testing section, and the path encoding has a stated edge: the full remote path is encoded into the anchor name, with separators and Windows-illegal characters becoming --, so /home/test and /data/test map to distinct directories.

Details

Alternatives

GooDAnDReaDY/dsh-remote-workspace · Sora233/dsh-extra-workspaces · harryopo/dsh-cloud-workspaces

More plugins in Infrastructure & Deployment

Browse more in Infrastructure & Deployment

Guides for Infrastructure & Deployment plugins