You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature request proposes enhancing the chat model selector by allowing users to:
Customize Model Display Names: Define user-friendly "tags" or aliases for model names, replacing the default, often technical, API model names in the selector.
Reorder Model List: Rearrange the order of models in the selector, enabling users to prioritize and group models according to their preferences.
Problem:
Currently, the chat model selector displays model names directly as they are defined by the API (e.g., deepseek-r1, gemini-2.0-flash-thinking-exp). These names can be:
Unclear and not user-friendly: Difficult to quickly understand or differentiate, especially for users unfamiliar with specific model naming conventions.
Inflexible for user organization: Users may have multiple configurations for the same underlying model (e.g., free vs. paid API access) and need a way to distinguish them clearly in the selector.
Lack of Customization: Users cannot organize the model list to reflect their workflow or frequently used models.
Proposed Solution:
Implement a mechanism to allow users to customize the display names of models and reorder them within the chat model selector.
Customizable Model Display Names (Tags):
Introduce a field (e.g., "Display Name" or "Tag") within the settings or configuration for each model.
Users can input a custom name in this field. This custom name will be displayed in the chat model selector instead of the default API model name.
Example: Instead of seeing gemini-2.0-flash-thinking-exp, a user could set the display name to Free(Gemini)2.0 Flash - Thinking.
2. Reorderable Model List:
Provide a drag-and-drop interface or up/down arrow controls within the settings to allow users to reorder the models in the list.
The order in the settings should directly reflect the order in which models appear in the chat model selector.
Example Use Case: A user could group their Gemini models by access type (Free/Paid) and then by model version, as shown below:
Free(Gemini)2.0 Flash - Thinking
Free(Gemini)2.0 Pro - Experimental
Free(Gemini)1.5 Pro
Free(Gemini)1.5 Flash
Paid(Gemini)1.5 Pro
Paid(Gemini)1.5 Flash
(Direct API) Deepseek-r1
OpenRouter Deepseek-r1
Together-Deepseek-r1
Benefits:
Improved User Experience: Makes the model selection process more intuitive and user-friendly.
Enhanced Organization: Allows users to categorize and group models based on their needs (e.g., by provider, cost, or specific use case).
Increased Clarity: Reduces confusion when using multiple configurations of the same model or when model names are technical or cryptic.
Workflow Optimization: Enables users to prioritize frequently used models by placing them at the top of the list.
UI Suggestion:
A "TAG" or "Display Name" field could be added within the model configuration settings. For reordering, a simple drag-and-drop interface in the settings panel would be ideal.
This feature would significantly improve the usability and customization of the chat model selector, making it more efficient and tailored to individual user workflows.
The text was updated successfully, but these errors were encountered:
Summary:
This feature request proposes enhancing the chat model selector by allowing users to:
Customize Model Display Names: Define user-friendly "tags" or aliases for model names, replacing the default, often technical, API model names in the selector.
Reorder Model List: Rearrange the order of models in the selector, enabling users to prioritize and group models according to their preferences.
Problem:
Currently, the chat model selector displays model names directly as they are defined by the API (e.g., deepseek-r1, gemini-2.0-flash-thinking-exp). These names can be:
Unclear and not user-friendly: Difficult to quickly understand or differentiate, especially for users unfamiliar with specific model naming conventions.
Inflexible for user organization: Users may have multiple configurations for the same underlying model (e.g., free vs. paid API access) and need a way to distinguish them clearly in the selector.
Lack of Customization: Users cannot organize the model list to reflect their workflow or frequently used models.
Proposed Solution:
Implement a mechanism to allow users to customize the display names of models and reorder them within the chat model selector.
Introduce a field (e.g., "Display Name" or "Tag") within the settings or configuration for each model.
Users can input a custom name in this field. This custom name will be displayed in the chat model selector instead of the default API model name.
Example: Instead of seeing gemini-2.0-flash-thinking-exp, a user could set the display name to Free(Gemini)2.0 Flash - Thinking.
2. Reorderable Model List:
Provide a drag-and-drop interface or up/down arrow controls within the settings to allow users to reorder the models in the list.
The order in the settings should directly reflect the order in which models appear in the chat model selector.
Example Use Case: A user could group their Gemini models by access type (Free/Paid) and then by model version, as shown below:
Free(Gemini)2.0 Flash - Thinking
Free(Gemini)2.0 Pro - Experimental
Free(Gemini)1.5 Pro
Free(Gemini)1.5 Flash
Paid(Gemini)1.5 Pro
Paid(Gemini)1.5 Flash
(Direct API) Deepseek-r1
OpenRouter Deepseek-r1
Together-Deepseek-r1
Benefits:
Improved User Experience: Makes the model selection process more intuitive and user-friendly.
Enhanced Organization: Allows users to categorize and group models based on their needs (e.g., by provider, cost, or specific use case).
Increased Clarity: Reduces confusion when using multiple configurations of the same model or when model names are technical or cryptic.
Workflow Optimization: Enables users to prioritize frequently used models by placing them at the top of the list.
UI Suggestion:
A "TAG" or "Display Name" field could be added within the model configuration settings. For reordering, a simple drag-and-drop interface in the settings panel would be ideal.
This feature would significantly improve the usability and customization of the chat model selector, making it more efficient and tailored to individual user workflows.
The text was updated successfully, but these errors were encountered: