mirror of
https://github.com/open-webui/open-webui.git
synced 2026-06-07 17:28:41 -05:00
enh: reintroduce hide model #2760
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#2760
Reference in New Issue
Block a user
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?
Originally created by @kivvi3412 on GitHub (Nov 22, 2024).
Originally assigned to: @tjbck on GitHub.
I want to hide the GPT-4o-mini option in the dropdown list, but if I directly disable the model from the console, it will prevent using cheaper models for generating titles or performing other tasks
@morgan55555 commented on GitHub (Nov 22, 2024):
You can set visibility in model settings.
Change it to "Private" and do not set any group for it, and it will be visible only for admins.
@kivvi3412 commented on GitHub (Nov 23, 2024):
@morgan55555 I mean, hide this model from Admin (which is myself) as well, but still be able to use this model to generate titles and so on...
@JohnathanCrow commented on GitHub (Dec 3, 2024):
I think this is related: It seems we can no longer hide base models and keep the workspace models functional. Or am I missing something?
@morgan55555 commented on GitHub (Dec 20, 2024):
Seems that workspace models still be functional, but task models currently is not, if it's private.
So, we still need to feature to hide models, or, at least, skip checks (like bypass_filter) if model is TASK_MODEL or TASK_MODEL_EXTERNAL.
@tjbck
@ProjectMoon commented on GitHub (Dec 20, 2024):
I think if the base models are disabled (which is different than hidden), the workspace models no longer work. It's because hiding was changed to enable/disable, and disabling a base model essentially makes it non-existent as far as the workspace is concerned.
@morgan55555 commented on GitHub (Dec 20, 2024):
Seems that its right, disabled models cannot be TASK_MODEL, or be a base model for any of the virtual models.
Maybe, we need an confirmation dialog when disabling models, like "Disabling of this model will invalidate next models: a, b, etc"?
But anyway, if TASK_MODEL is set, users should get access to this models by calling api functions, or at least admin shouldn't receive non-public models in TASK_MODEL's list.
I have a base model without system prompt for tasks and some of models, using this "clean" model as base. And I don't want users to use this clean model, but I should, because it's a model for tasks.
@ProjectMoon commented on GitHub (Dec 20, 2024):
I understand. I want to hide like 90% of my base models because they clutter the list. My instance is basically single-user, but I have a bunch of base models that are derived from actual ollama base models, and then I make workspace models from those. This allows me to update the modelfiles independently of the settings in OpenWebUI (tools, filters, etc).
@df-cgdm commented on GitHub (Dec 26, 2024):
Hello, I would like also disable model visibility in the chat UI but keep it available to be used for other model and/or api.
@FedeCuci commented on GitHub (Mar 4, 2025):
Somewhat related to this, I believe an easy way to hide all models is to disable all them all in "Settings > Models" and only enable those you want to use. For example, you could add a toggle switch to disable all models. Then the user can manually enable the ones they want to see in the drop-down menu. Many people, including me, are using OWUI with OpenRouter, and having to scroll/search through 250+ models each time is time-consuming.
@tjbck commented on GitHub (Mar 31, 2025):
Closing in favour of #12080