dsh-control
在一个本地窗口中管理所有机器上的 dsh 实例——远程会话原生流式传输到侧边栏。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:6mt/dsh-control#f2c772ef039f826fcfdd8bab13a7317f4cae1de9Control 以 dsh-control 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Every machine already runs dsh. Make this one window the front end for all of them.
Chat with the dsh instances on your other machines, natively from your local sidebar. Remote sessions stream back token by token; the remote uses its own model credentials, tools and sandbox. Zero changes on the remote. Zero dependencies. One-line install.
A real two-machine setup. Left: the remote machine's own dsh — the session there was created
for you and auto-named 控制端·<local title> (①). Right: your local dsh — the same question
runs on the remote (③ the model route is the environment name, cn-dsh2) and the answer lands in a
local session inside the workspace the plugin created for that environment (②).
🎬 A 15-second capture (one-click connect → streaming reply) is being recorded.
dsh plugin --profile <your profile> add github:6mt/dsh-control
Use the profile you already run (usually web or desktop). No build step, no native
modules, no dependencies — the plugin is plain JavaScript and installs as-is.
Download dsh-control-0.1.1.tgz and run:
dsh plugin --profile <your profile> add ./dsh-control-0.1.1.tgz
After installing, fully quit and reopen dsh (⌘Q). A「远程 dsh 环境」panel appears in the right sidebar.
An npm package (
dsh-control) is prepared and can be published later; the GitHub command above is the current install path.
github:6mt/dsh-control installs the newest commit of main and
pins it in your profile's lockfile — it does not silently follow later commits.dsh plugin --profile <your profile> update dsh-control
(pnpm re-resolves the git ref and pulls the new code)github:6mt/dsh-control#v0.1.0 (tag) or github:6mt/dsh-control#<commit>| Remote-workspace plugins (dsh-remote, …) | dsh-control | |
|---|---|---|
| The remote machine is a | file system (SFTP tool set) | dsh that is already running there |
| Sessions live | local session + remote directory | remote sessions, native in your sidebar |
| Credentials & tools | configured locally, SSH config duplicated | the remote's own — nothing copied |
| Remote needs | only SSH | dsh installed (≥0.2.0-rc.2) with its web instance running |
| Changes on the remote | some deploy dsh for you | zero (read-only probing + the remote's own API) |
The two coexist (tested side by side): no dsh on the remote → use dsh-remote; dsh already there → use dsh-control.
The remote dsh environments panel
The「远程 dsh 环境」panel: type user@host and connect — the row then reports its state and
whether the environment already has its workspace.
user@host; the plugin probes the remote dsh, fetches
its access token and opens an encrypted channel (~5 s)控制端·<local title>, so both sides matchWhat it does on your machine: one state file
($DSH_HOME/dsh-control/state.json, mode 0600, holds the remote access tokens) and an
on-demand SSH tunnel process.
What it never does: no installs or writes on the remote, no lifecycle management of
the remote dsh, never reads your other local credentials, tokens never enter logs.
When passwordless SSH is not set up it shows the exact one-line fix — passwords are
never stored. Details in SECURITY.md.
node --check lib/*.js
for t in test/*.test.mjs; do node "$t"; done # 52 checks: unit / contract / structural invariants
scripts/verify-boot-selfheal.sh # boot self-heal (needs a local dsh runtime)
MIT © 6mt