@yangzhe1991/dsh-proxy-router
DSH 插件：本地分流代理 + Web 设置页——只有规则命中的被墙域名走上游代理，其余（国内/内网/未知）直连；上游地址、清单、超时等参数可直接在设置中修改，实时生效、无需重启，并带有运行状态面板
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @yangzhe1991/dsh-proxy-router@0.1.1Proxy Router 以 @yangzhe1991/dsh-proxy-router 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →A routing-proxy plugin for DSH (DeepSeek Harness): only rule-matched blocked domains go through the upstream proxy — everything else (domestic sites, LAN addresses, unknown hosts) connects directly. Its settings live in the Web settings page.
The motivation is mundane: once you start dsh with export https_proxy=... http_proxy=... all_proxy=..., even api.deepseek.com and www.baidu.com take a detour through the proxy. This plugin turns "when should this go through the proxy" into a maintainable rule table, and "who is the upstream" into a setting you can change any time.
Everything outbound first hits the plugin's local routing proxy, which then decides where it goes:
| Outbound source | Notes |
|---|---|
Main-process fetch() | LLM API (api.deepseek.com), web_search, MCP, plugin HTTP calls |
web_fetch tool | shares one policy with the main process via the host's proxyRouteFor() |
| bash subprocesses | curl, git, npm/pnpm — inherit the same route through http_proxy + NODE_USE_ENV_PROXY |
DSH main process fetch / web_fetch / bash subprocesses
│ the plugin repoints the host's http(s) proxy at the local router
▼
Local routing proxy (built in, bound to 127.0.0.1:17890)
├── matches a proxy rule → upstream proxy (the address from the settings page)
└── everything else (default) → direct connection
Three rule layers, first match wins:
~/.dsh/proxy-router/rules.txt) — your own additions/removals, hot-reloadedLoyalsoldier/clash-rules gfw.txt + greatfire.txt via jsDelivr, cached, refreshed every 24h)defaultRoute (default: direct)Loopback and LAN addresses always go direct (127.0.0.0/8, 10/8, 172.16/12, 192.168/16, 169.254/16, 100.64/10, IPv6 ULA/link-local, plus single-label hostnames such as nas) — they are never handed to the upstream proxy.
dsh plugin --profile web add @yangzhe1991/dsh-proxy-router
Then restart dsh web.
For local development, install with
link:: set"@yangzhe1991/dsh-proxy-router": "link:/path/to/repo"in~/.dsh/profiles/web, runpnpm install, restart.
After the restart, open Settings → Plugins → Plugin configuration and expand the "代理分流 (proxy-router)" card:
| Field | Meaning |
|---|---|
| Upstream proxy | e.g. http://192.168.3.47:12801; empty falls back to https_proxy / http_proxy from the launch environment |
| Route when nothing matches | direct (recommended) or proxy |
| Remote blocklists | one URL per line; clear the box to load none |
| List refresh period | hours; 0 keeps whatever cache exists |
| Local router bind address | e.g. 127.0.0.1:17890 |
| Connect timeout | milliseconds; applies to connection setup only, never to streaming responses |
| Fall back to direct when the upstream fails | retry directly when the proxied connection cannot be established |
| Log every routing decision | verbose per-request lines on the host's stderr |
Below the fields sits a live status panel: bind address, upstream and where it came from, whether the host policy was taken over (and whether bash subprocesses are routed), rule counts, hit statistics, the local rules file path, and each remote list's size and refresh time.
Worth knowing:
proxy-router: section of $DSH_HOME/settings.yaml (default ~/.dsh/settings.yaml). Each field has a "reset" action that removes the user-layer entry, falling back to the composition default.⚠️ Once the upstream is configured here, stop exporting
http_proxy/https_proxy/all_proxyin your launch command. The host freezes those values into a snapshot at boot and hands it to bash subprocesses, which take priority — socurl/git/npmwould bypass the router and talk to your exported upstream directly. The plugin detects this, warns loudly in the log, and marks bash subprocesses as "direct to upstream (bypassing the router)" in the status panel.
The settings page writes the user layer, which resolves above the profile's composition config (the deployment default). Put machine-wide defaults there:
# ~/.dsh/profiles/web/cordis.patch.yml
- id: proxy-router
config:
upstream: http://192.168.3.47:12801
debug: false
Two path-shaped fields stay composition-only (they are deployment facts, not preferences):
| Field | Default | Meaning |
|---|---|---|
stateDir | ~/.dsh/proxy-router | cache and default rules file location |
rulesFile | <stateDir>/rules.txt | local rules file path |
Every settings field may also be written here as a default; in composition config lists accepts plain URL strings or { name, url, route } objects (the settings page flattens them to a URL list).
The file lives at ~/.dsh/proxy-router/rules.txt; a commented template is created on first run. Edits take effect immediately — no dsh restart. The settings page shows the path and the current rule count, but editing happens in your editor.
# one rule per line, '#' starts a comment; first match wins
proxy: some-blocked-site.com # this domain and all subdomains → upstream proxy
direct: cdn.example.cn # this domain and all subdomains → force direct
example.com # a bare domain means proxy:
direct: line fixes it.*.example.com, .example.com, +.example.com, DOMAIN-SUFFIX,example.com, DOMAIN,example.com (exact), DOMAIN-KEYWORD,ads — and dnsmasq's server=/example.com/114.114.114.114 for good measure.The local router ships a loopback-only debug endpoint:
# overview: bind address, upstream, rule counts, hit stats, policy self-check
curl -s http://127.0.0.1:17890/__proxy-router/status
# ask how a host would be routed
curl -s "http://127.0.0.1:17890/__proxy-router/why?host=www.google.com"
# → {"host":"www.google.com","route":"proxy","reason":"list:gfw:google.com"}
# reload rules (local + remote)
curl -s http://127.0.0.1:17890/__proxy-router/reload
The settings card reads the same status snapshot through the host web server's same-origin read-only route GET /dsh-proxy-router/status.
You can also verify routing with curl directly:
curl -x http://127.0.0.1:17890 -sI https://www.google.com # via upstream
curl -x http://127.0.0.1:17890 -sI https://www.baidu.com # direct
The startup log prints the upstream and its source, the bind address, rule counts, the policy self-check result, the settings-page entry point, and whether bash subprocesses are routed too.
/favicon.ico gets 204, / gets a human-readable hint). Without that guard, something as harmless as opening http://127.0.0.1:17890/... in a browser snowballs into a self-loop — 0.1.0 produced over a hundred million requests that way, so 0.1.1 rejects them outright.@deepseek-ai/dsh-http-proxy, @deepseek-ai/schemastery and undici, plus cordis' ctx.get / ctx.effect / ctx.inject; the browser half requires only react and no UI package.ctx.settings.installSection + the settings.plugin.item slot). On a deployment without a settings provider the plugin falls back to its composition config and everything else keeps working.http:// / https://). all_proxy=socks5://… is ignored with a warning; if your proxy also exposes a mixed port (mihomo/clash mixed-port), point the upstream at http://host:port.127.0.0.1 only; it is not exposed to the LAN, and the local rules file is not editable from the settings page (its path is shown there).MIT