mirror of
https://github.com/open-webui/open-webui.git
synced 2026-11-09 10:50:35 -06:00
[GH-ISSUE #14249] issue: Capability Button Status stored across models, causes errors. #32720
Reference in New Issue
Block a user
Originally created by @digitalassassins on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14249
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.10
Ollama Version (if applicable)
built in
Operating System
Windows 11
Browser (if applicable)
Edge
Confirmation
README.md.Expected Behavior
On one model that has the image generation capability turned on, tick the button for image generation. Type into the chat and receive an image. works fine.
Switch to a model that doesn't have image generation capabilities turned on in its settings.
Switch on the Web Search button and do a web search. The model to just do a web search.
Actual Behavior
When switching from a model with image generation button turned on, to a model that has the capability turned off. still results in that model generating the image.
The image button state is stored between chat windows for different models.
This shouldn't happen. as you cant click the button to turn off image generation without switching back to a model that has the image generation button to turn on and off.
When switching to a new chat with a different model. The status of the buttons should change based on the model's capabilities.
Steps to Reproduce
Only way to switch it off, is by going back to a model that has image generation capabilities and turning the button status to off..
Logs & Screenshots
Additional Information
Basically, the button status is saved between models and new chats, but the button status should reset for a new chat to prevent the issue. Alternatively a check to see if the model has the ability and if not then disable the button status.
@tjbck commented on GitHub (May 23, 2025):
Should be addressed with
88a296b989@digitalassassins commented on GitHub (May 24, 2025):
speedy response and fix, thank you :)