github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-22 09:31:58 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #12756] Issue: Banners don't show to users when two or models are selected. #87446

New Issue
Closed
opened 2026-05-15 11:55:19 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-15 11:55:19 -05:00
Owner
Copy Link

Originally created by @DmitriyAlergant on GitHub (Apr 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12756

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

Ollama Version (if applicable)

No response

Operating System

Docker

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

Expected Behavior

Expected behavior is that users see admin-pinned Banners (announcements) regardless of their models selection.

Actual Behavior

Observed behavior is that users only see the banners if only one model is selected. When 2 or more models are selected for concurrent call, banners don't show.

Steps to Reproduce

  1. Go to Settings -> Interface and add an INFO banner
  2. Go back to chat and select any two models. Banner does not show up
  3. Remove an extra model and keep one. Banner shows up again.

Logs & Screenshots

n/a

Additional Information

While this may have been a conscious design decisions ("save space"), it is controversial in many contexts.

Since WebUI allows to set a combination of models as a default, this means such users will stop seeing banners completely. This is not desirable.

In our company we start recommending users to use 2 models concurrently for continous evaluation of what works better for their use-cases. They want us to tell what to use (Sonnet or Gemini 2.5) and we don't know. We want them to use both and decide for themselves. Some users would actually make the "2 models" their temporary default. We don't want them to miss the banners.

Originally created by @DmitriyAlergant on GitHub (Apr 11, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/12756 ### 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.0 ### Ollama Version (if applicable) _No response_ ### Operating System Docker ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior Expected behavior is that users see admin-pinned Banners (announcements) regardless of their models selection. ### Actual Behavior Observed behavior is that users only see the banners if only one model is selected. When 2 or more models are selected for concurrent call, banners don't show. ### Steps to Reproduce 1. Go to Settings -> Interface and add an INFO banner 2. Go back to chat and select any two models. Banner does not show up 3. Remove an extra model and keep one. Banner shows up again. ### Logs & Screenshots n/a ### Additional Information While this may have been a conscious design decisions ("save space"), it is controversial in many contexts. Since WebUI allows to set a combination of models as a default, this means such users will stop seeing banners completely. This is not desirable. In our company we start recommending users to use 2 models concurrently for continous evaluation of what works better for their use-cases. They want us to tell what to use (Sonnet or Gemini 2.5) and we don't know. We want them to use both and decide for themselves. Some users would actually make the "2 models" their temporary default. We don't want them to miss the banners.
GiteaMirror added the bug label 2026-05-15 11:55:19 -05:00
GiteaMirror commented 2026-05-15 11:55:21 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 11, 2025):

PLEASE check for exisiting issues/discussions. Intended behaviour.

<!-- gh-comment-id:2798006524 --> @tjbck commented on GitHub (Apr 11, 2025): PLEASE check for exisiting issues/discussions. Intended behaviour.
GiteaMirror commented 2026-05-15 11:55:22 -05:00
Author
Owner
Copy Link

@DmitriyAlergant commented on GitHub (Apr 11, 2025):

@tjbck

Yes you are right I missed it (was only searching open issues, not including closed).

Would you potentially reconsider this intended behavior?

Like I said, the problem is the users who select 2 models as their default. In this case they will never be seeing the banners. Which undermines the purpose of banners to convey important information from admins to users.

<!-- gh-comment-id:2798027062 --> @DmitriyAlergant commented on GitHub (Apr 11, 2025): @tjbck Yes you are right I missed it (was only searching open issues, not including closed). Would you potentially **reconsider** this intended behavior? Like I said, the problem is the users who select 2 models _**as their default**_. In this case they will never be seeing the banners. Which undermines the purpose of banners to convey important information from admins to users.
GiteaMirror commented 2026-05-15 11:55:23 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 11, 2025):

Addressed with 30d02c638c

<!-- gh-comment-id:2798122414 --> @tjbck commented on GitHub (Apr 11, 2025): Addressed with 30d02c638c8a51449da21c09c830245232e6c0c1
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#87446
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?