AI Agent Hub
Back to plugins
🤖

dsh-windows-native

Model Inference Updated 2026.08.31

Run the following command in DeepSeek Harness:

dsh plugin install lucifergzsz414/dsh-windows-native

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install lucifergzsz414/dsh-windows-native in your terminal to install the plugin; the source repository is https://github.com/lucifergzsz414/dsh-windows-native .

About this plugin

Running DeepSeek Harness straight on Windows PowerShell — no WSL — quickly reveals the same handful of mistakes the agent keeps making: chaining commands with &&, trusting mojibake Chinese output as if the data itself were corrupted, assuming a junction was created because the exit code was zero. dsh-windows-native is a system-prompt injection plugin that lays every one of these traps out up front so the agent stops guessing.

It covers roughly fifteen real Windows/PowerShell pitfalls, each one a scar on the author's machine: use semicolons instead of && or ||, the console is not UTF-8 so non-ASCII output looks wrong even when the data is fine, multi-line non-ASCII text should be written to a file before execution, Python subprocess needs an explicit encoding, .bat script bodies must stay pure ASCII, Set-Content defaults to the system ANSI codepage, nested SSH quotes can hang silently for minutes, NUL is reserved so > /dev/null leaves a literal file behind, Docker drive-letter colons can mis-split a mount and the container still reports healthy, native .node bindings crash on Linux, killing the outer process does not free the port, and hiding a Scheduled Task actually requires pythonw.exe with CREATE_NO_WINDOW. None of it is theoretical.

It is aimed at developers who run DeepSeek Harness natively in Windows PowerShell rather than inside WSL, particularly in Chinese-language environments where GBK and UTF-8 constantly collide. The plugin bridges no environment and changes no configuration; it simply writes hard-won experience into the agent's context so it stops repeating the mistakes you already made.

Use Cases

  • Running DSH natively in Windows PowerShell without falling into Linux syntax traps
  • Resolving GBK vs UTF-8 encoding collisions that mangle Chinese output on a Windows console
  • Correcting Windows-specific failures in Docker mounts, Python subprocesses, and nested SSH quotes

Best For

  • Developers running DSH natively in Windows PowerShell rather than inside WSL
  • Users on Chinese Windows installations who constantly hit GBK/UTF-8 encoding collisions
  • Users who want their agent to stop repeating the same Windows-specific mistakes on every run