Notify users when switching chat provider that web search has its own config

[max-my]

Problem

When a user switches their chat model provider (Settings → Models), the web-search-deepseek plugin does not follow — it keeps using its own endpoint (https://api.deepseek.com/anthropic/v1) and its own credential resolution (DEEPSEEK_API_KEY / the credentials seam).

This causes a confusing 401 error on the first web_search call after switching to a custom provider, with no indication that search config lives in a separate settings page.

Suggested improvement

Add a notification or banner in the UI when the model provider changes, telling the user that web search configuration is independent and pointing them to Settings → Plugins → Web search to review the endpoint and API key.

At minimum, the web_search tool result could surface a clearer error that names the search endpoint and explicitly explains the separation from chat model config.

Relevant source

• packages/web/web-search-deepseek/src/index.ts — plugin config, credential resolution (falls back from literal apiKey → credentials seam → env var DEEPSEEK_API_KEY)
• packages/web/web-search-deepseek/src/provider.ts — endpoint fallback chain (config.baseURL → DEEPSEEK_SEARCH_BASE_URL → hardcoded default), and the searchEndpointError() message that currently fires on failure

[laurence8023]

Thanks for maintaining DSH. Adding a related scenario that sits one step earlier, in case it is useful.

Scope note: this is the official DSH desktop build (DeepSeek Harness desktop app, @deepseek-ai/dsh-desktop-runtime@0.1.7-rc.2, DSH_HOME=~/.dsh, profile desktop, Nightly channel), signed in with an account only — not the community DSH Desktop packaging and not the npx @deepseek-ai/dsh web CLI / Web form. "DSH" below means that official desktop build.

For users who sign in with an account only and never configure an API key, web_search fails on its very first call (WEB_PROVIDER_CREDENTIAL_MISSING), and no hint is visible in the UI — so it is not even apparent that search has its own configuration.

The cause matches this thread: the search channel resolves DEEPSEEK_API_KEY, which is independent of the chat channel. The only difference is that these users never perform a provider switch.

Details, the config excerpt from the bundle, the refs / records credential distinction, and a minimal repro are in #7845:
#7845

If this overlaps with your thread, I am happy to merge or remove it. Thanks for reading.

---

感谢维护。这里补充一个更靠前的同类场景，供参考。

环境说明：本条针对官方 DSH 桌面版（DeepSeek Harness 桌面应用，运行时 @deepseek-ai/dsh-desktop-runtime@0.1.7-rc.2，DSH_HOME = ~/.dsh，profile desktop，Nightly 渠道），且走账号登录通道——不是社区打包的 DSH Desktop，也不是 CLI / Web 形态。

只用账号登录、未配置任何 API key 的用户，从第一次调用起 web_search 就会失败（WEB_PROVIDER_CREDENTIAL_MISSING），界面上也暂未看到相关引导——用户甚至无从得知「搜索有自己的配置」。

原因与本帖一致：搜索通道的凭据引用 DEEPSEEK_API_KEY 独立于聊天通道；差别只在于这类用户没有发生过「切换提供方」这个动作。

已在 #7845 中附上包内配置原文、refs／records 凭据类型的区别与最小复现：#7845

如与本帖视角重复，我可以随时合并或删除。感谢阅读。