dsh-launch-in-one-click

Starting a Harness service on Windows used to mean typing the right command, praying the port is free, and deciphering a wall of garbled text when the install terminal and the launch console disagree on code page. dsh-launch-in-one-click strips that ritual down to one double-click, and the part it cares about most is not whether it can start a server but whether it should.

Every time the generated .bat runs, it binds the target port and reads the response body as a fingerprint. If the port is free it launches Harness; if an existing Harness instance answers with its characteristic 401, the launcher refuses to start a second copy and points you to the URL already in use; if some other program holds the port it reports the owning PID instead of guessing. When a newer plugin build loads it rewrites the desktop file with the current template while preserving the port, workspace, and runner the user recorded. The launcher is fully self-contained: uninstall the plugin and the .bat keeps working with no plugin process behind it. Encoding is handled explicitly against the system OEM code page, with GBK double-byte trail-byte scanning and an automatic switch to UTF-8 when a path cannot be carried, so a Chinese Windows console and an English one both get a launcher that prints correctly.

This is built for Windows users who run DeepSeek Harness as a daily tool, want a single double-click to open the service page, and do not want a second instance silently failing on the port bind. If you maintain several workspaces, schedule the launcher through a task, or branch logic on its nine documented exit codes, the same file slots in without a wrapper script.