173787247/dsh-wsl-net

README 摘要

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 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: 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 : Key Default Meaning timeoutMs 20000 Tool timeout. probeTimeoutMs 5000 Per-probe timeout. injectChildProxy…

分类