github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-15 21:19:39 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #14632] issue: Tools are all disabled by default despite being enabled specifically for a model #137045

New Issue
Closed
opened 2026-05-25 06:04:46 -05:00 by GiteaMirror · 11 comments
GiteaMirror commented 2026-05-25 06:04:46 -05:00
Owner
Copy Link

Originally created by @mkotzerke on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14632

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.13

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

No response

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

All Tools that are explicitly allowed for a model are enabled if a user starts a chat.

Actual Behavior

All tools are disabled and need to be manually toggled on.

Steps to Reproduce

Clear browser cookies and start new chat. Have tools enabled for a model in its setting

Logs & Screenshots

Image

Image

Additional Information

This is a terrible user experience because the non technical users are not aware of this and complain about the search for jira, confluence,... not working as before (This behaviour changed since i upgraded to current version).

Please restore previous behaviour and/or let this be explicitly configured by a setting flag (tools for model turned on/off by default).
I need to create a default user experience without every user having to manually toggle on tools.

Originally created by @mkotzerke on GitHub (Jun 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14632 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.13 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) _No response_ ### 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 All Tools that are explicitly allowed for a model are enabled if a user starts a chat. ### Actual Behavior All tools are disabled and need to be manually toggled on. ### Steps to Reproduce Clear browser cookies and start new chat. Have tools enabled for a model in its setting ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/277ca013-6510-4b32-89d3-d24263315b8d) ![Image](https://github.com/user-attachments/assets/7902973e-2d40-4b13-9a18-7f437c8872a9) ### Additional Information This is a terrible user experience because the non technical users are not aware of this and complain about the search for jira, confluence,... not working as before (This behaviour changed since i upgraded to current version). Please restore previous behaviour and/or let this be explicitly configured by a setting flag (tools for model turned on/off by default). I need to create a default user experience without every user having to manually toggle on tools.
GiteaMirror added the bug label 2026-05-25 06:04:46 -05:00
GiteaMirror commented 2026-05-25 06:04:51 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jun 3, 2025):

Addressed with c01e29c47f in dev!

<!-- gh-comment-id:2936551354 --> @tjbck commented on GitHub (Jun 3, 2025): Addressed with c01e29c47f07a72eb40689291b5d3dd62b818010 in dev!
GiteaMirror commented 2026-05-25 06:04:52 -05:00
Author
Owner
Copy Link

@akhilpocket23 commented on GitHub (Jun 12, 2025):

I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool.

<!-- gh-comment-id:2965870803 --> @akhilpocket23 commented on GitHub (Jun 12, 2025): I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool.
GiteaMirror commented 2026-05-25 06:04:53 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Jun 15, 2025):

I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool.

I am not able to reproduce this issue. Are you able to provide accurate reproduction steps for me to try?

<!-- gh-comment-id:2973465493 --> @silentoplayz commented on GitHub (Jun 15, 2025): > I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool. I am not able to reproduce this issue. Are you able to provide accurate reproduction steps for me to try?
GiteaMirror commented 2026-05-25 06:04:54 -05:00
Author
Owner
Copy Link

@visualcshape commented on GitHub (Jun 20, 2025):

I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool.

Hi, I have the same issue. My reproduction steps are:

  1. Ask a question, the tools are enabled by default.
  2. The model answered the question. The tool remains enabled.
  3. Refreshed the page.
  4. The tools are disabled on the chat.

If I don't refresh the page, the tools remain enabled. Howerver, If I refresh the page, or switch to another chat and back to the chat, the tools are disabled, which I expected is the tools are enabled.

My version is 0.6.15.

<!-- gh-comment-id:2990234818 --> @visualcshape commented on GitHub (Jun 20, 2025): > I am also facing one more issue .. when I enable tool, ask a question it works fine . but when I try to ask a follow up question , tools get disabled by default and gives response without using tool. Hi, I have the same issue. My reproduction steps are: 1. Ask a question, the tools are enabled by default. 2. The model answered the question. The tool remains enabled. 3. Refreshed the page. 4. The tools are disabled on the chat. If I don't refresh the page, the tools remain enabled. Howerver, If I refresh the page, or switch to another chat and back to the chat, the tools are disabled, which I expected is the tools are enabled. My version is 0.6.15.
GiteaMirror commented 2026-05-25 06:04:56 -05:00
Author
Owner
Copy Link

@podlisk commented on GitHub (Aug 20, 2025):

I am having exact the same issue as the message above.
My version 0.6.22

<!-- gh-comment-id:3204343946 --> @podlisk commented on GitHub (Aug 20, 2025): I am having exact the same issue as the message above. My version 0.6.22
GiteaMirror commented 2026-05-25 06:05:02 -05:00
Author
Owner
Copy Link

@pljones commented on GitHub (Nov 1, 2025):

Hi,

I'm still seeing this in v0.6.34.

<!-- gh-comment-id:3476351239 --> @pljones commented on GitHub (Nov 1, 2025): Hi, I'm still seeing this in v0.6.34.
GiteaMirror commented 2026-05-25 06:05:06 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Nov 1, 2025):

Hi,

I'm still seeing this in v0.6.34.

I'm unable to reproduce any of the issues described in this closed issue post. If you can provide reproduction steps that you believe would trigger this issue on my end, please provide them!

<!-- gh-comment-id:3476459580 --> @silentoplayz commented on GitHub (Nov 1, 2025): > Hi, > > I'm still seeing this in v0.6.34. I'm unable to reproduce any of the issues described in this closed issue post. If you can provide reproduction steps that you believe would trigger this issue on my end, please provide them!
GiteaMirror commented 2026-05-25 06:05:08 -05:00
Author
Owner
Copy Link

@pljones commented on GitHub (Nov 1, 2025):

Well, its pretty easy: run Open WebUI, configure the tools. Turn the tools on. Close that chat and start a new chat. They're not active. The state is expected to persist and it doesn't.

I'll do a video... tomorrow if I get time.

<!-- gh-comment-id:3476665392 --> @pljones commented on GitHub (Nov 1, 2025): Well, its pretty easy: run Open WebUI, configure the tools. Turn the tools on. Close that chat and start a new chat. They're not active. The state is expected to persist and it doesn't. I'll do a video... tomorrow if I get time.
GiteaMirror commented 2026-05-25 06:05:09 -05:00
Author
Owner
Copy Link

@pljones commented on GitHub (Nov 2, 2025):

You can watch the whole thing to see how hard it was to find a repeatable recipe for producing the issue. Or skip to the two minute mark to see that it's repeatable. It'll make more sense watching it all, I think.

https://github.com/user-attachments/assets/66167af5-cfe0-48c6-901e-4105bed87e05

The expected behaviour is that once "default" chats start with the tools enable, any new chat, regardless of the preceding context should also start with the tools enabled.

What actually happens depends on how you start the new chat -- and that leads to further confusion...

<!-- gh-comment-id:3477825389 --> @pljones commented on GitHub (Nov 2, 2025): You can watch the whole thing to see how hard it was to find a repeatable recipe for producing the issue. Or skip to the two minute mark to see that it's repeatable. It'll make more sense watching it all, I think. https://github.com/user-attachments/assets/66167af5-cfe0-48c6-901e-4105bed87e05 The _expected_ behaviour is that once "default" chats start with the tools enable, any _new_ chat, regardless of the preceding context should also start with the tools enabled. What actually happens depends on how you start the new chat -- and that leads to further confusion...
GiteaMirror commented 2026-05-25 06:05:10 -05:00
Author
Owner
Copy Link

@pljones commented on GitHub (Nov 3, 2025):

Hi silentoplayz,

OK, so this one captures it a bit better:

  1. Open a chat where the tools were disabled.
  2. Then start a new chat and check the tool status - disabled...
  3. Then ask a question that needs tool use:

https://github.com/user-attachments/assets/52efa46f-7160-40e0-b48d-0b3b20c6dade

Expected result ... well, confusion rules here. Ideally, do what the UI actually says but what the problem is appears to be that the tools are enabled but the UI isn't showing that correctly.

<!-- gh-comment-id:3480318057 --> @pljones commented on GitHub (Nov 3, 2025): Hi [silentoplayz](https://github.com/silentoplayz), OK, so this one captures it a bit better: 1. Open a chat where the tools _were_ disabled. 2. Then start a new chat and check the tool status - disabled... 3. Then ask a question that needs tool use: https://github.com/user-attachments/assets/52efa46f-7160-40e0-b48d-0b3b20c6dade Expected result ... well, confusion rules here. Ideally, do what the UI actually says but what the problem is appears to be that the tools are enabled but the UI isn't showing that correctly.
GiteaMirror commented 2026-05-25 06:05:11 -05:00
Author
Owner
Copy Link

@xITmasterx commented on GitHub (May 22, 2026):

Has anyone actually fixed this issue? It's becoming really annoying.

<!-- gh-comment-id:4515625236 --> @xITmasterx commented on GitHub (May 22, 2026): Has anyone actually fixed this issue? It's becoming really annoying.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#137045
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?