Back to directory

dsh-win32

Curated pickMaintenance: Active

sjh9714/dsh-win32

Fix and diagnose DeepSeek Harness on native Windows. Official PowerShell, Workspace Write, shortcuts, and legacy preset repair. No WSL.

View on GitHubHomepage
$ npx dsh-win32 setup

31

stars

2

forks

TypeScript

Language

MIT

License

2026-08-15

Created

2026-09-05

Last push

A native-Windows repair and verification toolkit for DeepSeek Harness: one-command setup, proven-safe known-failure fixes, a desktop shortcut, and a model-free `verify` acceptance run against your installed DSH stack.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-09-06

License

MIT

01What can it help you accomplish?

  • Repair and diagnose DeepSeek Harness on native Windows (no WSL)

    A verified official stack, known Windows failures fixed with proven-safe repairs, and a DeepSeek Harness desktop shortcut

    Windows users running DeepSeek Harness who hit launch, ACL, or PowerShell failures and want a repair that does not touch the official profile/preset

  • Prove an installed DSH stack actually works via a model-free acceptance run

    A pass/fail report that live-tests PowerShell 7, PTY state retention, Workspace Write policy, and Windows ACL confinement

    Windows users and CI pipelines that need live evidence the installed PowerShell/Workspace Write/ACL components work without a model request or API key

02How to install into DeepSeek Harness

Prerequisites

  • Native Windows and a DSH-supported Node release are required; Node 23 is explicitly unsupported.
  • An installed `@deepseek-ai/dsh` (DeepSeek Harness) — `verify` runs against an already installed dependency tree.
  • PowerShell 7 is recommended. dsh-win32 does not install it.

Installation steps

  1. 01

    `npx dsh-win32 setup` — checks the official persistent PowerShell and Workspace Write packages and creates a DeepSeek Harness desktop shortcut.

    $ npx dsh-win32 setup

  2. 02

    `npx dsh-win32 setup --profile desktop --no-shortcut` — use a different profile without creating a shortcut.

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

  3. 03

    `npx dsh-win32 setup --legacy` — repair the previous Git Bash / busybox presets.

    $ npx dsh-win32 setup --legacy

Verify the integration

  • `npx dsh-win32 verify` — model- and API-key-free acceptance run of the installed stack.
  • `npx dsh-win32 verify --json` — same check with machine-readable output.

03DSH integration and capability boundaries

DSH integrationNative runtime

Repairs and verifies the official native Windows DSH stack (persistent PowerShell + Windows ACL sandbox) directly — no WSL

  • Official stack check & safe repair

    an installed `@deepseek-ai/dsh` on Windowsknown Windows failures fixed with proven-safe repairs; profile left on the stock Minimal preset

  • Desktop shortcut

    the Web profile of an installed DSHa `DeepSeek Harness` desktop shortcut

  • Live verification (`verify`)

    an already installed `@deepseek-ai/dsh` dependency treea model- and API-key-free acceptance report of the PowerShell/Workspace Write/ACL components

  • Doctor & koffi fix

    the published DSH Windows package contract and installed koffi runtimes`doctor` JSON (`dsh-doctor/v1`) plus `fix` that repairs only known-broken koffi versions

  • Legacy preset repair

    DSH rc.6 and older (Git Bash / busybox presets)`setup --legacy` / `doctor --legacy` for the previous Windows presets

04Who is it for? When not to use it?

Good for

  • Windows users running DeepSeek Harness who hit launch, ACL, or PowerShell failures and want a repair that does not touch the official profile/preset
  • Windows users and CI pipelines that need live evidence the installed PowerShell/Workspace Write/ACL components work without a model request or API key

Not for

  • Requires native Windows and a DSH-supported Node release; Node 23 is explicitly unsupported. PowerShell 7 is recommended but is not installed by dsh-win32.
  • dsh-win32 fixes DSH on native Windows only and does not use WSL; it also will not install Git, PowerShell, busybox, WSL, or another DSH bundle on the current path.
  • The legacy Git Bash preset needs `danger-full-access`, which removes the normal Windows ACL confinement.
  • Running `verify` inside another Workspace Write / Windows ACL sandbox can stall before PowerShell launches; approve one unsandboxed/full-access execution for this verify command only.

05Compatibility, maintenance and safety notes

  • Requires native Windows and a DSH-supported Node release; Node 23 is explicitly unsupported. PowerShell 7 is recommended but is not installed by dsh-win32.
  • dsh-win32 fixes DSH on native Windows only and does not use WSL; it also will not install Git, PowerShell, busybox, WSL, or another DSH bundle on the current path.
  • The legacy Git Bash preset needs `danger-full-access`, which removes the normal Windows ACL confinement.
  • Running `verify` inside another Workspace Write / Windows ACL sandbox can stall before PowerShell launches; approve one unsandboxed/full-access execution for this verify command only.
Not specified by the authorNot specified by the authorv0.17.7

readme_verified

06Frequently asked questions

Do I need WSL to run dsh-win32?

No. dsh-win32 fixes DeepSeek Harness on native Windows and explicitly does not use WSL — it does not install Git, PowerShell, busybox, WSL, or another DSH bundle on the current path.

What does `npx dsh-win32 setup` do?

It checks the official persistent PowerShell and Workspace Write packages, creates a DeepSeek Harness desktop shortcut, and leaves the profile on the stock Minimal preset. PowerShell 7 is recommended but dsh-win32 does not install it.

How is `verify` different from `doctor`?

`doctor` verifies the published DSH Windows package contract and checks local failures from package metadata. `verify` is a model- and API-key-free acceptance run against your already installed `@deepseek-ai/dsh` dependency tree, live-testing the PowerShell/Workspace Write/ACL components.

Does `verify` need an API key or model access?

No. `verify` is a model- and API-key-free acceptance run that tests the installed stack only; it does not make a model request or use registry metadata as proof.

What Windows and Node versions are supported?

Native Windows and a DSH-supported Node release are required; Node 23 is explicitly unsupported. PowerShell 7 is recommended and is not installed by dsh-win32.

08Data and sources

  • Author-claimedgithub.com7401db4567f9…

    Current DeepSeek Harness already includes persistent PowerShell and a Windows ACL sandbox.

  • Author-claimedgithub.com7401db4567f9…

    **Official PowerShell. Workspace Write. One command.**

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-06. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.