DeepSeek Harness 插件

dsh-web-search-router

Free multi-provider web search router for DeepSeek Harness (DSH).(英文原文)

跳到安装方式

来源信息

GitHub 仓库
chenyuhao0628/dsh-web-search-router
最近更新
2026年8月18日
分类
文档与渲染
GitHub stars
0
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/chenyuhao0628/dsh-web-search-router
插件名:dsh-web-search-router
作者:chenyuhao0628

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

dsh-web-search-router

A free multi-provider web search router for DeepSeek Harness (DSH).

The plugin keeps DSH's built-in web_search tool and registers a multi-search provider. It starts with the keyless Parallel endpoint, then falls back through configured search APIs only when more results are needed or a provider fails.

Features

  • Keyless Parallel search as the first route.
  • Optional Tavily, Exa, Brave Search, Serper, and SerpApi fallbacks.
  • Dynamic fallback order balancing estimated free capacity and observed latency.
  • Live Tavily and SerpApi quota refreshes, plus Brave response-header quotas.
  • Early exit as soon as enough unique results have been collected.
  • URL canonicalization, deduplication, and reciprocal rank fusion (RRF).
  • Provider cooldowns after rate-limit, quota, authentication, or transient errors.
  • Write-only API key controls in the DSH Settings page.
  • No dependency on the paid DeepSeek web search provider.

Routing

Each request follows this sequence:

1. Query Parallel without an API key. 2. Stop immediately if enough unique results were returned. 3. Rank configured keyed providers by remaining estimated free capacity and exponentially weighted observed latency. 4. Query one provider at a time and stop as soon as the requested result count is reached. 5. Deduplicate and merge all collected results with RRF.

The initial keyed-provider estimates currently favor Tavily, Exa, Brave Search, Serper, and SerpApi according to the capacity/latency score. Runtime measurements can change that order automatically.

Before entering the keyed fallback chain, the router refreshes Tavily and SerpApi account usage when their ten-minute cache has expired. Brave quota is learned from the normal search response headers without an extra request. Exa and Serper currently use process-local estimates because they do not expose a documented public balance endpoint. A provider with a known zero balance is skipped until its usage snapshot changes.

Cooldowns are 10 minutes for HTTP 429, 6 hours for quota or credit exhaustion, 1 hour for authentication failures, and 1 minute for other transient failures. These are process-local health hints, not live quota counters.

Installation

From the DSH web profile directory, install the GitHub repository:

cd ~/.dsh/profiles/web
pnpm add github:chenyuhao0628/dsh-web-search-router

Add dsh-web-search-router to dsh.profile.bundles in that profile's package.json, then restart DSH. Select multi-search as the web search provider if it is not already selected.

For local development, a link dependency also works:

{
  "dependencies": {
    "dsh-web-search-router": "link:/absolute/path/to/dsh-web-search-router"
  }
}

API Keys

Open DSH Settings and choose 网络搜索. Each field writes directly to DSH's credential service and never reads the stored secret back into the page. The same page shows live, response-header, estimated, and cooldown states. Use 刷新额度 to force a new Tavily and SerpApi account-usage check.

ProviderCredential referenceRequired
ParallelNoneNo
TavilyTAVILY_API_KEYNo
ExaEXA_API_KEYNo
Brave SearchBRAVE_SEARCH_API_KEYNo
SerperSERPER_API_KEYNo
SerpApiSERPAPI_API_KEYNo

API keys are not stored in Cordis configuration or this repository. Do not put credentials in package.json, commits, issue reports, or screenshots. The browser status endpoint receives only normalized quota metadata; third-party account payloads and resolved credential values never cross that boundary.

Development

Requires Node.js 20 or newer and pnpm.

pnpm install
pnpm check
pnpm test

The tests cover URL normalization, RRF merging, and provider ranking. The plugin targets the Cordis and DSH web APIs declared in peerDependencies.

License

MIT