dsh-proxy

DSH's desktop and web clients issue LLM requests from the host Node process via undici's global fetch, which neither reads the Windows system proxy nor honours the HTTPS_PROXY environment variable, and the settings UI exposes no proxy option at all. When an API endpoint returns a 403 because Cloudflare blocks the source IP—common on mainland Chinese broadband—the only prior workaround was enabling Clash's TUN mode, which requires elevated privileges, takes over the entire network stack, and can conflict with everyday network configuration.

dsh-proxy takes a lighter approach: at load time it saves the current global dispatcher, then builds an undici ProxyAgent with a bypass list and installs it via setGlobalDispatcher. From that moment on, every global fetch in the process—model discovery, OpenAI SDK chat calls, the plugin marketplace, web search—exits through your designated HTTP proxy, while Clash or mihomo rules continue to split domestic and international traffic as usual. Configuration is deliberately minimal: enter the proxy host and port under Settings (default 127.0.0.1:7890, the Clash/mihomo mixed port), and changes apply immediately on save. Flipping the switch off restores direct connectivity at once, with no restart or uninstall. The built-in noProxy list lets loopback addresses through by default and supports domain-suffix wildcards. The plugin speaks HTTP/HTTPS proxy only; SOCKS5 users should point to their mixed port.

This plugin is built for anyone whose API endpoints are IP-blocked by Cloudflare or who must traverse a corporate proxy to reach overseas model providers, yet wants to avoid the system-level overhead of TUN mode. As long as DSH and the proxy client run on the same machine, dsh-proxy quietly funnels all host-process outbound traffic through the proxy in the background, so model lists load cleanly and conversations flow without a timeout in sight.