Currently /v1/models returns a flat list. When connecting to Hermes Agent (or any backend with many models), the model selector dropdown becomes a long flat list with 40+ entries — hard to navigate.
Models like hermes/deepseek/deepseek-v4-pro, hermes/ollama/qwen3-coder:480b are naturally hierarchical (provider/model) but Open WebUI renders them as a single flat dropdown.
Proposed Solution
Parse / separators in model IDs to create grouped/nested dropdown:
Could show as sections in the dropdown with provider headers.
Use Case
Hermes Agent exposes 47 models across 4 providers. Users need to quickly switch between models from different providers. A flat list is unusable at this scale.
References
Hermes Agent model router: auto-discovers providers from API keys, exposes hermes/{provider}/{model} format
Related: /v1/models already returns owned_by field which could be used for grouping
Originally created by @bogerman1 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24238
## Problem
Currently `/v1/models` returns a flat list. When connecting to Hermes Agent (or any backend with many models), the model selector dropdown becomes a long flat list with 40+ entries — hard to navigate.
Models like `hermes/deepseek/deepseek-v4-pro`, `hermes/ollama/qwen3-coder:480b` are naturally hierarchical (`provider/model`) but Open WebUI renders them as a single flat dropdown.
## Proposed Solution
Parse `/` separators in model IDs to create grouped/nested dropdown:
```
┌──────────────────────────────┐
│ hermes/ │
│ ├── deepseek/ │
│ │ └── deepseek-v4-pro │
│ ├── minimax/ │
│ │ ├── MiniMax-M2.5 │
│ │ └── MiniMax-M2.7 │
│ └── ollama/ │
│ ├── deepseek-v4-pro │
│ ├── glm-5 │
│ └── ... │
│ OpenAI/ │
│ └── gpt-4.1 │
└──────────────────────────────┘
```
Or alternatively, group models by `owned_by` field from `/v1/models` response:
```json
{ "id": "hermes/deepseek/deepseek-v4-pro", "owned_by": "deepseek", ... }
```
Could show as sections in the dropdown with provider headers.
## Use Case
Hermes Agent exposes 47 models across 4 providers. Users need to quickly switch between models from different providers. A flat list is unusable at this scale.
## References
- Hermes Agent model router: auto-discovers providers from API keys, exposes `hermes/{provider}/{model}` format
- Related: `/v1/models` already returns `owned_by` field which could be used for grouping
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 @bogerman1 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24238
Problem
Currently
/v1/modelsreturns a flat list. When connecting to Hermes Agent (or any backend with many models), the model selector dropdown becomes a long flat list with 40+ entries — hard to navigate.Models like
hermes/deepseek/deepseek-v4-pro,hermes/ollama/qwen3-coder:480bare naturally hierarchical (provider/model) but Open WebUI renders them as a single flat dropdown.Proposed Solution
Parse
/separators in model IDs to create grouped/nested dropdown:Or alternatively, group models by
owned_byfield from/v1/modelsresponse:Could show as sections in the dropdown with provider headers.
Use Case
Hermes Agent exposes 47 models across 4 providers. Users need to quickly switch between models from different providers. A flat list is unusable at this scale.
References
hermes/{provider}/{model}format/v1/modelsalready returnsowned_byfield which could be used for grouping@Classic298 commented on GitHub (Apr 29, 2026):
You can use provider prefixes for that