[GH-ISSUE #20595] issue: "search_web" tool executed even when "Web Search" control disabled #57895

Closed
opened 2026-05-05 21:52:37 -05:00 by GiteaMirror · 17 comments
Owner

Originally created by @SlavikCA on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20595

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.7.2

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

Chrome

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

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

Image

Additional Information

No response

Originally created by @SlavikCA on GitHub (Jan 11, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20595 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.7.2 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) Chrome ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### 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 <img width="813" height="659" alt="Image" src="https://github.com/user-attachments/assets/b8306010-132f-4d8c-a6b8-aa669c58648a" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-05 21:52:37 -05:00
Author
Owner

@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:

  1. #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

  2. #20552 issue: Retrieval: list index out of range
    by outis151 • Jan 10, 2026 • bug

  3. #19825 Image Generation and Web Search trigger on every message
    by bcnation • Dec 08, 2025 • bug

  4. #17369 issue: Cannot disable web search
    by drycounty • Sep 11, 2025 • bug

  5. #20186 issue: WEB_SEARCH_DOMAIN_FILTER_LIST cannot be specified via an environment variable.
    by leagueofsoups • Dec 26, 2025 • bug

Show 5 more related issues
  1. #19698 issue: .41 web based search and webpages - RAG - are not fixed
    by frenzybiscuit • Dec 02, 2025 • bug

  2. #19925 issue: Model responses stop after web searches
    by tm-coder-484 • Dec 13, 2025 • bug

  3. #19668 issue: hybrid search setting doesnt stay active
    by arslancloud • Dec 01, 2025 • bug

  4. #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

  5. #18290 Web Search returns incomplete or inconsistent results
    by aimendenche-nw • Oct 13, 2025 • bug


💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3735913697 --> @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: 1. [#20327](https://github.com/open-webui/open-webui/issues/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`* 2. [#20552](https://github.com/open-webui/open-webui/issues/20552) **issue: Retrieval: list index out of range** *by outis151 • Jan 10, 2026 • `bug`* 3. [#19825](https://github.com/open-webui/open-webui/issues/19825) **Image Generation and Web Search trigger on every message** *by bcnation • Dec 08, 2025 • `bug`* 4. [#17369](https://github.com/open-webui/open-webui/issues/17369) **issue: Cannot disable web search** *by drycounty • Sep 11, 2025 • `bug`* 5. [#20186](https://github.com/open-webui/open-webui/issues/20186) **issue: WEB_SEARCH_DOMAIN_FILTER_LIST cannot be specified via an environment variable.** *by leagueofsoups • Dec 26, 2025 • `bug`* <details> <summary>Show 5 more related issues</summary> 6. [#19698](https://github.com/open-webui/open-webui/issues/19698) **issue: .41 web based search and webpages - RAG - are not fixed** *by frenzybiscuit • Dec 02, 2025 • `bug`* 7. [#19925](https://github.com/open-webui/open-webui/issues/19925) **issue: Model responses stop after web searches** *by tm-coder-484 • Dec 13, 2025 • `bug`* 8. [#19668](https://github.com/open-webui/open-webui/issues/19668) **issue: hybrid search setting doesnt stay active** *by arslancloud • Dec 01, 2025 • `bug`* 9. [#15135](https://github.com/open-webui/open-webui/issues/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`* 10. [#18290](https://github.com/open-webui/open-webui/issues/18290) **Web Search returns incomplete or inconsistent results** *by aimendenche-nw • Oct 13, 2025 • `bug`* </details> --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
Author
Owner

@Classic298 commented on GitHub (Jan 11, 2026):

intended behaviour. docs will be updated to correct that

<!-- gh-comment-id:3735918134 --> @Classic298 commented on GitHub (Jan 11, 2026): intended behaviour. docs will be updated to correct that
Author
Owner

@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

<!-- gh-comment-id:3803763141 --> @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
Author
Owner

@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."

<!-- gh-comment-id:3803849953 --> @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."
Author
Owner

@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.

<!-- gh-comment-id:3803855612 --> @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.
Author
Owner

@Ithanil 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.

Understood, "intended behavior" just got me the vibe that it is intended to stay like that.

<!-- gh-comment-id:3803861866 --> @Ithanil 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. Understood, "intended behavior" just got me the vibe that it is intended to *stay* like that.
Author
Owner

@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.

<!-- gh-comment-id:3832423649 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:3921530711 --> @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.
Author
Owner

@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

<!-- gh-comment-id:3921644295 --> @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
Author
Owner

@SlavikCA commented on GitHub (Feb 18, 2026):

Testing open-webui 0.8.3

  • with llama.cpp
  • model: qwen3-coder80b

Using native functions call

Code execution works, as expected.

WebSearch and URL fetch works, as expected!

Image
<!-- gh-comment-id:3922165037 --> @SlavikCA commented on GitHub (Feb 18, 2026): Testing open-webui 0.8.3 - with llama.cpp - model: qwen3-coder80b Using native functions call Code execution works, as expected. WebSearch and URL fetch works, as expected! <img width="1031" height="1677" alt="Image" src="https://github.com/user-attachments/assets/7c410ef5-1f21-4a14-9bc7-87464d52481a" />
Author
Owner

@Ithanil 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

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.

<!-- gh-comment-id:3922328710 --> @Ithanil commented on GitHub (Feb 18, 2026): > [@yz342](https://github.com/yz342) from 0.8.3 onwards, all the toggles do exactly again what they're supposed to do > > cc [@Ithanil](https://github.com/Ithanil) 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.
Author
Owner

@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:

  1. It's of course misleading that the Web Search toggle is there in the chat but does not affect the agentic search capability of the model.
  2. We definitely need a per chat toggle for built-in tools. Sometimes I work with sensitive documents and I definitely don't want the model to send any data to a search engine by mistake.

Thank you in advance.

<!-- gh-comment-id:4104333572 --> @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: 1. It's of course misleading that the `Web Search` toggle is there in the chat but does not affect the agentic search capability of the model. 2. We definitely need a per chat toggle for built-in tools. Sometimes I work with sensitive documents and I definitely don't want the model to send any data to a search engine by mistake. Thank you in advance.
Author
Owner

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

@rdner it is fixed

as confirmed above by me and multiple other people

<!-- gh-comment-id:4104348988 --> @Classic298 commented on GitHub (Mar 21, 2026): @rdner it is fixed as confirmed above by me and multiple other people
Author
Owner

@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 Calling set to Native.

On the screenshot you can see that the Web Search toggle is off but the model clearly searched 3 times. I expanded and checked that the search results were actually received.

Image
<!-- gh-comment-id:4104373846 --> @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 Calling` set to `Native`. On the screenshot you can see that the `Web Search` toggle is off but the model clearly searched 3 times. I expanded and checked that the search results were actually received. <img width="999" height="495" alt="Image" src="https://github.com/user-attachments/assets/1efd81b2-4a7c-4a57-bc21-629e7a428f58" />
Author
Owner

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

@rdner do you have web search always on toggled in settings > interface?

<!-- gh-comment-id:4104399150 --> @Classic298 commented on GitHub (Mar 21, 2026): @rdner do you have web search always on toggled in settings > interface?
Author
Owner

@rdner commented on GitHub (Mar 21, 2026):

@Classic298 yes, you're right! Thanks a lot!

Changing Interface -> Web Search in Chat from Always to Default fixed it for me.

To be honest, I don't remember setting this to Always but now when it's set to Default the model does not have access to search_web anymore (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 🙂

<!-- gh-comment-id:4104420502 --> @rdner commented on GitHub (Mar 21, 2026): @Classic298 yes, you're right! Thanks a lot! Changing `Interface -> Web Search in Chat` from `Always` to `Default` fixed it for me. To be honest, I don't remember setting this to `Always` but now when it's set to `Default` the model does not have access to `search_web` anymore (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 🙂
Author
Owner

@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

<!-- gh-comment-id:4104497019 --> @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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#57895