Bundle
dsh-netassist
Network & proxy assistant for DeepSeek Harness (dsh): one-shot GitHub connectivity check, system proxy status, proxy port probing, full diag chain (DNS/TCP/HTTP) and hosts-file conflict scan — built from real-world China-network experience.
- Source
- Edge-Echo
- stars
- 1 stars
- License
- MIT
- Updated
- Updated yesterday
Readme
# dsh-netassist  [](https://www.npmjs.com/package/dsh-netassist) [](https://www.npmjs.com/package/dsh-netassist) [](LICENSE) [](https://github.com/Edge-Echo/dsh-netassist) **Network & proxy assistant for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (dsh).** Born from real-world China-network pain: GitHub flaky, proxies everywhere, hosts conflicts, TUN vs system proxy confusion. This plugin gives your agent one-shot answers to "is GitHub reachable?", "what proxy is my system using?", "is my proxy port alive?", plus a full diagnosis chain — all read-only, all injection-safe. > 中文文档见 [README.zh.md](README.zh.md)。 ## Tools | Tool | What it answers | |---|---| | `net_github_status` | Is GitHub reachable right now? (DNS + TCP 443) | | `net_proxy_status` | System proxy config: registry `ProxyEnable/ProxyServer/ProxyOverride` + proxy env vars | | `net_proxy_probe` | Which common local proxy ports are alive? (default 10808/10809/7890/7897/8888/1080) | | `net_diag` | Full chain for any host: DNS → TCP → HTTPS status code | | `net_hosts_check` | GitHub entries pinned in the hosts file (proxy conflict scan) | ## Install ```sh dsh plugin --profile web add dsh-netassist dsh web # restart ``` Then ask your agent: - "check if github.com is reachable" → `net_github_status` - "what proxy is my system using?" → `net_proxy_status` - "is my proxy running?" → `net_proxy_probe` - "why can't I reach api.example.com:8443?" → `net_diag` host=api.example.com port=8443 - "any github entries in my hosts?" → `net_hosts_check` ## How it works Every tool runs a short read-only PowerShell snippet through `powershell.exe -NoProfile -NonInteractive`. All user input crosses the script boundary as **Base64** — injection-proof by construction. No writes, no admin rights, no dependencies. - Config: `psTimeoutMs` (default 25000) — per-call PowerShell timeout, settable in your profile's `cordis.patch.yml` under the `netassist` entry. - Windows-only: tools fail loudly on non-Windows platforms. ## Real-world example (this machine) ``` net_github_status → DNS: 20.205.243.166, TCP 443: OPEN net_proxy_status → ProxyEnable: 1, ProxyServer: 127.0.0.1:10808 net_proxy_probe → 10808 OPEN, 10809/7890/7897/8888/1080 CLOSED net_hosts_check → no github entries in hosts (clean) ``` ## Troubleshooting - "PowerShell failed": usually execution-policy or anti-virus interference. The plugin uses `-NoProfile -NonInteractive`; check `Get-ExecutionPolicy` — it does not require RemoteSigned. - Port probes use a 5s connect timeout each, so a full probe takes ~5-10s worst case. ## Links - npm: <https://www.npmjs.com/package/dsh-netassist> - GitHub: <https://github.com/Edge-Echo/dsh-netassist> - License: MIT
Install
dsh plugin --profile web add github:Edge-Echo/dsh-netassist
Profile: web
With the hub plugin installed, ask your agent to install it by name — it resolves the same plan shown here.
dsh plugin --profile web add github:stvlynn/dsh.fish#path:packages/dsh-plugin-hub
install dsh-netassist from the hub
- This package builds from source on install. pnpm will ask you to allow its build script — that is permission to run the package’s code on your machine, outside the agent sandbox. Only allow sources you trust.
- This source has no pinned commit, so a later push upstream changes what installs. Prefer pinning a commit.