elves-ai/dsh-web-search-firecrawl

Firecrawl-backed web search provider for the built-in web_search tool, with a settings card for the API key and result limits.

dsh-web-search-firecrawl is a Firecrawl-backed search provider for the DeepSeek Harness web capability seam (ctx.web): it makes the built-in web_search tool run on Firecrawl's search API instead of the shipped DeepSeek route. It is a Cordis function plugin that registers a WebSearchProvider (id: firecrawl) into the seam — it does not own ctx.web and does not register a model-facing tool (the tool schema stays with @deepseek-ai/dsh-tool-web). It calls Firecrawl's POST /v1/search endpoint and maps the flat data[] into the seam's normalized WebSearchResult shape. The API key is configured from a dedicated Firecrawl page in DSH Settings, with $FIRECRAWL_API_KEY kept as a compatibility fallback.

Tools & Capabilities ★ 0 updated 2026-08-17
View on GitHub ↗

Install

dsh plugin --profile web add @elves-ai/dsh-web-search-firecrawl@latest

npm @elves-ai/dsh-web-search-firecrawl 1.0.0 verified 2026-09-03 (repository field → github.com/elves-ai/dsh-web-search-firecrawl; README EN primary with 中文 edition). Install: dsh plugin --profile web add @elves-ai/dsh-web-search-firecrawl@latest (from a deepseek-harness source checkout use pnpm dsh plugin ...). Restart dsh web and hard-refresh after installing so the Settings page loads.

Compatibility

DeepSeek Harness on the 0.1.0-rc.6 line of official packages (peers on @deepseek-ai/dsh-web ^0.1.0-rc.6); a Firecrawl API key (firecrawl.dev).

Details

Recent updates

1.0.0 current on npm (verified 2026-09-03); install section warns that on pre-rc.6 lines pnpm nests a second seam copy and error classification degrades.

FAQ

How do I point the built-in web_search at Firecrawl?
Install the plugin, restart dsh web, then hard-refresh: the bundle patch switches the web seam row to searchProvider: firecrawl and adds a Firecrawl settings page for the API key.
Do I still need the DeepSeek search backend?
No — searches route to Firecrawl's POST /v1/search once the provider is active; without an API key a search fails with a WEB_PROVIDER_* error instead of silently falling back.
Does it add new agent tools?
No — it registers a provider into the existing ctx.web seam, so the tool schema the model sees stays with the official dsh-tool-web.

Alternatives

1624318455/dsh-plugin-tavily · Biogod2020/dsh-bing-search

More plugins in Tools & Capabilities

Browse more in Tools & Capabilities

Guides for Tools & Capabilities plugins