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

[GH-ISSUE #5880] bug: Default Model Setting Inconsistencies in Open WebUI #52823

New Issue
Closed
opened 2026-05-05 13:57:45 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-05 13:57:45 -05:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Oct 3, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/5880

Bug Report: Default Model Setting Inconsistencies in Open WebUI

Environment

  • Ollama Version: v0.3.12 (latest)
  • Installation Method: Ollama Windows (preview)

  • Operating System: Windows 11 Pro 24H2, OS build 26120.770, Windows Feature Experience Pack 1000.26100.6.0
  • Browser (if applicable): Firefox v131.0 (64-bit)

Confirmation

  • I have read and followed all the instructions provided in the README.md.
  • I am on the latest version of both Open WebUI and Ollama.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Description

Bug Summary:
Multiple inconsistencies have been discovered in the default model settings across the Open WebUI platform. These issues affect the Set as default functionality, Admin account settings, and Whitelisted model constraints.

Expected Behavior

Issue 1: Inconsistent Default Model Setting

When a user sets a model as the default from the chat page's model drop-down selector, the change is not reflected in their Interface settings for the Default Model option. However, if the default model is set from the Interface settings, the update is correctly reflected in both the chat page and the Interface settings.

Expected Behavior:

  • Setting a model as default from the chat page drop-down selector should update the default model in both the chat page and the Interface settings.

Issue 2: Admin Account Settings Not Overriding User Default Model

Setting the Default Model under the Users tab in an Admin account does not override the user's default model for new chats. Instead, it only updates the user's Interface settings for the Default Model option, requiring the user to manually save the changes.

Expected Behavior:

  • Setting the Default Model under the Users tab in an Admin account should override the user's default model for new chats, without requiring manual user intervention.

Issue 3: Admin Account Model Setting Validation

An Admin account can set the Default Model under the Users tab to a model not present in the list of Whitelisted models. This results in the default model being cleared in the user's Interface settings for the Default Model option.

Expected Behavior:

  • The Admin account should only allow setting the Default Model to a model present in the list of Whitelisted models.
  • A validation mechanism should be implemented to ensure the selected model is Whitelisted before applying the default model setting.

Reproduction Details

Steps to Reproduce:

  1. Set a model as default from the chat page's model drop-down selector.
    • The change should be updated in both the chat page and the Interface settings, but it is not.
  2. Set the default model from the Interface settings.
    • The change is correctly reflected in both the chat page and Interface settings.
  3. As an Admin, set the default model under the Users tab for a user.
    • The setting should override the user's default model for new chats, but it does not.
  4. As an Admin, set the default model under the Users tab to a model not present in the list of Whitelisted models.
    • The Admin account should not allow this, but it does, resulting in the default model being cleared in the user's Interface settings.

Recommendations

To address these issues, the recommend fixes might be introduced:

  • Update the Set as default functionality to correctly reflect the default model in both the chat page and Interface settings.
  • Enhance the Admin account settings to override the user's default model for new chats without manual user intervention.
  • Implement validation mechanisms to restrict the selection of models not present in the list of Whitelisted models.

Note

This bug report aims to provide all necessary information for reproduction and addressing of the issue. If any additional details are required, please let me know.

Originally created by @silentoplayz on GitHub (Oct 3, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/5880 # Bug Report: Default Model Setting Inconsistencies in Open WebUI ### Environment - **Open WebUI Version:** [v0.3.30 (latest)](https://github.com/open-webui/open-webui/releases/tag/v0.3.30) - **Installation Method:** Docker Desktop ## - **Ollama Version:** [v0.3.12 (latest)](https://github.com/ollama/ollama/releases/tag/v0.3.12) - **Installation Method:** Ollama Windows (preview) ## - **Operating System:** Windows 11 Pro 24H2, OS build 26120.770, Windows Feature Experience Pack 1000.26100.6.0 - **Browser (if applicable):** Firefox v131.0 (64-bit) ## ### Confirmation - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. # ### Description **Bug Summary:** Multiple inconsistencies have been discovered in the default model settings across the Open WebUI platform. These issues affect the `Set as default` functionality, Admin account settings, and Whitelisted model constraints. # ### Expected Behavior ### **Issue 1: Inconsistent Default Model Setting** When a user sets a model as the default from the chat page's model drop-down selector, the change is not reflected in their Interface settings for the Default Model option. However, if the default model is set from the Interface settings, the update is correctly reflected in both the chat page and the Interface settings. **Expected Behavior:** - Setting a model as default from the chat page drop-down selector should update the default model in both the chat page and the Interface settings. ### **Issue 2: Admin Account Settings Not Overriding User Default Model** Setting the Default Model under the Users tab in an Admin account does not override the user's default model for new chats. Instead, it only updates the user's Interface settings for the Default Model option, requiring the user to manually save the changes. **Expected Behavior:** - Setting the Default Model under the Users tab in an Admin account should override the user's default model for new chats, without requiring manual user intervention. ### **Issue 3: Admin Account Model Setting Validation** An Admin account can set the Default Model under the Users tab to a model not present in the list of Whitelisted models. This results in the default model being cleared in the user's Interface settings for the Default Model option. **Expected Behavior:** - The Admin account should only allow setting the Default Model to a model present in the list of Whitelisted models. - A validation mechanism should be implemented to ensure the selected model is Whitelisted before applying the default model setting. # ### Reproduction Details **Steps to Reproduce:** 1. Set a model as default from the chat page's model drop-down selector. - The change should be updated in both the chat page and the Interface settings, but it is not. 2. Set the default model from the Interface settings. - The change is correctly reflected in both the chat page and Interface settings. 3. As an Admin, set the default model under the Users tab for a user. - The setting should override the user's default model for new chats, but it does not. 4. As an Admin, set the default model under the Users tab to a model not present in the list of Whitelisted models. - The Admin account should not allow this, but it does, resulting in the default model being cleared in the user's Interface settings. # ### **Recommendations** To address these issues, the recommend fixes might be introduced: - Update the `Set as default` functionality to correctly reflect the default model in both the chat page and Interface settings. - Enhance the Admin account settings to override the user's default model for new chats without manual user intervention. - Implement validation mechanisms to restrict the selection of models not present in the list of Whitelisted models. # ### Note This bug report aims to provide all necessary information for reproduction and addressing of the issue. If any additional details are required, please let me know.
GiteaMirror commented 2026-05-05 13:57:48 -05:00
Author
Owner
Copy Link

@thiswillbeyourgithub commented on GitHub (Oct 3, 2024):

I notice those too and it's an issue for my family setup.

<!-- gh-comment-id:2390604674 --> @thiswillbeyourgithub commented on GitHub (Oct 3, 2024): I notice those too and it's an issue for my family setup.
GiteaMirror commented 2026-05-05 13:57:48 -05:00
Author
Owner
Copy Link

@flefevre commented on GitHub (Oct 8, 2024):

What should be also the behaviour for the 'whitelist models' in the interface settings?
When set, should the models for all users and the admins matched the given list in the model selector in chat? (Preferred behaviour)
Or admin user should have all models accessible in the model selector in chat? ( Actual version)

<!-- gh-comment-id:2398858880 --> @flefevre commented on GitHub (Oct 8, 2024): What should be also the behaviour for the 'whitelist models' in the interface settings? When set, should the models for all users and the admins matched the given list in the model selector in chat? (Preferred behaviour) Or admin user should have all models accessible in the model selector in chat? ( Actual version)
GiteaMirror commented 2026-05-05 13:57:49 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Oct 10, 2024):

What should be also the behaviour for the 'whitelist models' in the interface settings?

When set, should the models for all users and the admins matched the given list in the model selector in chat? (Preferred behaviour)

Or admin user should have all models accessible in the model selector in chat? ( Actual version)

I believe the current functionality of the Admin's ability to whitelist models on a User account level is desired and the preferred behavior.

<!-- gh-comment-id:2404019939 --> @silentoplayz commented on GitHub (Oct 10, 2024): > What should be also the behaviour for the 'whitelist models' in the interface settings? > > When set, should the models for all users and the admins matched the given list in the model selector in chat? (Preferred behaviour) > > Or admin user should have all models accessible in the model selector in chat? ( Actual version) I believe the current functionality of the Admin's ability to whitelist models on a User account level is desired and the preferred behavior.
GiteaMirror commented 2026-05-05 13:57:50 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Nov 20, 2024):

This issue has been closed due to the depreciation of the Set as default option that was once found within the Interface settings menu and the depreciation of the Users tab in the Admin settings menu.

<!-- gh-comment-id:2487371499 --> @silentoplayz commented on GitHub (Nov 20, 2024): This issue has been closed due to the depreciation of the `Set as default` option that was once found within the `Interface` settings menu and the depreciation of the `Users` tab in the Admin settings menu.
GiteaMirror commented 2026-05-05 13:57:51 -05:00
Author
Owner
Copy Link

@neo-pan commented on GitHub (Nov 21, 2024):

Hi there,
I've looked through the documentation but couldn't find any information about this: is there still a way for Admin to change the Default Model for other users through alternative means or interfaces? This functionality is quite important for our team's workflow.
Would appreciate any guidance on this matter.

<!-- gh-comment-id:2490389188 --> @neo-pan commented on GitHub (Nov 21, 2024): Hi there, I've looked through the documentation but couldn't find any information about this: is there still a way for Admin to change the Default Model for other users through alternative means or interfaces? This functionality is quite important for our team's workflow. Would appreciate any guidance on this matter.
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
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#52823
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?