[GH-ISSUE #11977] feat: Model Alias System or Tag/Filter Functionality #16423

New Issue

GiteaMirror · 2026-04-19T22:21:03-05:00

GiteaMirror commented

2026-04-19 22:21:03 -05:00

Originally created by @lucian-nightwalker on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11977

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

When running 12+ Ollama models (e.g., hermes3:8b-q4_k_m, hf.co/ChaoticNeutrals/Eris-13B-GGUF:Q4_K_M) for roleplay, writing, theory, troubleshooting, and worldbuilding; the Open WebUI model dropdown feels raw and cluttered. There’s no easy way to identify or prioritize models by use case (e.g., “RP Ace” vs. “Theory Star”) without creating custom modelfiles, which takes extra steps and storage. Hiding models declutters but doesn’t solve the core issue—lack of personalization or filtering.

Tie into LiteLLM and you make the list even more cluttered.

Desired Solution you'd like

I'd propose one or both of the following as a solution:

Alias System:
An “Alias” field in Workspace > Models to rename models in the UI (e.g., Eris-13B → “Eris (RP Ace)”) without altering the base model. You can then toggle to display aliases in the dropdown, keep original names in logs.

Tag/Filter System:
Tag models with custom labels (e.g., “Roleplay,” “Scientific”) then add a filter dropdown or search to show only tagged models.

Example: Tag nous-hermes-13b as “Creative,” alias Eris-13B as “RP Ace,” filter to “Creative” for writing sessions or toggle aliases on.

Benefits: Streamlines model management, cuts reliance on workarounds, boosts usability for multi-model users—all UI-side, no backend overhaul.

Alternatives Considered

You can obviously create custom model files and name them whatever you want. But, this still isn't a very viable solution because you have to either remember (which, if you have a goldfish memory like me is difficult) what model is best for your intended use case before creating the custom model file, or, spend 20 minutes googling or asking Grok which model on your list is your best starting point.

Originally created by @lucian-nightwalker on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/11977 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description When running 12+ Ollama models (e.g., hermes3:8b-q4_k_m, hf.co/ChaoticNeutrals/Eris-13B-GGUF:Q4_K_M) for roleplay, writing, theory, troubleshooting, and worldbuilding; the Open WebUI model dropdown feels raw and cluttered. There’s no easy way to identify or prioritize models by use case (e.g., “RP Ace” vs. “Theory Star”) without creating custom modelfiles, which takes extra steps and storage. Hiding models declutters but doesn’t solve the core issue—lack of personalization or filtering. Tie into LiteLLM and you make the list even more cluttered. ### Desired Solution you'd like I'd propose one or both of the following as a solution: Alias System: An “Alias” field in Workspace > Models to rename models in the UI (e.g., Eris-13B → “Eris (RP Ace)”) without altering the base model. You can then toggle to display aliases in the dropdown, keep original names in logs. Tag/Filter System: Tag models with custom labels (e.g., “Roleplay,” “Scientific”) then add a filter dropdown or search to show only tagged models. Example: Tag nous-hermes-13b as “Creative,” alias Eris-13B as “RP Ace,” filter to “Creative” for writing sessions or toggle aliases on. Benefits: Streamlines model management, cuts reliance on workarounds, boosts usability for multi-model users—all UI-side, no backend overhaul. ### Alternatives Considered You can obviously create custom model files and name them whatever you want. But, this still isn't a very viable solution because you have to either remember (which, if you have a goldfish memory like me is difficult) what model is best for your intended use case before creating the custom model file, or, spend 20 minutes googling or asking Grok which model on your list is your best starting point.

GiteaMirror closed this issue

2026-04-19 22:21:04 -05:00

GiteaMirror commented

2026-04-19 22:21:06 -05:00

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

You can literally tag your models.

@tjbck commented on GitHub (Mar 23, 2025): You can literally tag your models.

GiteaMirror commented

2026-04-19 22:21:08 -05:00

@gaby commented on GitHub (Jan 21, 2026):

@tjbck what about the aliases. Ran into this issue while trying to implement that.

Some models use very complex names, and providing user friendly names as an alias would be beneficial.

@gaby commented on GitHub (Jan 21, 2026): @tjbck what about the aliases. Ran into this issue while trying to implement that. Some models use very complex names, and providing user friendly names as an alias would be beneficial.

GiteaMirror referenced this issue

2026-04-20 05:15:03 -05:00

[PR #16423] enh: Functions/Tools & Valves additional gimmicks #24126

GiteaMirror referenced this issue

2026-04-25 12:13:08 -05:00

[PR #16423] enh: Functions/Tools & Valves additional gimmicks #39756

GiteaMirror referenced this issue

2026-04-29 22:16:40 -05:00

[PR #16423] enh: Functions/Tools & Valves additional gimmicks #47174

GiteaMirror referenced this issue

2026-05-06 07:28:18 -05:00

[PR #16423] enh: Functions/Tools & Valves additional gimmicks #62982