flymysql/dsh-remote

English · 中文

dsh-remote

Remote-work assistant for DeepSeek Harness (DSH).

Manage several SSH machines, then pick a remote workspace (or a local one) and let the agent operate right there without leaving the harness — listing files, reading code, running builds & commands over the remote host, and keeping that remote directory mirrored into a real local workspace object.

The harness Web UI intentionally binds 127.0.0.1 (the CLI rejects --host 0.0.0.0 for safety). This plugin goes the other way: you connect out to the machines you maintain, pick a workspace, and work in it through the normal DSH workspace + agent fs flows — no changes to dsh-workspace or the harness core.

Screen previews

Settings → 远程工作区 — a multi-machine SSH registry (add / edit / delete / set-current, password stored locally):

The native “Add workspace” / “Select workspace” flow — a centered modal, two tabs, opens on 本机 (local); switch to 远程 (remote):

• 远程 — a machine <select>, a path field that auto-prefills / and live-completes directories (picking one immediately reveals its next level, OS/VSCode-style), plus a 浏览… floating browser that fills the field without committing — you review, edit, then 设为远程工作区.

Real capture (host scrubbed to a placeholder):

Features

• Multi-machine SSH — save any number of hosts (host/port/user + private key or password). Passwords are stored locally and never shown back in the UI. Switch with one click in Settings.
• Two-tab workspace picker (fills the native “Add workspace” flow):
  • 本机 / Local — opens the native OS folder chooser over the host, or lets you type a local path → adopted directly as a normal DSH local workspace (local workspaces fully coexist). The chooser uses the DSH directoryPicker service when available and otherwise falls back to the plugin’s own native picker (macOS osascript / Linux zenity→kdialog) — so it works even when the framework service isn’t registered on the desktop boot path.
  • 远程 / Remote — the picker is a centered modal (never squeezed into a narrow sidebar). Pick a machine → the path field is pre-filled with / and live autocompletes directories; selecting a directory immediately lists its next level (OS/VSCode-style cascade). A 浏览… floating browser (opaque, height-capped, scrollable, follows symlinks) fills the field without committing — you review, edit, then confirm. On confirm it creates a real local mirror under $DSH_HOME/remote-workspaces/<host>-<user>-<port>/<base> (a short path-hash is appended only when a different remote path already took the same basename) that passes fs.realpath → the harness adopts it as a real workspace while dsh-remote keeps it synced over SFTP. The chosen workspace is persisted on the machine, so it survives restarts.
• Bidirectional SFTP sync — rw_sync (remote → mirror) and rw_push (mirror → remote) round-trip your local-mirror edits back to the machine. Both are incremental: files whose size + mtime already match are skipped, and a per-file size cap prevents accidental big-binary downloads. Directory sweeps run with bounded parallelism.
• Model tools — rw_info, rw_connect, rw_pick_workspace, rw_list_dir, rw_read_file, rw_write_file, rw_exec (runs in the current workspace by default, or cwd=<path>), rw_search (portable recursive grep), rw_download, rw_upload, rw_sync, rw_push, rw_disconnect.
• Write directly to a remote file — rw_write_file creates or overwrites a remote file (making parent directories), so you don’t have to round-trip through a local mirror for a single-file edit. rw_download / rw_upload move a single file either way when you need the real bytes.
• Connection health — a 「测试连接」 test-connection button in the Settings page validates host/user/key/password before you save a machine.
• The active user@host:/path is injected into every system prompt so the agent knows its working root.
• No official dsh-workspace core is modified — everything is delivered as a normal plugin (directory-flow holes filled by the client half at priority -100).
• Cross-platform remotes — commands use portable POSIX forms (ls -la, sed -n, find … -exec grep), so the same plugin works against macOS/BSD as well as GNU/Linux hosts.
• Host-key verification (TOFU) — every SSH connect verifies the host key (hostKeyMode: accept-new): first connect records it, a later CHANGE is rejected as a possible man-in-the-middle. verify also refuses hosts never seen before; off disables it. Stored at $DSH_HOME/remote-workspaces/known_hosts.json; reset with /remote forget-key.
• Data lives under the harness home — machines + mirrors follow $DSH_HOME (the desktop app sets it to its own userData/harness); pre-0.6 data under ~/.dsh/remote-workspaces is migrated automatically on first run.

Install

dsh plugin add dsh-remote            # add the bundle

(or npm install dsh-remote + add - id: dsh-remote / name: dsh-remote in cordis.patch.yml).

Quick start

1. Add a machine — Settings → 远程工作区 → add host/port/user + key or password → (optional) set it current.
2. Open a workspace — click Add workspace in the sidebar / conversation:
   • 本机 → system folder chooser (or type a local path) → local workspace.
   • 远程 → choose the machine → browse to a remote directory (or type /path) → “设为远程工作区” ⇒ a local mirror workspace is created and adopted.
3. Work with the agent — treat it like any workspace:
   • rw_list_dir(path?)/rw_read_file — inspect remote files
   • rw_write_file(path, content) — create or overwrite a remote file directly
   • rw_search(pattern, path?) — grep remote files
   • rw_exec(command, cwd?) — run remote shell commands (defaults to the workspace dir)
   • rw_sync / rw_push — pull/push the local mirror to and from the remote

CLI defaults (optional)

Provide a default machine in cordis.patch.yml:

# Example only — use values for your own machine.
- id: dsh-remote
  name: dsh-remote
  config:
    host: 203.0.113.10   # or your real host / hostname
    port: 22
    username: dev
    privateKeyPath: ~/.ssh/id_rsa
    # or password: '…'
    workspace: ~/project

If host is empty the plugin starts disconnected and you configure machines in the UI.

CLI quick reference

Installing and driving DSH may live in different shells, so both the dsh binary and the npx form are shown. Always tell DSH which profile to use with --profile <name> (usually web).

# install the bundle into a profile (npm is pulled by pnpm; recommended)
dsh plugin --profile web add dsh-remote
# same but when `dsh` is not on PATH (e.g. Windows PowerShell inside a repo)
npx --yes @deepseek-ai/dsh plugin --profile web add dsh-remote

# confirm it is installed wire
dsh plugin --profile web list
npx --yes @deepseek-ai/dsh plugin --profile web list

# start the web surface (reload profile; the plugin activates on boot)
dsh --profile web
npx --yes @deepseek-ai/dsh --profile web   # http://127.0.0.1:3080

# use a local checkout instead of the npm version (dev iteration)
npx --yes @deepseek-ai/dsh plugin --profile web add /path/to/dsh-remote
npx --yes @deepseek-ai/dsh plugin --profile web remove dsh-remote   # back to release

After a successful start, Settings → 远程工作区 appears and the “Add workspace” flow gains the 本机 / 远程 tabs (screenshots above).

Development (sandbox, not product)

Iterate in the sandbox, never by hand-editing a product profile — the product profile is re-managed by the plugin manager and reverts hand-deployed files on reinstall. Use the helper script:

scripts/dev-run.sh --restart   # start / restart the isolated sandbox
scripts/dev-run.sh --stop      # stop it
scripts/dev-run.sh --status    # is it running?

• Runs its own DSH instance (dev-harness/harness inside this repo) with the plugin copied in from lib/ — it boots through the same bin.js web --patch path as the desktop app, so the sandbox reproduces the product boot behavior.
• The sandbox web UI serves on http://127.0.0.1:50599 and the plugin routes are live immediately (e.g. GET /dsh-remote/machines).
• Host-half changes (lib/index.js) need a sandbox restart (--restart); client-half changes (lib/client.js) need a page refresh.
• Node ESM resolves dependencies from the importing file’s real path, so the script copies lib/ (hardlink copy, cp -al) into the sandbox profile instead of symlinking — a symlink breaks @deepseek-ai/* resolution.
• Run scripts/check.mjs (static framework-constraint gate: command-name regex, …) before every commit; scripts/boot-smoke.sh boots an isolated instance to prove the plugin still starts.
• Full rules live in scripts/dev-standards.md (command names, cordis service access via ctx.get() only, optional framework services may never register, verify third-party callback contracts against the real runtime, …).

Deploying to a product profile is a separate, explicit action (./sync.sh) and should be done only when you intend to release.

Configuration

Safety

Giving the plugin a machine’s credentials lets the agent run shell commands as your user on that host. Only add machines you trust. Passwords are saved on the local machine file; treat it as sensitive (you may lock file ACLs).

License

MIT

Changelog

See CHANGELOG.md.