mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #20595] issue: "search_web" tool executed even when "Web Search" control disabled #57895
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SlavikCA on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20595
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.7.2
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
I expect that if "Web Search" UI is disabled, then no "search_web" will be used.
Actual Behavior
"search_web" used even though "Web Search" UI is disabled
Steps to Reproduce
I have Function call set to NATIVE
Using llama.cpp with GLM 4.6V model
"Web Search" UI is disabled
Logs & Screenshots
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 11, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20327 issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance
by galvanoid • Jan 02, 2026 •
bug#20552 issue: Retrieval: list index out of range
by outis151 • Jan 10, 2026 •
bug#19825 Image Generation and Web Search trigger on every message
by bcnation • Dec 08, 2025 •
bug#17369 issue: Cannot disable web search
by drycounty • Sep 11, 2025 •
bug#20186 issue: WEB_SEARCH_DOMAIN_FILTER_LIST cannot be specified via an environment variable.
by leagueofsoups • Dec 26, 2025 •
bugShow 5 more related issues
#19698 issue: .41 web based search and webpages - RAG - are not fixed
by frenzybiscuit • Dec 02, 2025 •
bug#19925 issue: Model responses stop after web searches
by tm-coder-484 • Dec 13, 2025 •
bug#19668 issue: hybrid search setting doesnt stay active
by arslancloud • Dec 01, 2025 •
bug#15135 issue: When BYPASS_WEB_SEARCH_WEB_LOADER is set to true for internet search, the data was not properly populated
by Yuan-HuiBin • Jun 19, 2025 •
bug#18290 Web Search returns incomplete or inconsistent results
by aimendenche-nw • Oct 13, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@Classic298 commented on GitHub (Jan 11, 2026):
intended behaviour. docs will be updated to correct that
@Ithanil commented on GitHub (Jan 27, 2026):
@Classic298 Not allowing the user any control about the injected tools is a very bad take in my opinion.
For me it means that I need to add more and more changes to my fork, because most of the tools are only desirable in certain situations and otherwise just pollute the context, adding cost and degrading quality. Furthermore, in a fully local deployment with local models, web search is the only way for PII to leave the system and thus needs to be disabled by default. I hope this kinda implementation isn't the final "word".
EDIT: As I can see, at least in "dev" the admin can now disable certain builtin tools. That's a much needed improvement. Returning easy controls for web search etc. to the user should be the next.
EDIT2: I hope that will come soon https://github.com/open-webui/open-webui/issues/19397#issuecomment-3781478576
@Classic298 commented on GitHub (Jan 27, 2026):
@Ithanil
https://github.com/open-webui/open-webui/pull/20729#issuecomment-3767536015
"toggles for builtin tools are wip."
@Classic298 commented on GitHub (Jan 27, 2026):
"Not allowing the user any control about the injected tools is a very bad take in my opinion."
This is not a take and this is not my opinion
This is how it is right now and as for now this is intended behaviour.
And as Tim wrote, and I clarified under multiple issues, toggles for builtin tools are WIP - therefore any "issue" is in reality just a feature request. Because for now it is intended that if builtin tools are activated that all tools are injected.
@Ithanil commented on GitHub (Jan 27, 2026):
Understood, "intended behavior" just got me the vibe that it is intended to stay like that.
@ddekany commented on GitHub (Feb 2, 2026):
If the web search toggle is not supported combined with native FC (in the free version), then do not show it in that case. Documenting this won't help the average user. They will just correctly asses that Open WebUI has a bug there. The bug is that you show the toggle to disable web search, when you will do web search regardless.
@yz342 commented on GitHub (Feb 18, 2026):
A simple way is to create a filter function within open webui, to modify the request body, such that
if web search is toggled on, builtin-tools is enabled. Otherwise builtin-tool is disabled.
@Classic298 commented on GitHub (Feb 18, 2026):
@yz342 from 0.8.3 onwards, all the toggles do exactly again what they're supposed to do
cc @Ithanil
@SlavikCA commented on GitHub (Feb 18, 2026):
Testing open-webui 0.8.3
Using native functions call
Code execution works, as expected.
WebSearch and URL fetch works, as expected!
@Ithanil commented on GitHub (Feb 18, 2026):
That's correct. Although I still don't understand why that single lines
features.get...wasn't added in the first place. 😜 In my fork it worked like that all the time.@rdner commented on GitHub (Mar 21, 2026):
Hello everybody, I'm trying to understand why this issue got closed. Is there anywhere I can track progress on fixing this bug?
I'm running Open Web UI v0.8.10 and I can still see the behavior described here:
Web Searchtoggle is there in the chat but does not affect the agentic search capability of the model.Thank you in advance.
@Classic298 commented on GitHub (Mar 21, 2026):
@rdner it is fixed
as confirmed above by me and multiple other people
@rdner commented on GitHub (Mar 21, 2026):
Am I doing something wrong?
Open Web UI v0.8.10
Model: Qwen3.5-35B-A3B-4bit (oMLX) with
Function Callingset toNative.On the screenshot you can see that the
Web Searchtoggle is off but the model clearly searched 3 times. I expanded and checked that the search results were actually received.@Classic298 commented on GitHub (Mar 21, 2026):
@rdner do you have web search always on toggled in settings > interface?
@rdner commented on GitHub (Mar 21, 2026):
@Classic298 yes, you're right! Thanks a lot!
Changing
Interface -> Web Search in ChatfromAlwaystoDefaultfixed it for me.To be honest, I don't remember setting this to
Alwaysbut now when it's set toDefaultthe model does not have access tosearch_webanymore (as expected).I still think it's a bit misleading: if the setting was set to
Always, why did the Chat UI let me disable the web-search and displayed it as disabled? I think it would be a fair suggestion to improve this UX 🙂@Classic298 commented on GitHub (Mar 21, 2026):
@rdner i raised this long ago, was closed because it is intended. apparently some other chat UIs handle it this way