deepseekplugins

DeepSeek Harness plugin

dsh-wsl-net

DeepSeek Harness tool: diagnose WSL/Windows proxy, Node 24 fetch, and DeepSeek/npm reachability.

Tools & Capabilities
Jump to install

Source facts

Repository
173787247/dsh-wsl-net
Latest update
Aug 19, 2026
Category
Tools & Capabilities
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/173787247/dsh-wsl-net
Plugin: dsh-wsl-net
Author: 173787247

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer3 files
README.mdSource · read only

dsh-wsl-net

DeepSeek Harness tool plugin: net_doctor diagnoses why HTTPS works in the Windows browser but fails from the WSL agent.

和 dsh-wsl-env 互补：那个往 prompt 里写路径事实，这个在会话里跑一遍代理和连通性。

常见原因：Clash 在 Windows 上、HTTP_PROXY 指向 127.0.0.1，但 Node 24 的 fetch 默认不读代理变量，除非 NODE_USE_ENV_PROXY=1。

0.2.0 还会给 bash / npm 子进程补上 NODE_USE_ENV_PROXY=1，以及 Linux 下常见工具会读的小写 http_proxy / https_proxy 别名。dsh 进程自己的 fetch 仍要靠启动脚本里的 NODE_USE_ENV_PROXY=1。

Install

dsh plugin --profile web add github:173787247/dsh-wsl-net
# or a local checkout:
dsh plugin --profile web add /absolute/path/to/dsh-wsl-net

Restart dsh web. In a new session, Trajectory → SYSTEM → Tools should list net_doctor. Ask: 「检查一下现在 DeepSeek API 和 npm 通不通」.

To check child injection, ask bash to run:

node -e "console.log(process.env.NODE_USE_ENV_PROXY, process.env.http_proxy || process.env.HTTP_PROXY)"

Expect 1 and your proxy URL.

What it reports

  • HTTP_PROXY / HTTPS_PROXY / NO_PROXY
  • NODE_USE_ENV_PROXY
  • optional npm registry
  • GET probes: https://api.deepseek.com/ and the npm registry (status < 500 counts as reachable, including 401)
  • advice: what to restart or set; it does not guess a Clash port

Does not print API keys. Does not change your proxy settings or Clash port.

Topics

On GitHub, add dsh-plugin.

Config

Override the whole row in the profile cordis.patch.yml:

- id: dsh-wsl-net
  name: dsh-wsl-net
  config:
    timeoutMs: 20000
    probeTimeoutMs: 5000
    injectChildProxy: true
KeyDefaultMeaning
timeoutMs20000Tool timeout.
probeTimeoutMs5000Per-probe timeout.
injectChildProxytrueSet false to stop wrapping subprocess.spawn.
Back to searchOpen GitHub repository

More related plugins

View category