[Feature]: 建议增加一个模块可以替换原生brave-search到tarvily-search。

[bigredNose]

Problem Statement

windows 11 安装了clawx 0.28版本
问题：每次都要先调用 web_search来brave来搜索，删除配置文件也不行，每次重启客户端配置文件。openclaw.json都会 "brave-web-search": {
"enabled": true
} 自动加载。最好能直接使用skills tarvily而不是每次都是brave。 同时 "web": {},增加的不启动元素工具也会重置。导致切换不成功。

Proposed Solution

强制修改，配置文件后就不要出来brave-web-search。工具 "web": {},能自定义。再界面上

Alternatives Considered

No response

Success Criteria

没有完成。

Additional Context

No response

[vcfgv]

Thanks for the report. A quick clarification first, since this seems related to how the current mechanisms are separated:

tavily-search is a Skill, while web_search is a built-in OpenClaw tool. They are not automatic replacements for each other. At the moment, web_search supports brave (default), perplexity, and grok as providers; tavily is not part of the built-in web_search provider list. So even if tavily-search is enabled, Brave-related behavior can still appear as long as the system is still using built-in web_search.

Based on your description, this looks more like a mismatch between feature boundaries and config structure, rather than a single isolated malfunction. If your goal is to use Tavily only, the practical approach is to explicitly disable built-in web_search and make sure the config is written under tools.web..., not top-level web. If you can share the relevant openclaw.json fragment before and after restart, plus what changes after relaunch, that would help determine whether this is a config-path issue or startup-time config sync causing the reset-like behavior.

---

感谢反馈。这里先澄清一下当前机制，避免配置项理解偏差：

tavily-search 是一个 Skill，而 web_search 是 OpenClaw 内置工具，这两者不是自动替换关系。当前 web_search 支持的 provider 是 brave（默认）、perplexity、grok；tavily 不在 web_search 的 provider 列表里。因此，即使启用了 tavily-search，只要系统仍在调用内置 web_search，就仍然会出现 Brave 相关配置或行为。

从你描述的现象看，问题更像是“能力边界”和“配置层级”混在了一起，而不完全是单一功能异常。若你的目标是只使用 Tavily，需要显式禁用内置 web_search，并确认配置写在 tools.web... 下，而不是顶层 web。如果方便的话，也建议补充一下你修改前后的 openclaw.json 相关片段以及重启后的实际变化，这样更容易判断是配置路径问题，还是启动阶段的配置同步导致了覆盖感。

[ashione]

Kimi

Thanks for the report. A quick clarification first, since this seems related to how the current mechanisms are separated:

tavily-search is a Skill, while web_search is a built-in OpenClaw tool. They are not automatic replacements for each other. At the moment, web_search supports brave (default), perplexity, and grok as providers; tavily is not part of the built-in web_search provider list. So even if tavily-search is enabled, Brave-related behavior can still appear as long as the system is still using built-in web_search.

Based on your description, this looks more like a mismatch between feature boundaries and config structure, rather than a single isolated malfunction. If your goal is to use Tavily only, the practical approach is to explicitly disable built-in web_search and make sure the config is written under tools.web..., not top-level web. If you can share the relevant openclaw.json fragment before and after restart, plus what changes after relaunch, that would help determine whether this is a config-path issue or startup-time config sync causing the reset-like behavior.

感谢反馈。这里先澄清一下当前机制，避免配置项理解偏差：

tavily-search 是一个 Skill，而 web_search 是 OpenClaw 内置工具，这两者不是自动替换关系。当前 web_search 支持的 provider 是 brave（默认）、perplexity、grok；tavily 不在 web_search 的 provider 列表里。因此，即使启用了 tavily-search，只要系统仍在调用内置 web_search，就仍然会出现 Brave 相关配置或行为。

从你描述的现象看，问题更像是“能力边界”和“配置层级”混在了一起，而不完全是单一功能异常。若你的目标是只使用 Tavily，需要显式禁用内置 web_search，并确认配置写在 tools.web... 下，而不是顶层 web。如果方便的话，也建议补充一下你修改前后的 openclaw.json 相关片段以及重启后的实际变化，这样更容易判断是配置路径问题，还是启动阶段的配置同步导致了覆盖感。

Kimi had been packed inside as builtin web search tool as well.
So we can notice an intersting thing that users might launch web search tool but failed cause API key is not belonged to international side of moonshot. What's a big pity.....
I also write a PR of related issue to overwrite kimi configuration which prevent cn site users to load i18n side base url. @vcfgv