DeepSeek Harness One-Click Setup

Problem

The dsh CLI for DeepSeek Harness does not install cleanly in the WorkBuddy Windows sandbox using common documentation. The environment has hard constraints: the npmjs registry is unreachable, npm cleanup can be blocked by a NODE_OPTIONS injected safe-delete shim, failed background installs can leave npm cache locks, and desktop shortcuts cannot be created through the usual PowerShell WScript.Shell COM path. Manual attempts can fail with ECONNRESET, EPERM, blocked COM instantiation, or a .lnk that does nothing on double-click.

How it works

The skill packages this flow into a concrete operating procedure:

• Install the CLI: prepare Node.js + npm and Python 3 with Pillow, then install dsh through the available mirror.
• Start the Web UI: serve the interface at http://127.0.0.1:3080 and configure the DeepSeek API key inside the UI.
• Optional desktop entry: generate a white whale .ico icon, create a .lnk using ctypes IShellLinkW, and verify that the target path, icon location, and working directory all resolve correctly.

The shortcut points to a launcher script so double-click starts the service and opens the browser.

Limits and notes

This workflow is tied to the WorkBuddy Windows sandbox, especially the registry.npmmirror.com mirror, fixed Node path, and sandbox security policies. It is not a general npm installation guide and does not replace DeepSeek Harness permissions, API, or security configuration. Before running it, check network mirror access, Python icon dependencies, stray npm processes, and cache lock state. Reusing the scripts in other Windows environments or restricted sandboxes may require rewriting paths, permissions, and COM assumptions.