AI Agent Hub
Back to plugins
🧩

dsh-doctor-windows

admin-security Updated 2026.08.14

Run the following command in DeepSeek Harness:

dsh plugin install sublatesublate-design/dsh-doctor-windows

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

Run dsh plugin install sublatesublate-design/dsh-doctor-windows in your terminal to install; the source is available at https://github.com/sublatesublate-design/dsh-doctor-windows .

About this plugin

Running DeepSeek Harness on Windows introduces environment issues that are harder to spot than on Linux or macOS: whether the Koffi installation backing the native folder picker is intact, whether PowerShell discovery works correctly, and whether proxy settings take effect at Node startup. dsh-doctor-windows provides a human-only /doctor-windows diagnostic command so you can run a full Windows environment health check even when the model provider is completely unavailable.

The command covers six key dimensions: Harness and Node.js versions and architecture, current workspace read and write permissions, UTF-16 low-byte-zero characters (which can truncate paths in preview builds of the native folder picker), proxy environment variables and the NODE_USE_ENV_PROXY startup behavior, discovery and non-interactive startup verification of both PowerShell 7 and Windows PowerShell, and the integrity of the Koffi installation used by the native folder picker. It prints no proxy URLs or credential values, changes no settings, opens no folder dialogs, and makes no network requests. Pure read, pure report.

If you deploy or debug DeepSeek Harness on Windows, especially in enterprise intranets, multi-layer proxy setups, or mixed PowerShell version environments, this plugin helps you quickly surface the low-level issues that are otherwise hard to reproduce and saves you from piecemeal trial and error.

Use Cases

  • Diagnosing Windows runtime and environment issues when the model provider is offline
  • Troubleshooting Node.js proxy behavior in multi-layer enterprise networks
  • Native folder picker failing due to path truncation or Koffi installation corruption

Best For

  • Developers deploying or debugging DeepSeek Harness on Windows
  • Ops engineers running Harness in enterprise proxy environments
  • Users hitting PowerShell discovery or native component compatibility issues