dsh-npm-runner

Running npm scripts inside a DeepSeek Harness session used to mean either leaving the chat for a terminal or asking the agent to hand-roll a shell command. dsh-npm-runner closes that gap. It reads the workspace root manifest and the package.json files of every workspace sub-package—never walking node_modules—and presents the scripts as collapsible, per-package groups that behave like the familiar NPM Scripts panel in VS Code. Click any script and it starts in the background with live output, an elapsed-time counter, and a Stop button that reaps the entire process tree. The plugin auto-detects each package's own package manager from the lockfiles present (pnpm, yarn, bun, or npm) and runs scripts in that package's directory, so you never have to cd manually. When a workspace has no scripts, the entry simply stays out of the way. Every run is also registered with DSH's background-job registry, letting the agent inspect output or kill a job through job_list, job_output, and job_kill, while panel-side stops are marked accounted-for to suppress redundant completion notices. On the security side, all requests pass through DSH's gateway trust fence (loopback or trusted Host, Origin match), the workspace is taken from the session rather than the request, and the host re-reads the target package.json to rebuild the spawn command itself—clients can only name a directory and a script label. This plugin is a natural fit for developers working in monorepo or multi-package setups who frequently need to start dev servers, run builds, or fire off maintenance scripts from within a DSH conversation, especially when those background tasks should stay visible to the agent.