dsh-update

Managing DeepSeek Harness versions used to mean opening a terminal for npm install or switching to DeepSeekDesk's native settings page — the web dashboard had no idea which build was running and offered no update path at all. dsh-harness-updater closes that gap: a single Settings → Install / Update panel shows the current version, install directory (with its detection source), Node and npm versions, listening port, and PID. Checking for updates reads the npm registry's dist-tags over plain HTTP, so it works without a local npm binary or even a network connection for the local-version display. When you are ready to upgrade, the primary button states the exact target version and its channel, install logs stream back in real time, and the status card refreshes the moment the job finishes.

Advanced options let you switch update channels (latest, next, alpha, or a pinned version), override the install directory, change the registry or npm path, and save any of these as defaults. Restarting Harness requires a two-step confirmation and relaunches the new instance with the same launch arguments; the log viewer scrubs tokens and sensitive keys before returning content to the browser. The plugin ships with zero runtime dependencies and zero build steps — the Node side uses only node:* built-ins and the browser side only require('react') — so after a single restart there is nothing else to maintain.

It is built for anyone who lives in the dsh web interface and wants the full update lifecycle — status, check, install, restart, inspect logs — without leaving the browser. It follows the same install strategy as DeepSeekDesk's HarnessInstaller, defaulting to the highest version across all dist-tags, and the UI always labels the target version and its source channel so an accidental alpha install is never ambiguous.