返回目录

dsh-web-search-exa

精选清单收录维护状态: 活跃

tonydua/dsh-web-search-exa

零配置的 Exa 网页搜索供应商,支持免密钥匿名 MCP 回退与带密钥 REST 两种接入方式。

前往 GitHub
$ dsh plugin add dsh-web-search-exa

安装

dsh 没有统一的安装命令——把该插件 README 中的配置行加入你的 profile/patch 配置,然后重启即可。

了解安装方式

13

星标

3

Fork

JavaScript

语言

MIT

许可证

2026-08-14

创建于

2026-10-14

最近推送

README

@tonydua/dsh-web-search-exa

English | 简体中文

npm version GitHub release npm downloads License dsh Node GitHub stars GitHub issues

Adds Exa web search to DeepSeek Harness (dsh), the anonymous no-key variant.

dsh plugin --profile web add @tonydua/dsh-web-search-exa

Restart dsh web and it works. No API key, no config edits, no provider to select.

Background, for reference only:

  • Exa is a search API. It retrieves pages by keyword or by meaning and returns citable sources with excerpts. It does not generate answers. Exa offers a REST API and also runs an unauthenticated public MCP server.
  • The official dsh-web-search-exa is dsh's Exa search provider. It uses Exa's REST API and is only useful once you configure an API key.
  • This package is a modified copy of the official one. The REST path works the same. What we added is a keyless channel: with no key it uses Exa's public MCP server, and with a key it still uses REST. The anonymous approach follows the oh-my-pi project, see Acknowledgements.

You can ignore all of this by default. Read Selecting a provider only if you also run the official package, or if dsh reports an ambiguous provider.

Built with deepseek-v4-flash inside DeepSeek Harness (dsh). The 0.2.3 live-config work was done with GLM-5.3-flash.

Features

  • Works without a key. Searches go through Exa's public MCP server (mcp.exa.ai/mcp) and carry no credentials.
  • Returns structured results on that keyless path. It calls web_search_advanced_exa, whose output is JSON in the REST field vocabulary, so sources carry real highlight snippets without text parsing.
  • Upgrades itself when you add a key. Setting EXA_API_KEY switches to Exa's POST /search REST API for higher limits, with no behavior change.
  • Drop-in. It registers into the dsh ctx.web seam; the model-facing web_search and web_fetch tools, their prompt sections, and the result cards all stay as they are.
  • Works out of the box. With no official package installed there is no provider to select.
  • Backs off when it fails. After repeated failures on the anonymous channel the plugin marks itself unavailable so dsh can pick another provider, instead of failing every search. See What happens when a search fails.

Installation

Pick one of three. The choice only decides where the code comes from; all three end up the same.

From npm. The dsh.bundle manifest ships the bundle patch, so the provider row is inserted for you and you do not edit any patch by hand.

dsh plugin --profile web add @tonydua/dsh-web-search-exa

From the GitHub Release. The same tarball, for when npm is unreachable.

dsh plugin --profile web add https://github.com/TonyDua/dsh-web-search-exa/releases/latest/download/dsh-web-search-exa.tgz

From the repository. Tracks main, including work not yet released.

dsh plugin --profile web add github:TonyDua/dsh-web-search-exa

For a local development checkout, use the same command with a path instead of a package name: dsh plugin --profile web add ../plugins/dsh-web-search-exa.

Restart dsh web afterwards. That is the whole procedure in most cases.

Selecting a provider

Skip this section unless you install the official package too.

Before each search, the dsh seam picks an available provider. If exactly one is available it is selected automatically. If more than one is available the seam raises WEB_PROVIDER_AMBIGUOUS and asks you to name one. So there are only two cases where you have to act:

  • You installed the official package as well. Both packages register the provider id exa, so dsh web fails at startup with WEB_DUPLICATE_PROVIDER. You must give this package a different id first, see Coexistence with the official package.
  • You see WEB_PROVIDER_AMBIGUOUS. Another provider is available. Name the one you want.

Two ways to name it:

# $DSH_HOME/profiles/web/cordis.patch.yml
- id: web
  name: '@deepseek-ai/dsh-web'
  config:
    searchProvider: exa

Or set $DSH_WEB_SEARCH_PROVIDER=exa at runtime.

Restart dsh web after the change. The model-facing web_search tool then uses the selected provider; no tool configuration changes.

Release artifacts and install warnings (usually not needed)

Release artifacts. CI packs this version's tarball, verifies it against every supported dsh version, attaches it to the GitHub Release, and publishes that same artifact to npm. So the release asset and the npm tarball are one file, not two builds that happen to match.

在 GitHub 阅读完整 README →

DSH Plugins 是独立的 DeepSeek Harness 插件目录,与 DeepSeek 官方无关,也不代表官方背书。第三方插件未经安全审计,安装前请审查源码。

每周获取最新的 DeepSeek Harness 插件,绝不滥发。