dsh-http-proxy

Your local network cannot reach model APIs directly, yet a proxy server can — a friction many developers hit daily. dsh-http-proxy solves exactly this: it routes only model-inference traffic through a proxy while keeping web search, scraping, MCP, and every other request on a clean direct connection. At runtime it wraps globalThis.fetch in a thin layer and inspects the target domain to pick the right path, touching zero lines of DSH source code. Uninstall it and fetch reverts to the original with nothing left behind.

It speaks HTTP, SOCKS4, SOCKS4a, SOCKS5, and SOCKS5h, covering most real-world proxy setups. Configuration is offered through two equally effective paths: the recommended DSH settings panel, where you type in a proxy URL and optionally whitelist or blacklist specific domains (changes take effect on the very next request, no restart needed), and an environment variable for quick, file-less trials. The default auto-detected model domain list includes api.deepseek.com, anything pointed to by DEEPSEEK_BASE_URL, and custom gateways registered in pi-ai, so there is no need to enumerate them manually.

This plugin is a natural fit for developers whose networks block direct access to model APIs while a proxy channel is available. If you want surgical control over which domains traverse the proxy and which stay direct, or you simply prefer not to alter global network settings for a single inference workload, dsh-http-proxy keeps the proxy scope tight around model reasoning and lets everything else flow untouched.