DeepSeek Harness (DSH) runs in a Node.js environment and, by default, neither reads the operating system’s proxy settings nor trusts the system certificate store. As a result, even if your browser can access the internet normally through a proxy accelerator, DSH may fail to connect to the network because of two independent barriers: routing and certificate trust.

dsh-system-net is a plugin designed to solve the above problems. It allows DSH to read the operating system’s proxy configuration and merge the system certificate store at runtime, eliminating the need to set environment variables or export certificate files.

Core Features

This plugin mainly addresses the following issues:

  • Routes traffic through the operating system proxy: DSH no longer relies on environment variables; it reads Windows system proxy settings directly.
  • Trusts the operating system certificate store: DSH merges the operating system certificate store, resolving TLS verification failures caused by self-signed CAs.
  • Zero configuration and maintenance-free: No certificate export, no environment variables, and no restart required after installation; the configuration is re-detected on every startup.

Installation and Enabling

The plugin is distributed via GitHub and installed using the github: prefix.

dsh plugin --profile web add github:chickmat/dsh-system-net

If there is no global dsh command in the environment, you can use:

npx -y @deepseek-ai/dsh plugin --profile web add github:chickmat/dsh-system-net

The plugin is applied automatically when DSH loads. Each subsequent startup re-detects and applies the configuration, requiring no manual intervention.

Prerequisites and Applicable Scenarios

Environment Requirements

  • DSH version: >= 0.2.0-rc.2
  • Node.js version: >= 22.19 or >= 24.5 (23.x is not supported)
  • Platform: Windows only
  • Accelerator mode: The accelerator must run in “system proxy mode” (i.e., write the proxy address into Windows Internet Options)

Applicable Scenarios

  • When using proxy accelerators such as Watt Toolkit, Steam++, or dev-sidecar that enable a TLS man-in-the-middle proxy.
  • When the browser can access the internet normally, but DSH experiences connection timeouts or certificate verification errors.

Notes

  1. Startup order: Start the accelerator first, then start DSH. The plugin detects the system proxy at startup.
  2. Mode limitations: The plugin does not support PAC automatic configuration parsing. If the accelerator uses hosts file rewriting or TUN virtual adapter mode, this plugin is usually not required.
  3. Single proxy conflicts: The system proxy usually has only one global slot. Running multiple tools that claim system proxy simultaneously may conflict with each other.

Verification and Status

After installing and restarting DSH, check the status file $DSH_HOME/system-net-status.json (default ~/.dsh/system-net-status.json).

Key field descriptions:

  • proxy.source: Proxy source. system-proxy indicates that the system proxy was successfully read.
  • cert.systemCount: Number of certificates read from the operating system certificate store.
  • selfCheck: Self-check request result. 200 indicates the network path is working.

Uninstall

Use the following command to uninstall:

dsh plugin --profile web remove dsh-system-net

The plugin leaves no residual files. After a restart, Node.js default behavior is restored.

Summary

dsh-system-net takes over routing and the certificate trust chain at runtime, resolving the incompatibility between Node.js default behavior and proxy accelerators. It simplifies the configuration process and is suitable for developers who need to use system-level proxy tools in a Windows environment.