[PR #1117] [MERGED] docs: Add missing Default Features step to agentic search setup #1115

New issue

Closed

opened 2026-10-18 14:17:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:17:15 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1117
Author: @sllrs
Created: 3/2/2026
Status: ✅ Merged
Merged: 3/2/2026
Merged by: @Classic298

Base: main ← Head: fix/agentic-search-default-features-docs

📝 Commits (1)

257be16 docs: Add missing Default Features step to agentic search setup

📊 Changes

1 file changed (+6 additions, -5 deletions)

View changed files

📝 docs/features/chat-conversations/web-search/agentic-search.mdx (+6 -5)

📄 Description

Summary

The Agentic Search setup guide is missing a required step: enabling Web Search under Default Features in the model settings.

Without this, the search_web and fetch_url tools are not injected in Native Mode — even when the Web Search capability and Builtin Tools are both enabled. The model receives other builtin tools (time, memory, notes, etc.) but not the web search tools.

This was confirmed on v0.8.7 and relates to the behavioral change introduced in open-webui/open-webui#20641 (commits c46ef3b and f1a1e64), which made the per-chat and Default Features toggles functional in Native Mode.

Changes

Added step 3 ("Enable Default Feature") to the setup instructions
Updated the tip box to clarify that both the Web Search capability and the Default Features toggle (or per-chat toggle) control tool injection in Native Mode
Corrected the previous statement that "The chat toggle is not required" — it is now relevant after the above fix

Steps to reproduce the original issue

Configure Brave (or any provider) in Admin → Settings → Web Search
On a model, enable Web Search capability + Builtin Tools
Set Function Calling to Native
Leave Default Features → Web Search unchecked
Start a new chat and ask a question requiring current information
The model will respond saying it has no web search tools available
Enable Default Features → Web Search → the model now calls search_web correctly

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/1117 **Author:** [@sllrs](https://github.com/sllrs) **Created:** 3/2/2026 **Status:** ✅ Merged **Merged:** 3/2/2026 **Merged by:** [@Classic298](https://github.com/Classic298) **Base:** `main` ← **Head:** `fix/agentic-search-default-features-docs` --- ### 📝 Commits (1) - [`257be16`](https://github.com/open-webui/docs/commit/257be16fafc7413e34c32f0be16b882735603c2a) docs: Add missing Default Features step to agentic search setup ### 📊 Changes **1 file changed** (+6 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `docs/features/chat-conversations/web-search/agentic-search.mdx` (+6 -5) </details> ### 📄 Description ## Summary The [Agentic Search setup guide](https://docs.openwebui.com/features/chat-conversations/web-search/agentic-search/) is missing a required step: enabling **Web Search** under **Default Features** in the model settings. Without this, the `search_web` and `fetch_url` tools are not injected in Native Mode — even when the Web Search capability and Builtin Tools are both enabled. The model receives other builtin tools (time, memory, notes, etc.) but not the web search tools. This was confirmed on **v0.8.7** and relates to the behavioral change introduced in [open-webui/open-webui#20641](https://github.com/open-webui/open-webui/issues/20641) (commits `c46ef3b` and `f1a1e64`), which made the per-chat and Default Features toggles functional in Native Mode. ## Changes - Added **step 3** ("Enable Default Feature") to the setup instructions - Updated the tip box to clarify that both the Web Search capability *and* the Default Features toggle (or per-chat toggle) control tool injection in Native Mode - Corrected the previous statement that "The chat toggle is not required" — it is now relevant after the above fix ## Steps to reproduce the original issue 1. Configure Brave (or any provider) in Admin → Settings → Web Search 2. On a model, enable Web Search capability + Builtin Tools 3. Set Function Calling to Native 4. Leave Default Features → Web Search **unchecked** 5. Start a new chat and ask a question requiring current information 6. The model will respond saying it has no web search tools available 7. Enable Default Features → Web Search → the model now calls `search_web` correctly --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:17:15 +00:00