dsh-doctor

Once DeepSeek Harness is up and running, environment hiccups—leftover processes holding a port, session files quietly ballooning past several hundred megabytes, a Node version that no longer fits—can take a lot of digging to track down. dsh-doctor collapses all of those scattered checks into a single /doctor command that you invoke inside an existing Web, TUI, or custom profile, with no extra UI or standalone process required.

On each run the plugin reads DSH_HOME, the profile name, and the bundle manifest; validates that Node and dsh fall within the supported ranges; probes the default port 3080 (or whatever --port specifies) to see who is LISTENING; walks the Windows process tree to flag node or dsh processes that likely belong to the current profile (it marks ownership and never kills anything); and stats every .jsonl and .zstd file under the sessions directory, calling out any that exceed the 50 MiB threshold with path and byte count. Everything is folded into a Markdown report with a PASS, WARN, or FAIL verdict plus a matching JSON file, written to the logs directory and ready to paste into GitHub Discussions.

It is built for developers who already use DeepSeek Harness and hit the occasional stuck process, port conflict, session bloat, or version mismatch. The plugin does not replace a desktop shell or a TUI, does not modify any official package, and acts as a lightweight diagnostic bundle: install it, run the command, read the verdict, and you are done.