[GH-ISSUE #13437] feat: Allow creating model "groups" / "families" #120221

New Issue

GiteaMirror · 2026-05-20T21:48:39-05:00

GiteaMirror commented

2026-05-20 21:48:39 -05:00

Originally created by @JRomainG on GitHub (May 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13437

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Recent model releases often come in many "flavors" (e.g. different sizes, MoE / dense, reasoning, etc.). Downloading the various flavors tends to clutter the UI and make the model picker crowded

Desired Solution you'd like

It would be useful for the admin to be able to create model "groups" or "families". The model picker could show these groups by default, and then once the user picks a group, they could choose a specific model in that group (or use the group default)

For example, let's say I downloaded the following models:

I would like to be able to create 2 groups:

Phi
- Phi-4
- Phi-4-mini (default)
- Phi-4-reasoning
- Phi-4-reasoning-plus
- Phi-4-mini-reasoning
Qwen
- Qwen3-30B-A3B
- Qwen3-32B
- Qwen3-14B
- Qwen3-8B (default)
- Qwen2.5-Coder-32B
- Qwen2.5-Coder-14B

Users would then choose for example the Qwen group, and by default they would be discussing with Qwen3-8B. However, they could also switch to Qwen3-32B (for example) within that same family

As a side note, with this new organization, searching could still give results for all models (rather than just high-level groups) so that users who know what they're looking for aren't forced into more clicks

Alternatives Considered

Currently, I use tags for models, which definitely helps navigate the model picker: I can choose models based on the use-case (e.g. code, think, math, etc.)

Still, the first impression is that the model picker is very full, which can make it confusing

Additional Context

No response

Originally created by @JRomainG on GitHub (May 2, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13437 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Recent model releases often come in many "flavors" (e.g. different sizes, MoE / dense, reasoning, etc.). Downloading the various flavors tends to clutter the UI and make the model picker crowded ### Desired Solution you'd like It would be useful for the admin to be able to create model "groups" or "families". The model picker could show these groups by default, and then once the user picks a group, they could choose a specific model in that group (or use the group default) For example, let's say I downloaded the following models: * [Phi-4](https://huggingface.co/microsoft/phi-4) * [Phi-4-mini](https://huggingface.co/microsoft/Phi-4-mini-instruct) * [Phi-4-reasoning](https://huggingface.co/microsoft/Phi-4-reasoning) * [Phi-4-reasoning-plus](https://huggingface.co/microsoft/Phi-4-reasoning-plus) * [Phi-4-mini-reasoning](https://huggingface.co/microsoft/Phi-4-mini-reasoning) * [Qwen3-30B-A3B](https://huggingface.co/Qwen/Qwen3-30B-A3B) * [Qwen3-32B](https://huggingface.co/Qwen/Qwen3-32B) * [Qwen3-14B](https://huggingface.co/Qwen/Qwen3-14B) * [Qwen3-8B](https://huggingface.co/Qwen/Qwen3-8B) * [Qwen2.5-Coder-32B](https://huggingface.co/Qwen/Qwen2.5-Coder-32B-Instruct-GGUF) * [Qwen2.5-Coder-14B](https://huggingface.co/Qwen/Qwen2.5-Coder-14B-Instruct) I would like to be able to create 2 groups: * Phi * Phi-4 * Phi-4-mini **(default)** * Phi-4-reasoning * Phi-4-reasoning-plus * Phi-4-mini-reasoning * Qwen * Qwen3-30B-A3B * Qwen3-32B * Qwen3-14B * Qwen3-8B **(default)** * Qwen2.5-Coder-32B * Qwen2.5-Coder-14B Users would then choose for example the Qwen group, and by default they would be discussing with Qwen3-8B. However, they could also switch to Qwen3-32B (for example) within that same family As a side note, with this new organization, searching could still give results for all models (rather than just high-level groups) so that users who know what they're looking for aren't forced into more clicks ### Alternatives Considered Currently, I use tags for models, which definitely helps navigate the model picker: I can choose models based on the use-case (e.g. code, think, math, etc.) Still, the first impression is that the model picker is very full, which can make it confusing ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-20 21:48:39 -05:00

GiteaMirror commented

2026-05-20 21:48:41 -05:00

@tjbck commented on GitHub (May 3, 2025):

You should be able to use model tags for this.

@tjbck commented on GitHub (May 3, 2025): You should be able to use model tags for this.

GiteaMirror commented

2026-05-20 21:48:41 -05:00

@ckuethe commented on GitHub (May 4, 2025):

I was just about to make the same request, for the same reasons.

"reasoning" for the various thinking models, "coder" for code optimized models, "python" for models optimized for python programming, etc.

@ckuethe commented on GitHub (May 4, 2025): I was just about to make the same request, for the same reasons. "reasoning" for the various thinking models, "coder" for code optimized models, "python" for models optimized for python programming, etc.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#120221