dsh-proxy

Juggling multiple LLM routes, web search, and streamable-http MCP while hopping between corporate Wi-Fi, home broadband, and mobile hotspots means a restart every time the proxy changes. dsh-proxy intercepts every in-process outbound request that flows through globalThis.fetch and reroutes it through an HTTP(S) CONNECT or SOCKS5 proxy of your choosing. Three hot-reloadable modes—direct, system, and manual—let you flip routing by editing one section of settings.yaml, with zero restarts and stale keep-alive connections drained within 30 seconds.

By owning the undici global dispatcher slot, the plugin covers pi-ai LLM calls, the official DeepSeek route, web_search / web_fetch, and streamable-http MCP servers under a single configuration. With exportEnv enabled (the default), HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY are also exported into the dsh process so child processes spawned after the switch—curl and git in bash-tool, stdio MCP servers—inheriting the same proxy. noProxy rules follow undici-style matcher semantics shared by both the HTTP and SOCKS5 paths, and in manual mode ambient environment variables are deliberately ignored so the settings section is the single source of truth.

Ideal for developers and researchers who work across multiple network environments, who want every piece of DSH outbound traffic including subprocesses to follow one proxy, and who dislike the restart-export-restart cycle. dsh-proxy does not replace a system-wide proxy tool; it consolidates the in-DSH proxy decision into one hot-reloaded config block, making a switch as light as flipping a toggle.