[GH-ISSUE #14249] issue: Capability Button Status stored across models, causes errors. #32720

Closed
opened 2026-04-25 06:35:55 -05:00 by GiteaMirror · 2 comments
Owner

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

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

Installation Method

Docker

Open WebUI Version

0.6.10

Ollama Version (if applicable)

built in

Operating System

Windows 11

Browser (if applicable)

Edge

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 listed steps to reproduce the bug in detail.

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

  1. create a model that has image generation capabilities turned on.
  2. create a model that has image generation capabilities turned off.
  3. go to a new chat with the model that has image generation capabilities and turn on the image generation button.
  4. start a new chat with the model without image generation capabilities
  5. the button is not available to turn on or off which is expected.
  6. send a chat message to the model without image generation capabilities turned on.
  7. the model sends a request to "ComfyUI" or "SD" to generate an image and shows the message "Generating Image..."
  8. close the browser and then come back to the chat window.
  9. image generation button status is still stored and will continue generating images.

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

Image

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.

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 - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.10 ### Ollama Version (if applicable) built in ### Operating System Windows 11 ### Browser (if applicable) Edge ### 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 listed steps to reproduce the bug in detail. ### 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 1) create a model that has image generation capabilities turned on. 2) create a model that has image generation capabilities turned off. 3) go to a new chat with the model that has image generation capabilities and turn on the image generation button. 4) start a new chat with the model without image generation capabilities 5) the button is not available to turn on or off which is expected. 6) send a chat message to the model without image generation capabilities turned on. 7) the model sends a request to "ComfyUI" or "SD" to generate an image and shows the message "Generating Image..." 8) close the browser and then come back to the chat window. 9) image generation button status is still stored and will continue generating images. 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 ![Image](https://github.com/user-attachments/assets/81e64a64-bd8e-4036-a303-2d31745ad2ee) ### 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.
GiteaMirror added the bug label 2026-04-25 06:35:55 -05:00
Author
Owner

@tjbck commented on GitHub (May 23, 2025):

Should be addressed with 88a296b989

<!-- gh-comment-id:2905650083 --> @tjbck commented on GitHub (May 23, 2025): Should be addressed with 88a296b989f5104eab2218945c2819c42e50a566
Author
Owner

@digitalassassins commented on GitHub (May 24, 2025):

speedy response and fix, thank you :)

<!-- gh-comment-id:2906259611 --> @digitalassassins commented on GitHub (May 24, 2025): speedy response and fix, thank you :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#32720