dsh-proxy-router

Once you boot dsh with http_proxy / https_proxy / all_proxy set, every outbound request is forced through the proxy. Domestic sites, LAN devices, and even the DeepSeek API all take an unnecessary detour, adding latency and cost.

dsh-proxy-router spins up a local routing proxy that intercepts all outbound traffic from the main-process fetch, the web_fetch tool, and bash subprocesses (curl, git, npm/pnpm), then applies a three-tier rule table per request to decide proxy vs. direct: a hot-reloadable local rules file, remote blocklists (clash-rules gfw and greatfire by default, auto-refreshed every 24 h), and a built-in seed list of roughly 140 high-frequency blocked domains. Loopback and LAN addresses always go direct. The settings page lets you change the upstream, default route, timeouts, fallback behaviour, and debug logging in real time with no dsh restart.

Built for dsh users who need both domestic and international resources in the same workflow. If your day mixes LLM API calls, web_search, MCP, and everyday domestic tooling, this plugin turns the proxy decision into a maintainable rule table instead of a blanket environment variable that punishes one side for the other.