searxng web · Web search tool

Key features

• dsh ships web_search pointed at the DeepSeek cloud search, and mounts no fetch provider at all.
• FetchGET with a browser-ish User-Agent
• The model would otherwise see two overlapping search tools (native web_search and mcp__searxng__searxng_web_search) plus several extra schemas — ambiguous tool selection and 1–2k tokens of per-request overhead for no search-quality gain (both hit the same instance).
• If you run SearXNG for privacy or offline use, your queries still leak to a vendor — until this bundle is installed.
• Unlike an MCP server integration, this rides dsh's own provider seam: the model keeps using the short native tool names (web_search, web_fetch), every agent and subagent inherits it, and nothing extra runs alongside dsh.