🔍 dsh-searchhub

npx @wilson.liu.cn/dsh-searchhub install --profile web

node scripts/cli.mjs install

npx @wilson.liu.cn/dsh-searchhub status               # 是否已安装 / 是否已激活 / 密钥是否配置
npx @wilson.liu.cn/dsh-searchhub install --dry-run    # 只打印计划，不做任何改动
npx @wilson.liu.cn/dsh-searchhub uninstall            # 卸载，并自动从 bundles 里摘掉
npx @wilson.liu.cn/dsh-searchhub install --spec github:Bin-top1/dsh-searchhub
npx @wilson.liu.cn/dsh-searchhub install --spec /path/to/dsh-searchhub   # 本地 checkout：自动打包成 tarball 再装

cd "$DSH_HOME/profiles/web"
npm install @wilson.liu.cn/dsh-searchhub

"dsh": {
  "profile": {
    "bundles": ["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app", "@wilson.liu.cn/dsh-searchhub"]
  }
}

dsh plugin --profile web add @wilson.liu.cn/dsh-searchhub

# $DSH_HOME/profiles/web/cordis.patch.yml
- id: web
  config:
    searchProvider: tavily
    fetchProvider: http
- id: web-search-deepseek
  disabled: true
- insert:
    - id: searchhub
      name: "@wilson.liu.cn/dsh-searchhub"

npm install     # 仅 typescript 与宿主类型包，都是 devDependencies
npm run build   # tsc -p tsconfig.json → lib/types/*.d.ts
npm test        # 安装器行为 + 打包不变量测试

Stop paying for your agent's web search.

dsh-searchhub is a pluggable search hub for the DeepSeek Harness (DSH). It lets your agent search the web through mainstream, drop-in search providers behind the DSH web capability seam (ctx.web) — instead of burning paid DeepSeek model turns on every web_search call.

💸 No more paying for search. Point the agent's built-in web_search tool at a real search API and keep your model spend for actual thinking.

🧩 Pluggable by design. One hub, many providers. Today it ships with Tavily; the architecture is built to add more of the market's popular search engines over time — pick the one you like and swap it in.

🎁 Free to start. Tavily gives you 1,000 free credits every month — no credit card to get going. Plenty for everyday agent research.

✨ Beautifully polished. Unlike a bare config toggle, dsh-searchhub ships its own hand-crafted native Settings card — collapsible, with a live tri-state status dot, a real show/hide eye toggle, instant key-format validation, and a proper clickable link to grab your key. It looks like it belongs in the product, because it was built to.

📸 The native Settings card

Its own polished card under Settings → Plugins, with a live status dot, a real show/hide toggle, and inline validation — it looks like it belongs in the product:

✨ Features

• 🔌 Pluggable search hub — a clean provider seam so mainstream search engines can be swapped in behind ctx.web. Tavily is included today, with room to grow.
• 💰 Zero model-turn cost — replaces the built-in web-search-deepseek provider, so web_search hits a real search API, not a paid model turn.
• 🎨 Its own polished native card — appears under Settings → Plugins → Plugin configuration as a dedicated, collapsible card (endpoint, search depth, max results, answer toggle, API key) with a live status dot, eye toggle, and inline key-format check.
• 🔐 Secrets done right — the API key lives as a credential reference (TAVILY_API_KEY by default), entered from the UI or the environment; it never has to sit in a config file.
• ⚡ One-command install — ships as a dsh bundle, so npx @wilson.liu.cn/dsh-searchhub install installs it with npm (no pnpm required) and appends it to dsh.profile.bundles. No hand-editing profile patch files.
• 🧭 Normalized results — maps provider results into the seam's { sources, truncated } shape the agent already understands.

🚀 Installation

Option A — install from npm (recommended, no pnpm needed)

npx @wilson.liu.cn/dsh-searchhub install --profile web

This downloads the package from the npm registry (@wilson.liu.cn/dsh-searchhub) and installs + activates it. To install with plain npm instead, see Option B.

From a checkout (when developing this plugin itself):

node scripts/cli.mjs install

It performs the same three steps dsh plugin performs, using the package manager you actually have:

1. initializes $DSH_HOME/profiles/web when it does not exist yet, exactly like DSH's own template (package.json + cordis.patch.yml + pnpm-workspace.yaml);
2. installs this package into that directory with npm;
3. appends the package to the profile's dsh.profile.bundles layer list, so its cordis.patch.yml (switch ctx.web to Tavily, disable web-search-deepseek, register this plugin's host + browser halves) applies on the next boot.

Other subcommands:

npx @wilson.liu.cn/dsh-searchhub status               # installed? activated? key configured?
npx @wilson.liu.cn/dsh-searchhub install --dry-run    # print the plan, change nothing
npx @wilson.liu.cn/dsh-searchhub uninstall            # remove it and drop its layer again
npx @wilson.liu.cn/dsh-searchhub install --spec github:Bin-top1/dsh-searchhub
npx @wilson.liu.cn/dsh-searchhub install --spec /path/to/dsh-searchhub   # checkout → packed first

Then restart the web profile (dsh web or dsh --profile web) and open Settings → Plugins; set the API key in the SearchHub card (or export TAVILY_API_KEY).

Why not dsh plugin add? dsh plugin is a pnpm forwarder (spawnSync("pnpm", …) internally) and fails outright on a machine without pnpm. This installer performs the same three steps with npm.

Why does a directory --spec get packed first? npm installs a local directory as a symlink, and a symlinked package resolves its @deepseek-ai/* imports from the checkout's real path — where the DSH peer packages are absent (or a duplicate copy lives). Packing the checkout into a tarball installs a real copy inside the profile, so those imports resolve through the profile's own node_modules chain into the DSH installation closure.

Option B — manual npm install + one manifest line

cd "$DSH_HOME/profiles/web"
npm install @wilson.liu.cn/dsh-searchhub

Then add the package name to that profile's dsh.profile.bundles (the layer list DSH composes plugins from):

"dsh": {
  "profile": {
    "bundles": ["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app", "@wilson.liu.cn/dsh-searchhub"]
  }
}

Option C — the dsh plugin forwarder (needs pnpm on PATH)

dsh plugin --profile web add @wilson.liu.cn/dsh-searchhub

Option D — hand-written patch layer (works without the bundles list)

# $DSH_HOME/profiles/web/cordis.patch.yml
- id: web
  config:
    searchProvider: tavily
    fetchProvider: http
- id: web-search-deepseek
  disabled: true
- insert:
    - id: searchhub
      name: "@wilson.liu.cn/dsh-searchhub"

⚠️ Do not point name: at a file inside a checkout (file:///…/dsh-searchhub/lib/index.js): the plugin then resolves its host-provided @deepseek-ai/* imports from the checkout's real path and fails with ERR_MODULE_NOT_FOUND (measured). For a local checkout use Option A's --spec <checkout>, which packs it first.

⚙️ Configuration

Setting the API key

Pick one:

1. Native settings card — open the SearchHub card under Settings → Plugins → Plugin configuration and paste the key into the API key box. It is stored encrypted through the credentials service (under the TAVILY_API_KEY reference by default).
2. Environment variable — export TAVILY_API_KEY (or whatever apiKeyEnv you set) before launching DSH.
3. Literal config — set apiKey directly (discouraged; keeps a secret in a file).

Get a key — and your 1,000 free credits/month — at https://app.tavily.com/.

The native settings card (dual-face plugin)

The DSH web Plugin configuration surface does not auto-generate a card for an arbitrary plugin. A card appears only when both halves are present:

1. Host half installs a settings section under a namespace (searchhub) — lib/index.js.
2. Browser half registers a React card into the settings.plugin.item slot, keyed by that same namespace — lib/client.js.

This plugin ships both, so it gets its own polished card (not a borrowed one). The browser half is declared to the DSH client-modules scanner via package.json:

{
  "dsh": {
    "bundle": { "patch": "./cordis.patch.yml" },
    "client": { "platform": "web" }
  },
  "exports": {
    ".":        { "default": "./lib/index.js" },
    "./client": { "default": "./lib/client.js" }
  }
}

The scanner serves lib/client.js to the browser as a classic script whose only top-level statement is a single window.__ModuleLoader__.load({ id, factory }) call. React and the JSX runtime are host-provided seed modules obtained through the factory's synchronous require — the browser half never bundles its own React. The card's secret input writes to the TAVILY_API_KEY credential reference through ctx.remote.credentials.set(...), and the host half resolves that same reference per search.

🗺️ Roadmap

dsh-searchhub is a hub, not a single-engine wrapper. Tavily is the first provider; the seam is deliberately generic so more of the market's popular search backends can be added behind the same card and the same ctx.web contract. Contributions of new providers are welcome.

📦 Publishing (maintainers)

npm login
npm publish

The prebuilt lib/ runtimes and cordis.patch.yml are included via the files allowlist, so consumers do not need a build step.

🛠️ Building from source

Nothing needs to be built to install or use this plugin: the repository ships prebuilt lib/index.js (host half) and lib/client.js (browser half), and the npm package contains only those, scripts/cli.mjs, cordis.patch.yml and the docs.

Maintainers run the build for the published type declarations:

npm install     # devDependencies only: typescript + the host type packages
npm run build   # tsc -p tsconfig.json → lib/types/*.d.ts
npm test        # installer behaviour + packaging invariants

• Host half: typed sources live in src/types/ (index.ts, provider.ts) and compile to .d.ts declarations via npm run build, which prepublishOnly runs before the tarball is built. lib/index.js is the authoritative runtime.
• Browser half: lib/client.js is the single authoritative, hand-authored source — read it directly. It is intentionally written in the exact factory-registration form the DSH client-modules scanner serves (React and the JSX runtime come from the host seed via require), so it needs no bundler and has no separate .ts mirror to drift out of sync.

📄 License

MIT © Bin