github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[Feature Request]: Batch Enable/Disable Models #4242

New Issue
Closed
opened 2025-11-11 15:49:26 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 15:49:26 -06:00
Owner
Copy Link
Copy Source

Originally created by @FedeCuci on GitHub (Mar 4, 2025).

Problem Description

Summary:
The current model selection process in OpenWebUI becomes inefficient when a large number of models are available, as it involves scanning through long lists with similarly named models, leading to time-consuming searches. Adding a "Disable All" toggle in "Settings > Models" would allow users to quickly clear the model list and enable only the models they intend to use.

Motivation:

  • Users with access to many models (e.g., users who use OpenRouter which currently offers 250+ models) find it time-consuming to search through an extensive list when selecting a model.
  • Frequently, models have similar names, making it difficult to find the specific model by searching, forcing the user to scroll through model search menu.
  • Disabling hundreds of models individually in Settings > Models is time-consuming and impractical

Desired Solution you'd like

Implement a "Disable All" toggle switch in the "Settings > Models" section (see image). This disables/enables all models at once. Currently, each model must be enabled/disabled individually. This is impractical with hundreds of models. Following the "Disable All" action, users can then enable individual models as needed.

Once only a few models are enabled, it would be possible to add a keybind to quickly change through the models. For example, Ctrl+Shift+Left/Right Arrow keys.

Additional Context

Image

Originally created by @FedeCuci on GitHub (Mar 4, 2025). ### Problem Description Summary: The current model selection process in OpenWebUI becomes inefficient when a large number of models are available, as it involves scanning through long lists with similarly named models, leading to time-consuming searches. Adding a "Disable All" toggle in "Settings > Models" would allow users to quickly clear the model list and enable only the models they intend to use. Motivation: - Users with access to many models (e.g., users who use OpenRouter which currently offers 250+ models) find it time-consuming to search through an extensive list when selecting a model. - Frequently, models have similar names, making it difficult to find the specific model by searching, forcing the user to scroll through model search menu. - Disabling hundreds of models individually in Settings > Models is time-consuming and impractical ### Desired Solution you'd like Implement a "Disable All" toggle switch in the "Settings > Models" section (see image). This disables/enables all models at once. Currently, each model must be enabled/disabled individually. This is impractical with hundreds of models. Following the "Disable All" action, users can then enable individual models as needed. Once only a few models are enabled, it would be possible to add a keybind to quickly change through the models. For example, Ctrl+Shift+Left/Right Arrow keys. ### Additional Context ![Image](https://github.com/user-attachments/assets/1980324f-7ee5-4094-a7f1-76ddd125c8be)
GiteaMirror commented 2025-11-11 15:49:27 -06:00
Author
Owner
Copy Link
Copy Source

@harrywang commented on GitHub (Mar 8, 2025):

Yes.

@harrywang commented on GitHub (Mar 8, 2025): Yes.
GiteaMirror commented 2025-11-11 15:49:28 -06:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Mar 28, 2025):

We're still trying to understand why this is wanted or would be a preferred way to disable models when you can whitelist models from connections directly. Could you elaborate more on use cases where this is clearly superior?

@tjbck commented on GitHub (Mar 28, 2025): We're still trying to understand why this is wanted or would be a preferred way to disable models when you can whitelist models from connections directly. Could you elaborate more on use cases where this is clearly superior?
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4242