AI Agent Hub
Back to plugins
🧰

bing-web-search

Web Tools Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install h-k-c/bing-web-search

Paste the following prompt into your AI chat to install this plugin:

Fetch the source from https://github.com/h-k-c/bing-web-search, copy the plugin directory into the node_modules of your DSH profile (e.g. ~/.dsh/profiles/web/node_modules/bing-web-search/), configure the searchProvider in cordis.patch.yml to point to this plugin, and restart the DSH process to start using it.

About this plugin

When building web-aware workflows in DeepSeek Harness, search is often the most fragile piece: an API price hike, an expired key, or simply the hassle of signing up can all break it. bing-web-search takes a pragmatic stance: keep search alive no matter what. At startup the plugin checks for TAVILY_API_KEY in the environment. If one is present it routes queries through Tavily and returns richer, summary-backed results. If not, it falls back automatically to Bing s free search endpoint—no key, no registration, no friction. You can literally install the plugin and start searching without touching a single config file. Beyond the dual-engine fallback, a handful of practical knobs are exposed: the number of results per query (1 to 10), and independent request timeouts for both Tavily and Bing. These respect environment variables as well as inline plugin config, giving you just enough flexibility without over-engineering. It suits two kinds of users: developers who want a zero-setup, ready-to-go search layer in DSH, and power users who already have a Tavily account and want the precision of curated summaries—just drop in the key and the experience upgrades seamlessly, while the free fallback remains as a safety net.

Use Cases

  • Keep a always-on search channel for web-aware DSH workflows
  • Start searching immediately without requesting any API key
  • Automatically upgrade to summary-backed results when a Tavily key is present

Best For

  • Lightweight DSH users who want search to work out of the box
  • Power users with a Tavily account who value curated summaries
  • Workflow builders whose pipelines depend on an always-available search layer