[GH-ISSUE #22545] issue: Certain Builtin Tools Not Available #19743

New Issue

2026-04-20T02:15:03-05:00

GiteaMirror commented

2026-04-20 02:15:03 -05:00

Originally created by @pdp-oui on GitHub (Mar 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22545

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

v0.8.10

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

Any

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

Prior to 0.8.10, web search was automatically triggered when a model needed to reach out to the internet, if the following conditions were met:

native tool calling was enabled and the capability was enabled in the model
Web Search was enabled in "Capabilities"
Web Search was enabled in "Builtin Tools"
Web Search was disabled in "Default Features"

Actual Behavior

Since the upgrade, web search needs to be enabled in the integrations menu for the model to see the function available to it.

Disabled in Integration Menu:

Enabled in Integration Menu:

Steps to Reproduce

Disable the integration via menu:

Logs & Screenshots

See above

Additional Information

Is this the intended behavior, and was this a bug prior to 0.8.10

Originally created by @pdp-oui on GitHub (Mar 10, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22545 ### 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 v0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) Any ### 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 Prior to 0.8.10, web search was automatically triggered when a model needed to reach out to the internet, if the following conditions were met: - native tool calling was enabled and the capability was enabled in the model - Web Search was enabled in "Capabilities" - Web Search was enabled in "Builtin Tools" - Web Search was disabled in "Default Features" ### Actual Behavior Since the upgrade, web search needs to be enabled in the integrations menu for the model to see the function available to it. Disabled in Integration Menu: <img width="740" height="980" alt="Image" src="https://github.com/user-attachments/assets/eb4d71b8-706d-4462-9972-0a90dd67f2c2" /> Enabled in Integration Menu: <img width="740" height="980" alt="Image" src="https://github.com/user-attachments/assets/1ad2bcb3-42fc-4bb5-ad32-7f4c625168c9" /> ### Steps to Reproduce Disable the integration via menu: <img width="302" height="139" alt="Image" src="https://github.com/user-attachments/assets/9f663e10-a0a0-494a-9c1f-2246ebdde69d" /> ### Logs & Screenshots See above ### Additional Information Is this the intended behavior, and was this a bug prior to 0.8.10

GiteaMirror added the bug label 2026-04-20 02:15:03 -05:00

GiteaMirror closed this issue

2026-04-20 02:15:04 -05:00

GiteaMirror commented

2026-04-20 02:15:05 -05:00

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

This changed a few versions ago, and was prominently noted in the changed section.

The documentation was updated too to reflect this

Intended behaviour, not a bug

@Classic298 commented on GitHub (Mar 10, 2026): This changed a few versions ago, and was prominently noted in the changed section. The documentation was updated too to reflect this Intended behaviour, not a bug