dsh-proxy — hot-swappable outbound proxy for every DSH request (manual / system / direct, zero restarts)

[tr1v3r]

I made a DSH plugin that routes every in-process outbound request — LLM providers, web_search / web_fetch, streamable-http MCP — through a proxy you can switch at runtime, without restarting dsh. One hot-reloaded settings section picks the strategy:

# ~/.config/dsh/settings.yaml
dsh-proxy:
  mode: manual        # direct | system | manual
  proxy: socks5://127.0.0.1:1080
  noProxy: [localhost, .internal.example]
  exportEnv: true

• manual — route through your proxy URL: http(s):// CONNECT or socks5:// (URL credentials supported, socks5h:// accepted), with a noProxy bypass list
• system — just follow the host: HTTP_PROXY/HTTPS_PROXY/ALL_PROXY/NO_PROXY env everywhere (socks ALL_PROXY included), falling back to the macOS System Settings network proxy (scutil --proxy) when env is unset; re-detected on every save
• direct — no proxy

Every save takes effect immediately — proxy on, off, re-pointed at another server, or switched between manual and system. The GIF above is a real recording walking all three; the full boot-verified flow (settings watcher → dispatcher swap → live fetch) is in the repo's probe.

How it works: DSH and pi-ai issue requests via globalThis.fetch, which reads undici's well-known global dispatcher slot. The plugin owns that slot.

• http(s):// → EnvHttpProxyAgent (CONNECT tunneling); socks5:// → undici's native Socks5ProxyAgent
• One shared noProxy matcher for both protocols (bare entries match host + dot-boundary subdomains, host:port pins a port, * bypasses all); ambient NO_PROXY/HTTP_PROXY env is deliberately ignored in manual mode so routing is fully settings-driven
• exportEnv (manual mode) mirrors the switch into child-process env — curl/git/stdio MCP servers spawned after a switch follow along; operator-set variables are never clobbered
• Invalid config keeps traffic direct and logs why; proxy credentials are redacted in logs

Known limits: Windows registry / PAC / Linux-desktop proxy detection not yet covered in system mode; pi-ai's Bedrock route manages its own proxying via AWS SDK env; the built-in browser host is a separate process and is not routed.

# in ~/.config/dsh/profiles/<name>/package.json
"dependencies": { "@tr1v3r/dsh-proxy": "^0.1.2" },
"dsh": { "profile": { "bundles": ["@deepseek-ai/dsh-base", "@tr1v3r/dsh-proxy"] } }

dsh plugin --profile <name> install --no-frozen-lockfile

Restart once to mount — after that, never again for switching.

• GitHub: https://github.com/tr1v3r/dsh-proxy
• npm: https://www.npmjs.com/package/@tr1v3r/dsh-proxy