yugasun/dsh-plugins--packages-dsh-web-search0

@yugasun/dsh-web-search

Multi-provider web search for DeepSeek Harness: Baidu, Doubao, Tavily, and Exa backends for ctx.web.

包名
@yugasun/dsh-web-search
版本
0.1.0
许可证
MIT
最近更新
2026年8月18日

安装

$npx -p @deepseek-ai/dsh dsh plugin --profile web add github:yugasun/dsh-plugins#ce68e2ab1d298aa39d3a93a7ffd980a49b4ee8c1&path:packages/dsh-web-search

dsh-web-search

npm

Multi-provider web search for DeepSeek Harness. It registers Baidu, Doubao, Tavily, and Exa backends into ctx.web. The model-facing web_search / web_fetch tools stay the official @deepseek-ai/dsh-tool-web schema.

Compatible with DeepSeek Harness 0.1.0-rc.7.

中文文档

Installing a plugin runs third-party code in the harness process with your permissions. Review the source before you install.

Install

From npm:

dsh plugin --profile web add @yugasun/dsh-web-search

From a clone of this monorepo:

dsh plugin --profile web add ./packages/dsh-web-search

Restart dsh web. Settings has a Web search page. Turn Custom search off to keep DSH built-in web_search (deepseek-official) and web_fetch (http); turn it on to use Baidu / Doubao / Tavily / Exa.

From Git (subdirectory):

dsh plugin --profile web add github:yugasun/dsh-plugins#path:packages/dsh-web-search

Uninstall:

dsh plugin --profile web remove @yugasun/dsh-web-search

Providers

IdBackendKeyNotes
baiduQianfan Intelligent Search Generation POST /v2/ai_search/chat/completionsBAIDU_API_KEY or QIANFAN_API_KEYUses a Qianfan model to return a summary plus web references. web_fetch stays on DSH built-in http.
doubaoVolcengine Ark Responses + web_search toolARK_API_KEY or DOUBAO_API_KEYNeeds a Doubao model id that supports the web-search plugin. web_fetch stays on DSH built-in http.
tavilyTavily Search POST /search and Extract POST /extractTAVILY_API_KEYLLM-oriented snippets plus an optional answer. When this backend is active, web_fetch uses Extract.
exaExa Search POST /search and Contents POST /contentsEXA_API_KEYDefault provider id is exa; change exaProviderId if the official @deepseek-ai/dsh-web-search-exa is also installed. When this backend is active, web_fetch uses Contents.

Keys are read in this order: plugin settings, DSH credentials (TAVILY_API_KEY and friends), then the launch environment / ~/.dsh/.env. Settings secrets are never echoed back to the client. A export TAVILY_API_KEY=… inside an agent bash tool does not reach the harness process.

Selection

Installing the plugin can retarget official web_search at this package's facade id dsh-web-search. Settings → Web search has a Custom search switch:

  • Off: web_search uses DSH built-in deepseek-official; web_fetch uses http
  • On (default): pick the backend below
    • Auto (default): first configured backend in order Baidu → Doubao → Tavily → Exa
    • Explicit: Baidu / Doubao / Tavily / Exa
    • Tavily or Exa active: web_fetch uses that vendor's extract/contents API
    • Baidu or Doubao active: web_fetch stays on DSH built-in http

Develop

pnpm --filter @yugasun/dsh-web-search test
pnpm --filter @yugasun/dsh-web-search build

License

MIT