AI Agent Hub
Back to plugins
🧩

dsh-plugin-proxy-env

admin-security Updated 2026.09.10

Run the following command in DeepSeek Harness:

dsh plugin install looeton/dsh-plugin-proxy-env

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install looeton/dsh-plugin-proxy-env in your terminal to install this plugin; the full source is at https://github.com/looeton/dsh-plugin-proxy-env

About this plugin

When running shell, git, npm, or python inside DSH, child processes often inherit no proxy variables at all. You end up running setx and restarting, or sprinkling exports into every script. Worse, when the proxy chain breaks, pinpointing which link failed is pure guesswork.

dsh-plugin-proxy-env writes HTTP_PROXY, HTTPS_PROXY, NODE_USE_ENV_PROXY, and NO_PROXY into the harness host process environment once at plugin load, so every subsequent spawn carries them. At startup it walks the chain nearest-first: port listening, CONNECT tunnel, DNS fake-ip detection, direct and proxied probes, then renders a single PASS / WARN / FAIL verdict with one fix suggestion, saved to report.json for the agent to read without any tool call.

Ideal for developers who rely on a local proxy (Clash, V2Ray, etc.) inside DSH to reach blocked sites—especially on Windows—where manual per-session proxy configuration is tedious and you want the agent to tell you, on its own, whether the proxy is actually working.

Use Cases

  • Child processes (shell, git, npm) inside DSH on Windows can't reach the local proxy automatically
  • The proxy chain breaks and you cannot tell which link failed
  • You want the agent to verify proxy availability at startup, on its own

Best For

  • Developers who rely on a local proxy (Clash, V2Ray) inside DSH to reach blocked sites
  • Windows users who want to skip setx-and-restart every session
  • Users who want the agent to self-diagnose its own network path