dsh-clash-proxy

Many DeepSeek Harness users need instant access to domestic sites while also reaching international services reliably, yet the usual fix — a system-wide proxy or a separate Clash client — pollutes the entire runtime and adds ongoing maintenance. dsh-clash-proxy confines smart rule-splitting entirely within the Harness process tree: DSH native fetch calls, web search, MCP tools, and spawned pwsh, jobs, and workflow subprocesses inherit the proxy automatically, while the rest of the system stays untouched. Disabling or uninstalling restores environment variables and the runtime dispatcher with no leftovers.

The plugin ships a built-in rule engine bundled with roughly 110,000 domestic domain suffixes and IPv4/IPv6 ranges, paired with subscription nodes for automatic direct-versus-proxy routing. Supported transports include Shadowsocks AEAD, Trojan, VLESS with Reality, VMess, Hysteria2, and Socks5 / HTTP, all exposed over a single loopback port speaking both HTTP CONNECT and SOCKS5. The Web GUI handles subscription refresh, per-node latency tests, url-test / select / fallback group switching, and live traffic monitoring — no terminal required.

If your DSH workflow depends on LLM calls, MCP tools, or subprocess scripts that must hit both Baidu instantly and GitHub or Google steadily, and you would rather not maintain a separate system-level proxy client, dsh-clash-proxy is purpose-built for that: paste a subscription URL and you are up and running.