I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
Currently, in the Workspaces section, the dropdown menu used to select a "Base Model" is a standard, static list. For users with a large number of local or API-based models, this becomes highly inefficient.
The list requires manual scrolling to find specific models, which creates a friction point in the workflow—especially when contrasted with the much more polished and efficient "Model Picker" used in the main New Chat interface.
Desired Solution you'd like
I would like the Workspace Base Model selection to use the same searchable, categorized UI component found in the New Chat model picker.
Key benefits:
Searchability: Users can type to filter models instantly.
Consistency: Provides a unified UX across different parts of the Open WebUI interface.
Scalability: Better handles environments with dozens or hundreds of available models.
Alternatives Considered
Keeping the current dropdown: This remains difficult to use as the model library grows, especially on mobile
Adding a simple search bar to the existing dropdown: While better, it would be more efficient to reuse the existing high-quality component already built for the main chat interface.
Additional Context
Reusing the ModelPicker component (or the logic behind it) from the chat interface would streamline navigation for power users who manage many models within Workspaces.
Note: If this is considered a larger task than a "quick coding session," I am happy to move this to the Discussions/Ideas section
Originally created by @toonvank on GitHub (May 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24576
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
Currently, in the Workspaces section, the dropdown menu used to select a "Base Model" is a standard, static list. For users with a large number of local or API-based models, this becomes highly inefficient.
The list requires manual scrolling to find specific models, which creates a friction point in the workflow—especially when contrasted with the much more polished and efficient "Model Picker" used in the main New Chat interface.
### Desired Solution you'd like
I would like the Workspace Base Model selection to use the same searchable, categorized UI component found in the New Chat model picker.
Key benefits:
- Searchability: Users can type to filter models instantly.
- Consistency: Provides a unified UX across different parts of the Open WebUI interface.
- Scalability: Better handles environments with dozens or hundreds of available models.
### Alternatives Considered
- Keeping the current dropdown: This remains difficult to use as the model library grows, especially on mobile
- Adding a simple search bar to the existing dropdown: While better, it would be more efficient to reuse the existing high-quality component already built for the main chat interface.
### Additional Context
Reusing the ModelPicker component (or the logic behind it) from the chat interface would streamline navigation for power users who manage many models within Workspaces.
Note: If this is considered a larger task than a "quick coding session," I am happy to move this to the Discussions/Ideas section
@owui-terminator[bot] commented on GitHub (May 11, 2026):
🔍Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣#21501feat: Workspace “Select a base model” dropdown becomes unusable with OpenRouter or multiple providers (duplicate formats, no provider context, huge unsorted list) Directly related: it reports the Workspace “Select a base model” dropdown becoming unusable with many models and explicitly suggests replacing the plain select with a searchable combobox. This overlaps strongly with your request to use the unified searchable model picker UI. by spencerthayer
🟣#18719feat: UI Limitations Prevent Model Selection During Workspace Creation Directly related: it asks to use the same model selection menu as New Chat for Workspace creation because the current Base Model picker is hard to use and not searchable. This is essentially the same UX request for Workspaces. by juliosene
🟣#19033feat: Same search and hover for true model name for LLM Selection for Models in Workspace Related: it describes the Workspace model selection dropdown lacking the search/hover features available in the main model picker, especially when many duplicate model names exist. While narrower, it supports the same unified-picker direction. by Wladastic
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4420512433 -->
@owui-terminator[bot] commented on GitHub (May 11, 2026):
<!-- terminator-bot:related-issues-reply -->
🔍 **Related Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. 🟣 [#21501](https://github.com/open-webui/open-webui/issues/21501) **feat: Workspace “Select a base model” dropdown becomes unusable with OpenRouter or multiple providers (duplicate formats, no provider context, huge unsorted list)**
*Directly related: it reports the Workspace “Select a base model” dropdown becoming unusable with many models and explicitly suggests replacing the plain select with a searchable combobox. This overlaps strongly with your request to use the unified searchable model picker UI.*
*by spencerthayer*
2. 🟣 [#18719](https://github.com/open-webui/open-webui/issues/18719) **feat: UI Limitations Prevent Model Selection During Workspace Creation**
*Directly related: it asks to use the same model selection menu as New Chat for Workspace creation because the current Base Model picker is hard to use and not searchable. This is essentially the same UX request for Workspaces.*
*by juliosene*
3. 🟣 [#19033](https://github.com/open-webui/open-webui/issues/19033) **feat: Same search and hover for true model name for LLM Selection for Models in Workspace**
*Related: it describes the Workspace model selection dropdown lacking the search/hover features available in the main model picker, especially when many duplicate model names exist. While narrower, it supports the same unified-picker direction.*
*by Wladastic*
---
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @toonvank on GitHub (May 11, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24576
Check Existing Issues
Verify Feature Scope
Problem Description
Currently, in the Workspaces section, the dropdown menu used to select a "Base Model" is a standard, static list. For users with a large number of local or API-based models, this becomes highly inefficient.
The list requires manual scrolling to find specific models, which creates a friction point in the workflow—especially when contrasted with the much more polished and efficient "Model Picker" used in the main New Chat interface.
Desired Solution you'd like
I would like the Workspace Base Model selection to use the same searchable, categorized UI component found in the New Chat model picker.
Key benefits:
Searchability: Users can type to filter models instantly.
Consistency: Provides a unified UX across different parts of the Open WebUI interface.
Scalability: Better handles environments with dozens or hundreds of available models.
Alternatives Considered
Additional Context
Reusing the ModelPicker component (or the logic behind it) from the chat interface would streamline navigation for power users who manage many models within Workspaces.
Note: If this is considered a larger task than a "quick coding session," I am happy to move this to the Discussions/Ideas section
@owui-terminator[bot] commented on GitHub (May 11, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #21501 feat: Workspace “Select a base model” dropdown becomes unusable with OpenRouter or multiple providers (duplicate formats, no provider context, huge unsorted list)
Directly related: it reports the Workspace “Select a base model” dropdown becoming unusable with many models and explicitly suggests replacing the plain select with a searchable combobox. This overlaps strongly with your request to use the unified searchable model picker UI.
by spencerthayer
🟣 #18719 feat: UI Limitations Prevent Model Selection During Workspace Creation
Directly related: it asks to use the same model selection menu as New Chat for Workspace creation because the current Base Model picker is hard to use and not searchable. This is essentially the same UX request for Workspaces.
by juliosene
🟣 #19033 feat: Same search and hover for true model name for LLM Selection for Models in Workspace
Related: it describes the Workspace model selection dropdown lacking the search/hover features available in the main model picker, especially when many duplicate model names exist. While narrower, it supports the same unified-picker direction.
by Wladastic
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.