copylee711/dsh-proxy
Global and per-provider network proxy settings for DeepSeek Harness, applied on save with no restart.
@copylee/dsh-proxy adds a network proxy to DeepSeek Harness with both a global mode — where model requests, web search, web fetch, HTTP MCP and the commands the agent runs all go through the proxy — and a per-provider mode, where each model provider can follow global, use its own proxy or force direct. Settings apply on save rather than after a restart, and hosts to bypass are given one per line (subdomains match; localhost/127.0.0.1 are always direct). Its menus follow the author's dsh-free-search floating-card interaction, with full keyboard support.
Install
dsh plugin --profile web add @copylee/dsh-proxyCopied verbatim from the README's Install block. The README warns: 'Keep the @copylee/ scope. The unscoped dsh-proxy and dsh-network-proxy packages on npm belong to other people and are unrelated.' It also gives a github: form (dsh plugin --profile web add github:copylee711/dsh-proxy) and says built output is committed, so no build script or allowBuilds entry is needed.
Compatibility
The README says the plugin adds a Network proxy page in Settings that applies on save, so no dsh restart is needed; the precedence is provider setting > global proxy > HTTP(S)_PROXY from launch. The global selector offers Off, System proxy (auto-detect) and Manual proxy, and detection tries HTTPS_PROXY / HTTP_PROXY / ALL_PROXY in that order.
Details
- Repo: copylee711/dsh-proxy
- Category: Infrastructure & Deployment
- Stars: 2
- Version: GitHub repo copylee711/dsh-proxy; npm package @copylee/dsh-proxy at 0.4.5 (registry check 2026-10-07).
FAQ
- Do I need to restart dsh after changing the proxy?
- No — the README says the settings apply on save, so no dsh restart is needed.
- Which proxy setting wins?
- The README states the precedence: provider setting > global proxy > HTTP(S)_PROXY from launch.
Alternatives
flymysql/dsh-remote · dataelement/dsh-desktop · feibi-mochi/deepseek-harness-control-center