[GH-ISSUE #19252] feat: Add Prefix Name configuration option to connections. #138550

New Issue

GiteaMirror · 2026-05-25T10:45:53-05:00

GiteaMirror commented

2026-05-25 10:45:53 -05:00

Originally created by @MicahZoltu on GitHub (Nov 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19252

Check Existing Issues

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

I have multiple connections that each provide a large number of models. There is a large overlap of models provided by various providers. When I am looking for a model either in the Admin Panel models list or in the New Chat models list, I often see the same model listed listed multiple times and it can be difficult and in some cases impossible to differentiate them.

Desired Solution you'd like

Similar to the Prefix ID configuration option available in the connections configuration page, I would like to see a Prefix Name configuration option. Setting this would add the provided prefix to the model name field so everywhere in the UI the model appears, it would include the prefix.

For formatting, I am partial to {prefix_name}: {original_name} or {prefix_name} - {original_name} (note the spaces to make it more readable).

Alternatives Considered

Tags: Tags do not appear directly in the model list in the latest version of the UI, so they do not help me quickly identify which model I want to select. The categorization also doesn't help when I know what model I want to use but I do not know which providers have it available (common for new models).

Prefix IDs: These only appear on mouse-over, and are not used during model searches. They also do not appear at all in the Admin Panel, where there is currently no way to differentiate two similarly named models from different providers.

Additional Context

This question has come up numerous times in Discord and issues here where people think the Prefix ID should do what I'm describing and are surprised to find that it doesn't, or only does so in some specific circumstances (like when the connection doesn't provide a name field). Each time they are told that the system is working as intended, even though it does not serve their actual needs and this can lead to user frustration.

I believe this is an easy change because it would basically just involve copying the Prefix ID code and changing id to name. I may be wrong on this assumption though.

One challenge to consider is that if a connection provides IDs and not names, then the Prefix ID is already going to be part of the model name due to the model name being derived from the ID. An ideal solution would be that If both a Prefix Name and Prefix ID are provided, then the final model name will be {prefix_name}: {original_id}, and not {prefix_name}: {prefix_id}:{original_id}

Originally created by @MicahZoltu on GitHub (Nov 18, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19252 ### 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 I have multiple connections that each provide a large number of models. There is a large overlap of models provided by various providers. When I am looking for a model either in the Admin Panel models list or in the New Chat models list, I often see the same model listed listed multiple times and it can be difficult and in some cases impossible to differentiate them. ### Desired Solution you'd like Similar to the Prefix ID configuration option available in the connections configuration page, I would like to see a **Prefix Name** configuration option. Setting this would add the provided prefix to the model name field so everywhere in the UI the model appears, it would include the prefix. For formatting, I am partial to `{prefix_name}: {original_name}` or `{prefix_name} - {original_name}` (note the spaces to make it more readable). ### Alternatives Considered Tags: Tags do not appear directly in the model list in the latest version of the UI, so they do not help me quickly identify which model I want to select. The categorization also doesn't help when I know what model I want to use but I do not know which providers have it available (common for new models). Prefix IDs: These only appear on mouse-over, and are not used during model searches. They also do not appear at all in the Admin Panel, where there is currently no way to differentiate two similarly named models from different providers. ### Additional Context This question has come up numerous times in Discord and issues here where people think the Prefix ID should do what I'm describing and are surprised to find that it doesn't, or only does so in some specific circumstances (like when the connection doesn't provide a `name` field). Each time they are told that the system is working as intended, even though it does not serve their actual needs and this can lead to user frustration. I believe this is an easy change because it would basically just involve copying the Prefix ID code and changing `id` to `name`. I may be wrong on this assumption though. One challenge to consider is that if a connection provides IDs and not names, then the Prefix ID is already going to be part of the model name due to the model name being derived from the ID. An ideal solution would be that If both a Prefix Name and Prefix ID are provided, then the final model name will be `{prefix_name}: {original_id}`, and not `{prefix_name}: {prefix_id}:{original_id}`

GiteaMirror closed this issue

2026-05-25 10:45:54 -05:00

GiteaMirror commented

2026-05-25 10:45:57 -05:00

@MicahZoltu commented on GitHub (Nov 18, 2025):

@tjbck It would be really helpful if you could provide some clarity on why this is an undesirable feature. Multiple users have requested it in various forms, and the issues keep getting closed with links to unrelated issues, or they get closed with no comment like this. It seems like a slam dunk request because it should be trivial to implement (all of the infrastructure already exists for Prefix ID), users want it, and it doesn't cause any change in behavior to anyone who doesn't use the feature.

At least a little insight into why this particular feature seems to be greatly disliked by the project maintainers would go a long way to making users filing bugs/feature requests feel heard at least and not driven away.

@MicahZoltu commented on GitHub (Nov 18, 2025): @tjbck It would be really helpful if you could provide some clarity on why this is an undesirable feature. Multiple users have requested it in various forms, and the issues keep getting closed with links to unrelated issues, or they get closed with no comment like this. It seems like a slam dunk request because it should be trivial to implement (all of the infrastructure already exists for Prefix ID), users want it, and it doesn't cause any change in behavior to anyone who doesn't use the feature. At least a little insight into why this particular feature seems to be greatly disliked by the project maintainers would go a long way to making users filing bugs/feature requests feel heard at least and not driven away.

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#138550