Preface

DeepSeek Harness (DSH) on Windows relies on the coordinated operation of components such as the official PowerShell persistent terminal, Workspace Write policy, and Windows ACL sandbox. Common issues encountered in actual deployments include: PowerShell 7 or koffi runtime anomalies, mismatches between presets and the official stack, missing desktop shortcuts, and older DSH versions still using Git Bash / busybox paths. Troubleshooting these faults on native Windows without WSL typically requires cross-referencing multiple package contracts.

Below, we introduce the community plugin dsh-win32 (maintainer: sjh9714, SkillHub category: Workflow). It uses a single PowerShell command to check the official stack, diagnose known Windows faults, apply provably safe fixes, and optionally create desktop shortcuts. It does not install Git, PowerShell, busybox, WSL, or another DSH bundle.

What This Is

dsh-win32 is a repair and diagnostic tool for DSH on native Windows, currently at npm version 0.17.0, MIT license, GitHub repository sjh9714/dsh-win32 (17 stars, 2 forks). Directory page: SkillHub · sjh9714/dsh-win32.

Current DSH already includes persistent PowerShell and Windows ACL sandbox; dsh-win32 builds upon this to verify official component contracts, locate known local faults, apply verifiable safe fixes, and guide subsequent steps for the first session.

Core Features

setup: One-click Check and Configuration

setup will:

  1. Check the latest published DSH Windows package contract
  2. Check PowerShell 7 and known corrupted koffi runtime
  3. Create a DeepSeek Harness desktop shortcut for the Web profile
  4. Keep official profiles and presets unchanged
  5. Output clear subsequent steps for the first session

After completion, open DSH, add a workspace, select the official Minimal preset, and keep Workspace Write enabled.

verify: On-site Acceptance Test for Installed Stack

verify runs against the dependency tree of an installed @deepseek-ai/dsh, does not rely on registry metadata as proof, and requires no model or API key. It invokes the persistent pwsh tool through official terminal, subprocess, Workspace Write policy, and Windows ACL sandbox components in an isolated temporary home and workspace.

Passing requires meeting multiple on-site observations, including: 64-bit PowerShell 7 starts normally; two pwsh invocations maintain the same PTY, working directory, and environment; read/write content within the workspace is consistent; the sandbox rejects out-of-bounds writes and the shell recovers; cancel and replace invocation behaviors are normal; temporary resources are all cleaned up. This command does not load or modify user DSH profiles, configurations, workspaces, or PowerShell profiles.

Note the boundary: verify validates component chain acceptance, does not launch a full stock Minimal host/preset, and does not initiate model requests, so it cannot be equated to proof of an end-to-end stock session.

doctor and fix: Diagnosis and Safe Repair

  • doctor: Verifies the published DSH Windows package contract and checks local Windows faults; JSON output follows the dsh-doctor/v1 envelope format
  • fix: Only repairs installed koffi versions that are known corrupted or fail to load at runtime, and re-verifies loading after repair

doctor examines published metadata; use verify when on-site evidence of the installed stack is needed.

legacy: Older DSH Presets

DSH rc.6 and earlier versions did not come with the current official PowerShell stack. Using --legacy still allows access to Git Bash and busybox presets: Git Bash preset requires danger-full-access; busybox preset can run under Workspace Write. Neither path automatically installs Git.

Installation and Activation

The plugin is categorized as Workflow in SkillHub and can be run directly via CLI with npm (no global installation required). Node requirement is ^22.19.0 || >=24.0.0; Node 23 is explicitly not supported. It must be executed on native Windows with a DSH-supported Node version.

First, perform an environment check, then run setup:

npx dsh-win32 setup

This command will not install PowerShell 7 for you; the official recommendation is to have PowerShell 7 installed, but the plugin itself does not handle installation.

If using the desktop profile and not needing a shortcut:

npx dsh-win32 setup --profile desktop --no-shortcut

--sandboxed is still accepted by older scripts; current DSH already provides a sandbox, so this flag no longer produces additional changes.

Typical Usage

On-site Acceptance Test for Installed Stack

npx dsh-win32 verify
npx dsh-win32 verify --json

Diagnosis and Repair of koffi

npx dsh-win32 doctor
npx dsh-win32 doctor --json
npx dsh-win32 fix

Older DSH Paths

npx dsh-win32 setup --legacy
npx dsh-win32 setup --legacy --sandboxed
npx dsh-win32 doctor --legacy

After completing the above steps, if verify passes, it can be considered that the official PowerShell persistence, Workspace Write, and Windows ACL sandbox are working correctly on the local component chain; if issues persist, use doctor --json to cross-reference the dsh-doctor/v1 output for further troubleshooting.

Applicable Scenarios and Notes

Who It’s For

  • Using DSH on native Windows without relying on WSL
  • Needing to verify that the official PowerShell + Workspace Write + sandbox stack works according to contract
  • Encountering koffi runtime load failures, or still maintaining older DSH rc.6 and earlier legacy presets

Usage Notes

  1. The plugin runs with the permissions of the current DSH process; please read the GitHub source code and MIT license before installation or execution to ensure behavior meets expectations
  2. verify will fail and retain the isolation snapshot if it cannot confirm whether the worker and its child processes remain isolated due to timeout or output limits, rather than deleting files when processes might still be active
  3. Legacy busybox sessions use ash instead of Bash; editing legacy-encoded files will write in UTF-8
  4. Before upstream Windows path issues are fixed, in legacy scenarios, C:\tmp should be considered outside the expected write perimeter
  5. SkillHub is an independent DSH plugin community directory, with no official affiliation to DeepSeek / High-Flyer; the DSH ecosystem follows an “everything is a plugin” philosophy, and this tool is one of the workflow aids for Windows

Conclusion

dsh-win32 converges common DSH faults on Windows into four commands: setup, verify, doctor, fix: checking the official stack, on-site acceptance of the component chain, diagnosing metadata and local faults, and safely repairing koffi. It doesn’t install WSL and doesn’t bundle Git or PowerShell.

  • Directory page: https://www.skillhub.cn/plugins/sjh9714/dsh-win32
  • GitHub: https://github.com/sjh9714/dsh-win32