Ability to comment or rename model configurations #1376

Closed
opened 2026-02-21 17:32:57 -05:00 by yindo · 0 comments
Owner

Originally created by @soulteary on GitHub (Mar 15, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

In my usage scenario and that of some friends, we have multiple model providers and interfaces to configure, and some models come from the same provider, such as Azure, which allows the deployment of many models.

I want to use Dify as the application development platform and API Gateway. Currently, Dify's settings do not include tags for model names or comments. When there are too many models, it is not easy to distinguish the models.

2. Describe the feature you'd like to see

The model configuration interface adds comments to the model, which helps distinguish different model resources from the same supplier.

3. How will this feature improve your workflow or experience?

When using and maintaining applications, you can clearly choose the model backend. When replacing, you can clearly see which applications rely on this model.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @soulteary on GitHub (Mar 15, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? In my usage scenario and that of some friends, we have multiple model providers and interfaces to configure, and some models come from the same provider, such as Azure, which allows the deployment of many models. I want to use Dify as the application development platform and API Gateway. Currently, Dify's settings do not include tags for model names or comments. When there are too many models, it is not easy to distinguish the models. ### 2. Describe the feature you'd like to see The model configuration interface adds comments to the model, which helps distinguish different model resources from the same supplier. ### 3. How will this feature improve your workflow or experience? When using and maintaining applications, you can clearly choose the model backend. When replacing, you can clearly see which applications rely on this model. ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:32:57 -05:00
yindo closed this issue 2026-02-21 17:32:57 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#1376