@deepforce/dsh-plugin-reloader
无需重启 dsh web 即可热加载已安装的 DeepSeek Harness 插件：监视插件包，在原位重新加载发生变化的插件，并在依赖项发生变化时重启
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @deepforce/dsh-plugin-reloader@0.3.0Plugin Reloader 以 @deepforce/dsh-plugin-reloader 发布，当前版本为 0.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
Hot-reload installed DeepSeek Harness
plugins without restarting dsh web. After you upgrade a plugin (e.g. dsh plugin add github:...), the new code takes effect in place; only a dependency-tree change restarts the
process (through an external supervisor script).
It reuses the same reload pipeline dsh's built-in HMR uses for user code — clear the module
caches, re-import the plugin entry, dispose the old fibers, mount fresh ones, roll back on
failure — minus the node_modules exclusion that keeps the built-in HMR away from installed
plugins. The loader's internal module cache is reachable through dsh's vendored loader
without any special flag.
package.json files (every
pollIntervalMs, default 2s) and hot-reloads a plugin in place when its code changes.
Polling (stat mtime+size) is used instead of a file-watcher library: chokidar's fs-watch
never reached ready inside the long-lived dsh web process on Windows, and polling is
immune to pnpm's whole-directory replacements (the stat simply sees the new files on the
next tick). Plugin upgrades are low-frequency, so a 2-second stat of a handful of files is
negligible./reload <plugin> command — manually hot-reload one installed plugin; with no
argument it lists the loaded plugins, marking non-reloadable ones ([official],
[service], [self])./watch-status command — prints live watch diagnostics: watched scopes, event count,
the last observed change, reload count, skipped reloads, and any startup error. Read it
after upgrading a plugin to confirm the auto-reload fired (events and reloads
incremented).package.json changes its
dependencies/peerDependencies, the process exits with code 42 (configurable) so a
supervisor relaunches it.@deepseek-ai plugins and plugins that provide
services other plugins depend on are not hot-reloaded by default: the attempt is
skipped, logged, and counted in /watch-status. Reloading a service provider would
cascade restarts through every plugin that injects its services, and reloading an
official plugin is equivalent to patching dsh itself mid-session. Override per category
with allowOfficial / allowServiceProviders.dsh plugin --profile web add github:deepforce/dsh-plugin-reloader
Restart dsh web once so the plugin loads. For the dependency-change restart to be useful,
start dsh through the supervisor instead of directly:
# Windows (cmd)
scripts\dsh-restart.cmd web
# Windows (PowerShell)
powershell -File scripts\dsh-restart.ps1 web
After upgrading an installed plugin:
dsh plugin --profile web add github:deepforce/dsh-balance # upgrade
The watcher notices the changed lib/ files and hot-reloads it — no restart. To force it
manually, type /reload @deepforce/dsh-balance in a session, or /reload with no argument
to list candidates.
If the upgrade also changed the plugin's dependency tree, the process exits 42 and the
supervisor relaunches dsh web automatically (a supervisor is required — a plain dsh web
just exits).
| Field | Default | Meaning |
|---|---|---|
watchEnabled | true | Poll installed plugins and hot-reload on code changes |
watchRoots | ["@deepseek-ai", "@deepforce"] | Scoped directories under the profile's node_modules to consider |
debounceMs | 400 | Change coalescing window before a reload fires |
pollIntervalMs | 2000 | Polling interval for change detection |
restartExitCode | 42 | Exit code used when a dependency tree changed (supervisor restarts on it) |
allowOfficial | false | Also hot-reload official @deepseek-ai plugins (not recommended) |
allowServiceProviders | false | Also hot-reload plugins that provide services other plugins depend on (not recommended) |
Example overlay:
# reloader.cordis.yml
- patch:
- id: plugin-reloader
config:
debounceMs: 600
restartExitCode: 50
Tested against DeepSeek Harness 0.2.0-rc.2 (web profile, Windows 11, Node 24) and earlier
0.1.0-rc.x builds. It depends on the loader's internal module cache (loader.internal), which
the vendored loader exposes by default; if a future dsh removes that surface, the plugin degrades
to /reload reporting "loader internal is unavailable". Version 0.3.0 requires dsh 0.2.x:
0.2.0 and earlier pin dsh-commands to ^0.0.1-rc.1, which — caret on a 0.0.x version being
an exact-version constraint — matches no later build, so dsh's plugin compatibility gate skipped
the plugin entirely.
pnpm install # uses pnpm-workspace.yaml overrides for upstream npm gaps
pnpm run build # tsc emits lib/index.js
MIT