reina4xa/dsh-plugin-reload
Deepseek harness plugin for reloading your deepseek harness plugin (e.g
Gives the agent a reload_plugin tool that restarts exactly one Cordis Loader entry — matched by entry id, module name, or MCP serverName — while every other entry keeps running. Two strategies: mcp-client entries respawn the MCP server child process on restart (picking up new server code on disk) and re-register its tools without touching sibling MCP connections; in-process plugin entries get a hard reload that busts the Node ESM/CJS module caches for the entry and its local source files.
Install
dsh plugin --profile web add dsh-plugin-reloaddsh plugin --profile web add dsh-plugin-reload (npm dsh-plugin-reload 0.2.1, verified on npm 2026-08-30; since v0.1.2 the package declares a dsh.bundle so a single command installs and auto-mounts). Update: dsh plugin --profile web update dsh-plugin-reload.
Compatibility
DSH web profile; Cordis Loader entry restart by id, module name, or MCP serverName; Node.js; MIT.
Details
- Repo: reina4xa/dsh-plugin-reload
- Category: Other
- Stars: 2
- Version: npm dsh-plugin-reload 0.2.1
- Last push: 2026-08-16
- First seen: 2026-08-14
Recent updates
reload_plugin tool; single-entry reload by id/module/MCP serverName; MCP child respawn + tool re-registration; in-process hard reload with cache busting.
FAQ
- What can be reloaded?
- Exactly one Cordis Loader entry at a time, matched by entry id, module name or MCP serverName — everything else keeps running.
- How are MCP entries handled?
- mcp-client entries respawn the MCP server child process (picking up new server code on disk) and re-register its tools; sibling MCP connections are not affected.
- How do in-process entries reload?
- A hard reload: the Node ESM/CJS module caches for the entry and its local source files are busted before re-importing.
Alternatives
Equinox7379/dsh-update-radar · duntansen/dsh-update-checker · KeLearns/dsh-update-checker