github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #13456] issue: setting a private model for title generation should show a warning #55582

New Issue
Closed
opened 2026-05-05 17:40:04 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 17:40:04 -05:00
Owner
Copy Link

Originally created by @thiswillbeyourgithub on GitHub (May 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13456

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

Git Clone

Open WebUI Version

v0.6.5

Ollama Version (if applicable)

No response

Operating System

all

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

Expected Behavior

The admin should be notified when setting a private model in the tasks, as it forbids the naming of chats for non admin users.

I do think that it would be an improvement to display a warning to the admin in the interface settings if the models set are private.

Actual Behavior

The current behavior for task (title generation, tag generation etc) is that if the admin set the model to a model that is not accessible to this user (because private or not in the appropriate permission) then no titles will be generated.

Even worse: if the admin does NOT set a title generation model, the chats will be named by the start of the first user message (which is ugly but usable), but if we set a private model all chats will be named "New Chat" (which makes it impossible to find anything)

Steps to Reproduce

  1. Set the title generation llm to a private model
  2. Create chats as a non admin
  3. Notice the private model is never called
  4. Notice that the admin has no way to know this happened

Logs & Screenshots

Irrelevant

Additional Information

  • It is entirely not obvious that "private" also means that they will not be doing interface related tasks, I thought that it only was about actual chats.
  • Furthermore, this happens silently (no debug nor warning in the logs for the admin that
  • This is particularly annoying because the admin can go months without knowing that the chat title of the non admin user is broken unless a user tells them.
  • Even more important now that models are private by default

While I do think that it should not be the case because generating those tasks is not something the the user has access over (it just happens without his intervention), I read in another issue that you deem it expected behavior so I wont argue with that.

Originally created by @thiswillbeyourgithub on GitHub (May 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13456 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 Git Clone ### Open WebUI Version v0.6.5 ### Ollama Version (if applicable) _No response_ ### Operating System all ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior The admin should be notified when setting a private model in the tasks, as it forbids the naming of chats for non admin users. **I do think that it would be an improvement to display a warning to the admin in the interface settings if the models set are private.** ### Actual Behavior The current behavior for task (title generation, tag generation etc) is that if the admin set the model to a model that is not accessible to this user (because private or not in the appropriate permission) then no titles will be generated. Even worse: if the admin does NOT set a title generation model, the chats will be named by the start of the first user message (which is ugly but usable), but if we set a private model all chats will be named "New Chat" (which makes it impossible to find anything) ### Steps to Reproduce 1. Set the title generation llm to a private model 2. Create chats as a non admin 3. Notice the private model is never called 4. Notice that the admin has no way to know this happened ### Logs & Screenshots Irrelevant ### Additional Information - It is entirely not obvious that "private" also means that they will not be doing interface related tasks, I thought that it only was about actual chats. - Furthermore, this happens silently (no debug nor warning in the logs for the admin that - This is particularly annoying because the admin can go months without knowing that the chat title of the non admin user is broken unless a user tells them. - Even more important now that models are private by default While I do think that it should not be the case because generating those tasks is not something the the user has access over (it just happens without his intervention), I read in another issue that you deem it expected behavior so I wont argue with that.
GiteaMirror added the bug label 2026-05-05 17:40:04 -05:00
GiteaMirror commented 2026-05-05 17:40:07 -05:00
Author
Owner
Copy Link

@Simi5599 commented on GitHub (May 5, 2025):

Can relate, also an option to only generate the title for non-admin users would be needed

<!-- gh-comment-id:2850953510 --> @Simi5599 commented on GitHub (May 5, 2025): Can relate, also an option to only generate the title for non-admin users would be needed
GiteaMirror commented 2026-05-05 17:40:07 -05:00
Author
Owner
Copy Link

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

Addressed with de69c08a1d in dev!

<!-- gh-comment-id:2869084594 --> @tjbck commented on GitHub (May 10, 2025): Addressed with de69c08a1d0556f6d98477c57c8d9df204d391d1 in dev!
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#55582
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?