web_search disabled by default — no tools.web section, no provider configured

Release: v2026.7.1-3
Reporter: Pedro Larroy

Description

web_search doesn't work out of the box. Default config ships with no tools.web section at all — no provider, no API key — so any web_search call returns "disabled or no provider available."

Observed

Agent diagnosis (from live session):

Your config has no tools.web section at all — no provider, no API key. That's why it returns "disabled or no provider available."

Expected

Web search should work with a sane zero-config default (e.g. DuckDuckGo, no key required), or the app should clearly surface in Settings that web search is unconfigured and guide the user to pick a provider, instead of failing silently mid-chat.

Suggested fix

Default tools.web.search.provider to duckduckgo (free, no key) out of the box, with option to switch to Brave/Perplexity/Gemini/Grok/Exa/SearXNG for durability (DuckDuckGo can rate-limit/captcha under load).

Note: web_fetch is enabled by default and works fine — this only affects web_search.

No files or tests are named. Start by locating the default configuration and the web_search provider and Settings handling; compare them with the working web_fetch path. Done means web_search either works with a zero-configuration DuckDuckGo default or clearly identifies the missing configuration and guides the user to choose a provider.