[GH-ISSUE #22719] feat: How to make web search trigger autonomously based on model judgment? #19796

New Issue

GiteaMirror · 2026-04-20T02:17:47-05:00

GiteaMirror commented

2026-04-20 02:17:47 -05:00

Originally created by @4LONpSPlKJit0 on GitHub (Mar 16, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22719

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

When web search is enabled as a model Capability, it triggers broadly across most queries — including ones that clearly don't need external information, such as internal document lookups or general knowledge questions. There is currently no way to let the model intelligently decide whether web search is needed based on the query itself.
Environment: Open WebUI 0.7.2

Desired Solution you'd like

Expose web search as a callable Tool (alongside other tools like a knowledge base) so the model can choose whether to invoke it based on query context — similar to how custom Tools work today. This would allow the model to reason:

"This asks about real-time/external info → call web search"
"This asks about internal documents → call knowledge base only"
"This is a general question → answer directly, no tools needed"

Alternatives Considered

Tried adding priority rules to the system prompt and Tool Call Prompt (e.g., "only use web search for external/real-time queries"), but the built-in web search Capability bypasses tool call logic and does not reliably follow prompt instructions.

Additional Context

No response

Originally created by @4LONpSPlKJit0 on GitHub (Mar 16, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22719 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description When web search is enabled as a model Capability, it triggers broadly across most queries — including ones that clearly don't need external information, such as internal document lookups or general knowledge questions. There is currently no way to let the model intelligently decide whether web search is needed based on the query itself. Environment: Open WebUI 0.7.2 ### Desired Solution you'd like Expose web search as a callable Tool (alongside other tools like a knowledge base) so the model can choose whether to invoke it based on query context — similar to how custom Tools work today. This would allow the model to reason: "This asks about real-time/external info → call web search" "This asks about internal documents → call knowledge base only" "This is a general question → answer directly, no tools needed" ### Alternatives Considered Tried adding priority rules to the system prompt and Tool Call Prompt (e.g., "only use web search for external/real-time queries"), but the built-in web search Capability bypasses tool call logic and does not reliably follow prompt instructions. ### Additional Context _No response_

GiteaMirror closed this issue

2026-04-20 02:17:48 -05:00

GiteaMirror commented

2026-04-20 02:17:50 -05:00

@jndao commented on GitHub (Mar 16, 2026):

Hey!

I believe this is a feature already available in openwebui
https://docs.openwebui.com/features/extensibility/plugin/tools/#-native-mode-agentic-mode--system-function-calling--recommended

Native Mode (also called Agentic Mode) leverages the model's built-in capability to handle tool definitions and return structured tool calls (JSON).

@jndao commented on GitHub (Mar 16, 2026): Hey! I believe this is a feature already available in openwebui https://docs.openwebui.com/features/extensibility/plugin/tools/#-native-mode-agentic-mode--system-function-calling--recommended > Native Mode (also called Agentic Mode) leverages the model's built-in capability to handle tool definitions and return structured tool calls (JSON).

GiteaMirror commented

2026-04-20 02:17:50 -05:00

@Classic298 commented on GitHub (Mar 16, 2026):

use native function calling

https://docs.openwebui.com/features/chat-conversations/web-search/agentic-search

@Classic298 commented on GitHub (Mar 16, 2026): use native function calling https://docs.openwebui.com/features/chat-conversations/web-search/agentic-search

GiteaMirror referenced this issue

2026-04-20 05:53:55 -05:00

[PR #19796] [CLOSED] fix: MCP OAuth discovery via Protected Resource metadata flow #25348

GiteaMirror referenced this issue

2026-04-25 08:33:26 -05:00

[GH-ISSUE #19794] MCP OAuth 2.1: Not following WWW-Authenticate → Protected Resource → Authorization Server discovery chain #34525

GiteaMirror referenced this issue

2026-04-25 13:19:13 -05:00

[PR #19796] [CLOSED] fix: MCP OAuth discovery via Protected Resource metadata flow #40978

GiteaMirror referenced this issue

2026-04-30 00:12:45 -05:00

[PR #19796] [CLOSED] fix: MCP OAuth discovery via Protected Resource metadata flow #48396