dsh-net-proxy-plugin

Running agent tasks in DeepSeek Harness from mainland China often means hitting timeouts on git clone, pnpm install, or web fetch when accessing overseas services. You may already have Clash or V2Ray running locally, yet dsh internal fetch calls and the subprocesses it spawns do not automatically pick up your proxy, and manually juggling environment variables is fragile and easy to forget to revert.

dsh-net-proxy-plugin takes a restrained approach: at startup it scans every existing proxy source on the system (environment variables, Windows/macOS/Linux system proxy settings, and common local ports such as 7890 and 10809), then probes connectivity to default targets (Google 204, GitHub). Only when direct access truly fails and a candidate proxy is reachable does it attach that proxy to the dsh fetch chain and the proxy environment variables, so that in-process requests and child processes like git and pnpm all benefit. When direct connectivity is fine the plugin stays completely silent; on uninstall it precisely restores the environment variables and the global dispatcher, leaving no residue.

It is designed for users in mainland China who already run a local proxy and want dsh web tools and agent subprocesses to benefit from it automatically. This is a safety net, not a default takeover: with no VPN, no proxy, or working direct connectivity, the plugin does absolutely nothing.