dsh-free-search

One-line Description

Provides 10 switchable web search engines for DeepSeek Harness, defaulting to free Bing, enabling agents to search the web without any API key, with time filtering, platform search, and a web settings interface.

Core Features

• Provides 10 web search engines (ddg / ddg-lite / bing / searxng / anysearch / exa / tavily / keenable / perplexity / deepseek-official), default bing works out of the box
• Automatic engine fallback: any engine error (missing key, 401, rate limit, network issue) automatically tries the next one in rotation, search never fails directly, and the actual active engine is noted at the top of results
• Web settings page + chat /free-search-engine command to switch engines, configure API keys, test connectivity, toggle between Chinese and English UI
• Time-filtering enabled advanced_search tool, supports "last N days/hours/months" or "after a certain date"
• Platform search platform_search tool, retrieves public APIs by GitHub / V2EX / Bilibili / Reddit
• Result caching (LRU 50 entries, TTL 0-5 minutes configurable), prevents rate limiting on free engines and saves paid quota

Technical Implementation

• Language: JavaScript (ESM)
• Key Dependencies: @deepseek-ai/dsh-settings (configuration access and bridging), @deepseek-ai/dsh-tools (agent tool registration), @deepseek-ai/schemastery (configuration schema validation)
• Architecture Pattern: Implements the official WebSearchProvider interface (id / available / search), uses cordis.patch.yml to simultaneously inject the web-search-free sub-plugin and redirect the host's web.searchProvider to this plugin's ddg provider, causing DSH's built-in web_search tool to automatically use this plugin's multi-engine logic; host-side + client-side dual packages (lib/index.js + lib/client.js)
• Entry Files: lib/index.js (host-side, registers provider/tools/settings panel bridging), lib/client.js (browser-side React settings card + popup command)

Use Cases

Use this plugin when you don't have or don't want a DeepSeek official API key but need agents to search the web, such as daily Q&A, information lookup, fetching web page content; or when your OpenAI-compatible gateway doesn't support the web_search tool, this plugin directly takes over search via the host-side implementation. Regular users' needs like searching "recent week's XX news", "finding repositories on GitHub", "reading this link's content" can all be directly covered.

Prerequisites and Compatibility

Note: @deepseek-ai/dsh-settings and @deepseek-ai/dsh-tools are intentionally declared as peerDependencies; DSH runtime must use the single instance in the installation tree. Please install via dsh plugin --profile <profile> add ..., do not copy the DSH core package to the profile's local node_modules; duplicate copies will break the tool scheduler.

Installation

dsh plugin --profile web add github:DDDMUC/dsh-free-search

Restart dsh web after installation to take effect.

Configuration Options

Configuration is saved under the free-search namespace in ~/.dsh/settings.yaml, or can be filled in via the web settings page (key fields only display "configured" in the UI, not echoed in plain text).

FAQ

Q: Do I need to configure an API key after installation?

A: Not needed. The default engine is free Bing, it can search the web right after installation. Exa/Tavily/Keenable will use each provider's public anonymous quota even without a key; only Perplexity and DeepSeek official (these two paid engines) require a key.

Q: Where do I switch search engines?

A: Two ways. In the web settings page, go to Settings → Plugins → Configurable → Free Search card, use the dropdown to switch and save; or in the chat input, type /free-search-engine to pop up the engine selection window and click to select, which is equivalent to switching and saving via the settings page.

Q: What happens if one engine returns no results?

A: The plugin follows a unified fallback chain: after the preferred engine fails, it tries other engines in sequence (first paid engines with configured keys, then Exa/Tavily/Keenable's keyless channels, finally free engines like Bing/AnySearch/DDG). A Note is added at the top of results explaining the actual active engine and the reason for skipping (e.g., "Note: perplexity unavailable or failed, using exa.").

Q: How to search "recent week's news" or "updates since July"?

A: Just tell the agent in natural language, e.g., "search DSH news from the last 3 days", "find releases since July". The agent will call the advanced_search tool with the timeRange parameter, supporting fixed buckets (day/week/month/year), custom relative values (12h / 3d / 2mo / 1y), and absolute dates (2026-07-01).

Q: How to read the full text of a web page from search results?

A: Just tell the agent "open the first link and see the content". The web_fetch tool is enabled (official dsh-web-fetch-http provider), automatically follows redirects and converts HTML to plain text. Note it has no SSRF protection, agents can theoretically access internal addresses, please use as needed.

Q: Do I need to configure a proxy for domestic use?

A: Engines like DuckDuckGo may have restricted access in China. On Node 24+, you need to set three environment variables for the dsh process: NODE_USE_ENV_PROXY=1, HTTPS_PROXY, HTTP_PROXY, otherwise Node fetch won't use the system proxy.

Q: How to uninstall?

A: Remove this plugin entry from the DSH profile's plugin list, then restart dsh web. Configuration is written to the free-search namespace in ~/.dsh/settings.yaml, which can be manually cleaned up if needed.

Q: What's the relationship with DSH's built-in web_search?

A: This plugin implements the official WebSearchProvider interface and uses cordis.patch.yml to redirect the host's web.searchProvider field to this plugin's provider (id=ddg). Therefore, DSH's built-in web_search tool automatically calls this plugin's multi-engine + fallback logic; they don't conflict.

Difficulty Level

Beginner — Default Bing works right after installation, paid engines also have keyless fallback; deep customization only requires switching engines via the web settings page dropdown and filling in keys as needed.

Known Issues and Limitations

• DuckDuckGo (html / lite) occasionally triggers anti-bot rate limiting ("anti-bot challenge"), usually temporary, recovers automatically; first failure is skipped by the fallback chain, noted in results
• Bing / AnySearch don't support time filtering parameters (no corresponding query fields), when timeRange is present they are skipped and engines that support filtering are used instead
• Tavily / SearXNG / DDG time filtering only supports fixed buckets (day/week/month/year), custom relative values (like 3d) are approximate-mapped to the nearest bucket
• Paid engines (Perplexity, DeepSeek official) without configured keys are skipped by the fallback chain, they won't "fake search"
• web_fetch tool has no SSRF protection, agents can theoretically read internal addresses
• Checking for updates requests npm registry https://registry.npmjs.org/dsh-free-search/latest, domestic environments with network restrictions may not get the version number

DeepSeek Harness 免费搜索插件 —— 无需 API key，零成本，多引擎可切换。 一个给 DeepSeek Harness (dsh) 添加多引擎搜索 provider 的插件，注册进 ctx.web seam。内置 web_search 工具自动选用，支持网页设置页切换引擎、配置 API key、一键测试所有引擎、弹出式命令切换引擎。

中文 · English

---

中文

为什么需要它

dsh 默认的搜索 provider 依赖 DeepSeek 官方 API key（DEEPSEEK_API_KEY）。如果你：

• 没有（或不想用）DeepSeek 官方 key，
• 用的是 opencode-go 这类网关（其 OpenAI 兼容端点不支持 web_search 工具），

……那么内置搜索必然失败，agent 会告诉你"无法联网"。

这个插件提供多个免费引擎 + 自动回退，彻底摆脱 DeepSeek 官方 key 的依赖。

特性

• 零成本 —— 多个免费引擎，无需 key、无需注册
• 多引擎可选：DuckDuckGo（html/lite）、Bing、SearXNG（元搜索，支持自定义实例）、AnySearch、Exa、Tavily、Keenable、Perplexity、DeepSeek 官方
• 网页设置页 —— 引擎切换 + API key 配置（UI 中 key 脱敏显示"已配置"）+ 中英文切换
• 弹出式切换命令 —— 聊天框输入 /free-search-engine，弹出引擎选择窗口，点选即切换（等效设置页 + 保存）
• 引擎测试 —— free_search_test 工具让 agent 一键测试所有引擎；设置页也有"测试引擎"按钮（直测当前引擎，不走回退链，付费引擎无 key 会明确报错）
• 统一引擎回退 —— 任何引擎失败（付费/免费，缺 key/401/限流/网络）自动轮流尝试下一个引擎：首选引擎 → 其他引擎（exa/tavily/keenable 无 key 也会尝试，因为它们自带 keyless 免费额度）→ 剩余免费引擎，搜索永不直接失败；结果顶部注明实际生效的引擎（如 Note: perplexity unavailable or failed, using exa.）
• 时间过滤 —— advanced_search 工具支持 timeRange：固定档、自定义相对值、绝对日期三种形式（详见下方逻辑说明）
• 系统提示词注入 —— agent 知道当前用哪个引擎、哪些需要 key
• 版本号 + 检查更新 —— 设置卡片显示当前版本（v0.4.11），"检查更新"按钮直连 npm registry 对比最新版，有新版本时提示并可一键跳转
• 结果缓存 —— 相同查询（含引擎/时间过滤参数）5 分钟内命中缓存（LRU 50 条），防免费引擎限流、省付费额度；时长可在设置页 0-5 分钟自由配置（0 关闭）
• 免费标注 —— 设置页中免费引擎带绿色 FREE 徽章，付费引擎带橙色 API KEY 徽章
• 网页抓取（web_fetch） —— 让 agent 抓取网页内容（官方 dsh-web-fetch-http provider，纯 JS，零额外依赖）
• 平台搜索（platform_search） —— 搜 GitHub / V2EX / B站（公开 API，零依赖）
• 干净集成 —— 实现官方 WebSearchProvider seam 接口，与官方插件共存

引擎列表

• 默认引擎为 bing（免费且最稳定），安装后开箱即用。
• 自动回退：任何引擎失败（免费限流/反爬，付费缺 key/无效/网络错误）都会自动轮流尝试下一个引擎——先试其他已配 key 的付费引擎，再试免费引擎（Bing/AnySearch 等），并在结果中附带回退提示——搜索不会因引擎问题直接失败。
• 设置页有官网链接：免费引擎显示"访问官网 →"，付费引擎显示"获取 API Key →"（新标签页打开）：
  • Exa：https://dashboard.exa.ai/api-keys
  • Tavily：https://app.tavily.com/home
  • Keenable：https://keenable.ai/login
  • Perplexity：https://www.perplexity.ai/settings/api
  • DeepSeek：https://platform.deepseek.com/api_keys

为什么免费引擎不需要 key？

• AnySearch：其 v1/search REST 接口提供匿名的公共搜索额度，无需注册或 API key。额度有限流（适合日常搜索），但作为免费引擎之一，与其他免费引擎互相回退，体验稳定。
• Exa：公开 MCP 端点（mcp.exa.ai/mcp）支持匿名调用，不配 key 也能用；配置 EXA_API_KEY 后可获得更高额度。
• Tavily：通过 x-tavily-access-mode: keyless 头走 keyless 匿名额度，不配 key 即可用；配置 TAVILY_API_KEY 后走账号档，额度更高、结果质量更稳定。
• Keenable：无 key 时走其公开 MCP 端点（api.keenable.ai/mcp）匿名调用；配置 KEENABLE_API_KEY 后走 REST API（api.keenable.ai/v1/search），额度更高、按组织限流。

安装

git clone https://github.com/DDDMUC/dsh-free-search.git
dsh plugin --profile web add /path/to/dsh-free-search

然后重启：

dsh web

依赖说明

插件对 @deepseek-ai/dsh-settings 和 @deepseek-ai/dsh-tools 使用 peerDependencies，这是刻意的：DSH 运行时必须使用安装树中的唯一实例。请通过 dsh plugin --profile <profile> add ... 安装插件，不要把 DSH 核心包复制进 profile 的本地 node_modules；重复副本会导致工具调度器失效。

使用

网页设置（推荐）

安装后，打开 设置 → 插件 → 可配置 标签页 → Free Search 卡片（官方设置页）：

• Search engine：下拉框切换引擎，保存即生效
• API keys：为 Exa / Tavily / Keenable / Perplexity / DeepSeek 填写 key（密码框，保存后只显示"已配置"）
• Test engine：直测当前引擎可用性（不走回退链，付费引擎无 key 会明确报错）
• Use Bing default：把当前搜索引擎切回稳定的免费 Bing；Discard 只撤销尚未保存的编辑
• Platform search：勾选启用 GitHub / V2EX / Bilibili 平台搜索（platform_search 工具按此过滤）
• EN / 中文：切换界面语言（默认中文）

聊天框切换引擎（/free-search-engine）

不用进设置页也能切换引擎：在聊天框输入 /free-search-engine，弹出引擎选择窗口（和 /model 选模型一样的交互），点选即切换，当前引擎会标记出来。等效于设置页切换 + 保存，且界面语言跟随设置页（中文/英文）。

命令只改首选引擎配置，搜索仍走 web_search + 统一回退链：即使首选引擎挂了也会自动换其他引擎，永不直接失败。系统提示词同步刷新。

配置文件

配置存在 ~/.dsh/settings.yaml：

free-search:
  provider: bing              # ddg / ddg-lite / bing / searxng / anysearch / exa / tavily / keenable / perplexity / deepseek-official
  lang: zh                    # 设置页界面语言（zh / en）
  bingMarket: zh-CN           # Bing 市场
  region: cn-zh               # DuckDuckGo 区域（可选）
  searxngInstances:           # 自定义 SearXNG 实例（可选）
    - https://your-instance.example
  exaApiKey: ...              # 或通过设置页填写
  tavilyApiKey: ...           # 或通过设置页填写
  keenableApiKey: ...         # 或通过设置页填写
  perplexityApiKey: ...
  deepseekApiKey: ...

让 agent 测试所有引擎

对 agent 说"测试一下所有搜索引擎"，它会调用 free_search_test 工具，逐个测试并报告：

Search engine test:
- ddg: FAIL - DuckDuckGo is rate-limited right now (anti-bot challenge, usually temporary) - Bing works
- bing: OK (2 results, e.g. "DeepSeek Harness developer preview...")
- exa: FAIL - EXA_API_KEY not configured

时间过滤（advanced_search）

让 agent 搜"最近一周的新闻"、"这个月的发布"、"最近 3 天的消息"、"7 月以来的更新"，它会调用 advanced_search 工具，带 timeRange 参数。该工具同样走统一回退链，且可显式指定 engine，返回结构同 web_search。

timeRange 支持三种形式：

各引擎对 timeRange 的处理逻辑：

"最近似档位"映射规则：≤2 天 → day，≤14 天 → week，≤90 天 → month，否则 year。例如 3d 在 Tavily 上按 day 处理，2mo 按 month 处理。

引擎链优先级：当带 timeRange 搜索时，支持时间过滤的引擎（tavily / exa / keenable / searxng / ddg / ddg-lite）会排到引擎链前面，确保过滤真正生效——即使首选引擎是 bing（不支持过滤），也会先尝试支持过滤的引擎。

示例对话："帮我搜最近 3 天关于 DSH 的新闻" → agent 调用 advanced_search，timeRange: "3d"。

抓取网页内容（web_fetch）

搜索到 URL 后，可以让 agent 读取网页全文（如"打开第一个链接看看内容"）。web_fetch 工具已启用（官方 dsh-web-fetch-http provider）：

• 自动跟随重定向、解码正文（HTML 转文本）
• 支持超时和大小限制
• ⚠️ 注意：web_fetch 无 SSRF 防护，agent 理论上可访问内网地址——按需使用

平台搜索（platform_search）

让 agent 搜特定平台，如"在 GitHub 上搜 deepseek harness"、"看看 B站有什么相关视频"、"V2EX 上关于 dsh 的讨论"。platform_search 工具支持：

全部走公开 API，零外部依赖，开箱即用。

本地引擎切换工具（tools/）

tools/ 目录附带了一个本地切换小工具（零依赖）：

• 启动搜索引擎切换器.cmd（Windows）——双击启动本地 Node 服务（http://127.0.0.1:4789）并自动打开浏览器选择页面
• switch-engine.html —— 选择页面：显示当前引擎，点选新引擎，一键写入配置
• server.mjs —— 本地服务，负责读写 ~/.dsh/profiles/web/cordis.patch.yml
• switch-engine.ps1 —— 无界面命令行版：powershell -File tools/switch-engine.ps1 -Engine bing

切换后重启 dsh web 生效。

配置卡片挂在官方设置页的 settings.plugin.item 插槽（dsh 自带），配置读写走插件自建 bridge，不依赖 dsh-web-ui，插件可独立使用。

代理说明（国内用户）

DuckDuckGo 等引擎可能需要代理才能访问，而 Node.js 的 fetch 默认不走系统代理。需要给 dsh 进程设置（Node 24+）：

export NODE_USE_ENV_PROXY=1
export HTTPS_PROXY=http://127.0.0.1:7897   # 你的代理地址
export HTTP_PROXY=http://127.0.0.1:7897

Windows 用户：桌面快捷方式已内置此配置（set NODE_USE_ENV_PROXY=1&& set HTTPS_PROXY=...）。

工作原理

• lib/index.js：host 端。实现 WebSearchProvider（id / available() / search()），统一引擎路由 + 自动回退（付费引擎优先，免费兜底）；解析 timeRange（固定档/相对值/绝对日期）并透传给各引擎；注册 free-search settings namespace；提供 /api/dsh-free-search-settings 读写桥 + raw-search 调试接口；注册 free_search_test、platform_search、advanced_search 工具；动态注入引擎清单到系统提示词（设置变更时自动刷新）。
• lib/client.js：浏览器端。React 配置卡片（引擎选择 + key 输入 + 连通测试 + 中英切换），挂载到官方设置页的 settings.plugin.item 插槽；注册 /free-search-engine 弹出式切换命令（commandUi popupSelect，与 /model 同机制）。
• cordis.patch.yml：插件 loader 配置。

---

English

Why You Need It

dsh's default search provider relies on the official DeepSeek API key (DEEPSEEK_API_KEY). If you:

• Do not have (or prefer not to use) an official DeepSeek key,
• Use a gateway like opencode-go (whose OpenAI-compatible endpoint does not support the web_search tool),

...then the built-in search will inevitably fail, and the agent will tell you "I cannot access the internet."

This plugin provides multiple free search engines with automatic fallback, completely freeing you from relying on DeepSeek's official key.

Features

• Zero Cost — Multiple free engines with no API key or registration required
• Multi-Engine Support — DuckDuckGo (HTML / Lite), Bing, AnySearch AI, SearXNG (meta-search with custom instances), Exa, Tavily, Keenable, Perplexity, and DeepSeek Official
• Web Settings UI — Engine switching, API key configuration (keys masked as "configured" in the UI), and a Chinese/English toggle
• Popup Switch Command — Type /free-search-engine in the chat: a picker opens with all engines; click one to switch (equivalent to the settings page + save)
• Engine Testing — free_search_test for the agent to check all engines in one call; the settings UI also has a "Test engine" button that tests the selected engine directly (no fallback chain; paid engines without a key report an explicit error)
• Unified Engine Fallback — Any engine failure (paid or free, missing key, 401, rate limit, network error) automatically tries the next engine: the configured engine first, then other engines (exa/tavily/keenable are tried even without a key because they have built-in keyless quota), then the remaining free engines (Bing/AnySearch etc.) — with a note attached to the results naming the engine that actually served them (e.g. Note: perplexity unavailable or failed, using exa.). Search never fails outright.
• Time Filtering — The advanced_search tool supports timeRange: fixed tiers, custom relative values, or an absolute date (details below)
• System Prompt Injection — The agent is aware of the currently active engine and which engines require API keys
• Version + Update Check — The settings card shows the current version (v0.4.11), and a "Check update" button queries the npm registry to compare against the latest release, prompting a one-click jump when a newer version exists
• Result Caching — Identical queries (same engine / time-filter args) hit an LRU cache (50 entries) for up to 5 minutes, protecting free engines from rate-limiting and saving paid quota; the TTL is configurable from 0-5 minutes in the settings UI (0 disables caching)
• Visual Badges — Free engines feature a green FREE badge, while paid engines show an orange API KEY badge in the settings UI
• Webpage Fetching (web_fetch) — Allows the agent to read full webpage contents (official dsh-web-fetch-http provider, pure JS, zero extra dependencies)
• Platform Search (platform_search) — Search GitHub / V2EX / Bilibili (public APIs, zero extra dependencies)
• Clean Integration — Implements the official WebSearchProvider seam interface, coexisting seamlessly with official plugins

Supported Engines

• Default engine is bing (free and most stable), ready to use out of the box after installation.
• Auto-failover: any engine failure (rate-limited free engine, or missing/invalid paid key, network error) automatically tries the next engine — the configured engine first, then other engines (exa/tavily/keenable are tried even without a key because they have built-in keyless quota), then the remaining free engines (Bing/AnySearch etc.) — with a note attached to the results naming the engine that actually served them (e.g. Note: perplexity unavailable or failed, using exa.). Search never fails outright because of engine issues.
• Official Links in Settings: Free engines display "Visit Website →", while paid engines display "Get API Key →" (opens in a new tab):
  • Exa: https://dashboard.exa.ai/api-keys
  • Tavily: https://app.tavily.com/home
  • Keenable: https://keenable.ai/login
  • Perplexity: https://www.perplexity.ai/settings/api
  • DeepSeek: https://platform.deepseek.com/api_keys

Why are some engines free?

• AnySearch: its v1/search REST endpoint provides anonymous public search quota without registration or an API key. Quota is rate-limited (fine for daily queries), but as one of the free engines with mutual fallback it stays reliable.
• Exa: its public MCP endpoint (mcp.exa.ai/mcp) supports anonymous requests, so it works without a key; configuring EXA_API_KEY grants a higher usage quota.
• Tavily: offers keyless anonymous quota via the x-tavily-access-mode: keyless header — it works without a key; configuring TAVILY_API_KEY switches to the account tier for higher quota and more stable results.
• Keenable: without a key it is called via its public MCP endpoint (api.keenable.ai/mcp); configuring KEENABLE_API_KEY switches to the REST API (api.keenable.ai/v1/search) for higher quota and organization-scoped rate limits.

Installation

git clone https://github.com/DDDMUC/dsh-free-search.git
dsh plugin --profile web add /path/to/dsh-free-search

Then restart:

dsh web

Dependency Note

This plugin intentionally specifies @deepseek-ai/dsh-settings and @deepseek-ai/dsh-tools as peerDependencies: the DSH runtime must use a single instance from the installation tree. Always install the plugin using dsh plugin --profile <profile> add .... Do not copy DSH core packages into a profile-local node_modules, as duplicate copies can break the tool scheduler.

Usage

Web Settings (Recommended)

After installation, navigate to Settings → Plugins → Configurable tab → Free Search card (the official settings page):

• Search engine: Select an engine from the dropdown; changes take effect immediately upon saving.
• API keys: Enter keys for Exa / Tavily / Keenable / Perplexity / DeepSeek (password fields; displayed as "configured" once saved).
• Test engine: Tests the selected engine directly (no fallback chain; paid engines without a key report an explicit error).
• Use Bing default: stage a switch back to the stable free Bing engine; Discard only cancels unsaved edits
• Platform search: check GitHub / V2EX / Bilibili to enable them for the platform_search tool (disabled platforms are skipped).
• EN / 中文: toggle the interface language (default Chinese).

Switching Engines from the Chat (/free-search-engine)

You can also switch the engine right from the chat — no need to open the settings page. Type /free-search-engine: a picker opens with all engines (the same interaction as /model for selecting a model). Click one to switch; the current engine is marked. Equivalent to switching and saving in the settings page, and the language follows the settings page (Chinese/English).

The command only changes the preferred engine; search still goes through web_search + the unified fallback chain — even if the preferred engine fails, it automatically switches to others, never failing outright. The system prompt refreshes accordingly.

Configuration File

Configuration is stored in ~/.dsh/settings.yaml:

free-search:
  provider: bing              # ddg / ddg-lite / bing / searxng / anysearch / exa / tavily / keenable / perplexity / deepseek-official
  lang: zh                    # settings UI language (zh / en)
  bingMarket: zh-CN           # Bing market
  region: cn-zh               # DuckDuckGo region (optional)
  searxngInstances:           # Custom SearXNG instances (optional)
    - https://your-instance.example
  exaApiKey: ...              # Or configure via the web settings UI
  tavilyApiKey: ...           # Or configure via the web settings UI
  keenableApiKey: ...         # Or configure via the web settings UI
  perplexityApiKey: ...
  deepseekApiKey: ...

Asking the Agent to Test All Engines

Tell the agent "Test all search engines", and it will call the free_search_test tool to check each engine sequentially and report back:

Search engine test:
- ddg: FAIL - DuckDuckGo is rate-limited right now (anti-bot challenge, usually temporary) - Bing works
- bing: OK (2 results, e.g. "DeepSeek Harness developer preview...")
- exa: FAIL - EXA_API_KEY not configured

Time Filtering (advanced_search)

Ask the agent for "news from the last week", "releases this month", "updates from the last 3 days", or "posts since July", and it will call the advanced_search tool with a timeRange parameter. It uses the same unified fallback chain, can force a specific engine, and returns the same shape as web_search.

The timeRange parameter accepts three forms:

How each engine handles timeRange:

Nearest-tier mapping rule: ≤2 days → day, ≤14 days → week, ≤90 days → month, otherwise year. For example, 3d becomes day on Tavily, and 2mo becomes month.

Engine-chain priority: when a timeRange is present, engines that support time filtering (tavily / exa / keenable / searxng / ddg / ddg-lite) are moved to the front of the fallback chain, so the filter actually takes effect — even if the preferred engine is bing (which does not support filtering), a filtering-capable engine is tried first.

Example: "Find DSH news from the last 3 days" → agent calls advanced_search with timeRange: "3d".

Fetch Webpage Content (web_fetch)

After searching, the agent can read full webpage content (e.g., "Open the first link and summarize it"). The web_fetch tool is enabled by default (official dsh-web-fetch-http provider):

• Automatically follows redirects and decodes HTML to plain text.
• Supports timeout and response size limits.
• ⚠️ Note: web_fetch does not have SSRF protection; the agent could theoretically access internal network addresses. Use as needed.

Platform Search (platform_search)

Ask the agent to search specific platforms (e.g., "Search GitHub for deepseek harness", "Find related videos on Bilibili", or "Discussions about dsh on V2EX"). The platform_search tool supports:

All platform searches rely on public endpoints with zero external dependencies and work out of the box.

Local Engine Switcher (tools/)

The tools/ directory includes a lightweight, zero-dependency switcher:

• 启动搜索引擎切换器.cmd (Windows) — Double-click to launch a local Node server (http://127.0.0.1:4789) and automatically open the engine selector page in your browser.
• switch-engine.html — The selector UI: displays current engine status and allows one-click switching.
• server.mjs — The local backend service responsible for reading/writing ~/.dsh/profiles/web/cordis.patch.yml.
• switch-engine.ps1 — Headless PowerShell script: powershell -File tools/switch-engine.ps1 -Engine bing.

Restart dsh web after switching to apply changes.

The settings card mounts into the official settings.plugin.item slot (built into DSH), and configuration reads/writes go through the plugin's own bridge. No dsh-web-ui dependency — the plugin can be used standalone.

Proxy Note (for Users in Mainland China)

Engines like DuckDuckGo may require a proxy. Since Node.js fetch does not use the system proxy by default, set the following environment variables for the dsh process (Node 24+):

export NODE_USE_ENV_PROXY=1
export HTTPS_PROXY=http://127.0.0.1:7897   # Your proxy address
export HTTP_PROXY=http://127.0.0.1:7897

Windows users: The desktop shortcut already includes this configuration (set NODE_USE_ENV_PROXY=1&& set HTTPS_PROXY=...).

How It Works

• lib/index.js: Host side. Implements WebSearchProvider (id / available() / search()), unified engine routing + auto-fallback (paid engines first, free as fallback); parses timeRange (fixed tiers / relative values / absolute dates) and forwards it to each engine; registers the free-search settings namespace; provides the /api/dsh-free-search-settings read/write bridge + raw-search debug endpoint; registers the free_search_test, platform_search, and advanced_search tools; dynamically injects the engine list into system prompts (auto-refreshes on settings change).
• lib/client.js: Browser side. React configuration card (engine select, key inputs, connectivity test, and Chinese/English toggle), mounted into the official settings.plugin.item slot; registers the /free-search-engine popup switch command (commandUi popupSelect, the same mechanism as /model).
• cordis.patch.yml: Plugin loader configuration.

License

MIT