DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Windows Native — DSH Plugin for DeepSeek Harness
← Plugins
W

dsh-windows-native

Windows Native

Tells DeepSeek Harness the shell rules for native Windows (no WSL) — PowerShell syntax, console encoding, junction/file-lock gotchas.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:lucifergzsz414/dsh-windows-native#f98a7b25e51d9e3f6dc85aa0c3c33cd278499899
READMECompatibilityVersions

Compatibility and provenance

Windows Native is published as dsh-windows-native and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
8/31/2026

Versions

0.1.0stable
8/31/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
8/31/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in

Related plugins

More verified plugins in developer-tools.

Web App@deepseek-ai/dsh-web-appThe dsh browser-surface bundle: the web patch layer over dsh-base plus the runtime glue plugin (frontend dist serving, web-surface prompt, bash runtime variables, URL line)Sdk Minimal@deepseek-ai/dsh-sdk-minimalThe standalone minimal SDK profile bundle: JSON-RPC, one DeepSeek adapter, persistent shell, and JSONL sessionsSdk App@deepseek-ai/dsh-sdk-appThe dsh SDK profile bundle: stdio JSON-RPC serving and process lifecycle over dsh-baseSubagent Codex@deepseek-ai/dsh-subagent-codexOne-shot Codex subagent provider over the official app-server protocol

README

dsh-windows-native

I run DeepSeek Harness straight on Windows — no WSL, just PowerShell. Every WSL & Windows Interop plugin on the dsh-plugin list assumes you're bridging out from WSL, so none of them help here. Meanwhile the agent kept doing the same handful of things wrong: chaining commands with && (PowerShell 5.1 doesn't have it), printing Chinese text that comes back as mojibake, quietly creating a junction that Windows then refuses and nobody notices. This plugin just tells it up front so it stops guessing.

It's a system-prompt injection, nothing fancier. Copy-pasted the structure from dsh-wsl-env since that plugin already does the WSL side of the same idea well.

What it tells the agent

  • PowerShell has no && / || — use ;, or A; if ($?) { B }
  • The console usually isn't UTF-8, so Chinese/non-ASCII output can get mangled even though the actual data is fine — don't trust what you see printed
  • Don't feed multi-line non-ASCII text through an inline heredoc or -c "..." — write it to a file first, then run the file
  • .bat file contents have to stay ASCII (cmd.exe pre-scans them and can corrupt UTF-8/GBK before anything runs — filenames are fine, the script body isn't)
  • A junction or symlink can fail silently without admin rights / Developer Mode — check it actually exists after creating it, don't just trust the exit code
  • A file open in Word/Excel/WPS throws a plain PermissionError on write. That's not corruption, don't force-retry the same filename
  • Killing the outer process (a task runner, a job wrapper) doesn't free the port if the real node/python process underneath is still alive — you end up hitting a stale server and think your fix didn't work. Find the real PID and kill that
  • If you need a Scheduled Task to run something invisibly, -WindowStyle Hidden still flashes a console window for a moment. Launch it through pythonw.exe with CREATE_NO_WINDOW instead

None of this is theoretical — every line above is something that actually went wrong on this machine at some point.

Install

dsh plugin add dsh-windows-native

Config

when: windows   # inject only on native win32 (default), or "always"
order: 15
extraNotes: ""   # your own notes, appended after the built-in list

Status

Early, and the list is exactly as long as my own scar tissue — not a survey of every Windows footgun that exists. If you hit something this plugin should have warned you about, open a PR with the actual failure you saw, not a guess at what might go wrong.