feat: Default Disable All Provider Models in External Links Configuration Instead of Enabling All #6679

New Issue

GiteaMirror · 2025-11-11T17:03:07-06:00

GiteaMirror commented

2025-11-11 17:03:07 -06:00

Originally created by @cksdxz1007 on GitHub (Oct 15, 2025).

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Currently, in the admin settings panel under "External Links," when users initially add a model provider's API URL and key (such as OpenRouter, OpenAI, etc.), the system automatically retrieves all available models from that provider and sets all models to enabled status by default. This results in an overwhelming number of irrelevant models appearing in the model selection dropdown in the chat interface (e.g., OpenRouter provides over 300 models), severely impacting user experience and interface cleanliness.

Desired Solution you'd like

This feature request aims to modify this behavior: After initially adding an external provider, all models should be disabled by default, allowing users to manually enable specific models according to their actual needs.

After Adding External Providers:

The system retrieves all available model lists from the provider.
All models are set to disabled status by default (i.e., enabled: false).

Model Management:

Users can view all synchronized models in Admin Settings → Model Management.
Users manually check the models they wish to enable (e.g., only enable gpt-4, claude-3-sonnet, etc.).
Only enabled models appear in the model selection dropdown in the chat interface.

Batch Operation Support (Optional Enhancement):

Provide features like "Select All," "Deselect All," or search/filter by name to facilitate quick management of large numbers of models.

Alternatives Considered

No response

Additional Context

No response

Originally created by @cksdxz1007 on GitHub (Oct 15, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Currently, in the admin settings panel under "External Links," when users initially add a model provider's API URL and key (such as OpenRouter, OpenAI, etc.), the system automatically retrieves all available models from that provider and sets all models to **enabled status** by default. This results in an overwhelming number of irrelevant models appearing in the model selection dropdown in the chat interface (e.g., OpenRouter provides over 300 models), severely impacting user experience and interface cleanliness. ### Desired Solution you'd like This feature request aims to modify this behavior: **After initially adding an external provider, all models should be disabled by default**, allowing users to manually enable specific models according to their actual needs. 1. **After Adding External Providers**: - The system retrieves all available model lists from the provider. - **All models are set to disabled status by default** (i.e., `enabled: false`). 2. **Model Management**: - Users can view all synchronized models in Admin Settings → Model Management. - Users manually check the models they wish to enable (e.g., only enable `gpt-4`, `claude-3-sonnet`, etc.). - Only enabled models appear in the model selection dropdown in the chat interface. 3. **Batch Operation Support** (Optional Enhancement): - Provide features like "Select All," "Deselect All," or search/filter by name to facilitate quick management of large numbers of models. ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror closed this issue

2025-11-11 17:03:08 -06:00

GiteaMirror commented

2025-11-11 17:03:09 -06:00

@Classic298 commented on GitHub (Oct 15, 2025):

PLEASE check for duplicate issues and discussions. This has been raised a dozen times before.

The recommended solution to your problem is to manually add the models you would want to enable anyways

E.g.:

Add new connection
Still within the add new connection modal, there is an input field that allows you to allowlist certain models from the API. All model IDs you enter there (and add with the plus button) will be added.
All model IDs that match the allowlisted model IDs will be fetched from the API and all others won't.
Save the connection
Observe

You will see that only the models you want are in the model list now and all others you don't want are not there.

Achieves the same thing as you propose with disabling all by default, except it's even better because all other models you don't even want are not retrieved and therefore not shown to you. Less cluttered UI and less data usage in the database for storing model information of models you don't even want to use.

@Classic298 commented on GitHub (Oct 15, 2025): PLEASE check for duplicate issues and discussions. This has been raised a dozen times before. The recommended solution to your problem is to manually add the models you would want to enable anyways E.g.: 1. Add new connection 2. Still within the add new connection modal, there is an input field that allows you to allowlist certain models from the API. All model IDs you enter there (and add with the plus button) will be added. 3. All model IDs that match the allowlisted model IDs will be fetched from the API and all others won't. 4. Save the connection 5. Observe You will see that only the models you want are in the model list now and all others you don't want are not there. Achieves the same thing as you propose with disabling all by default, except it's even better because all other models you don't even want are not retrieved and therefore not shown to you. Less cluttered UI and less data usage in the database for storing model information of models you don't even want to use.

GiteaMirror referenced this issue

2026-04-19 20:47:59 -05:00

[GH-ISSUE #6679] Support Multiple API Endpoints for Title and Tag Generatio #14443

GiteaMirror referenced this issue

2026-04-25 04:19:20 -05:00

[GH-ISSUE #6679] Support Multiple API Endpoints for Title and Tag Generatio #29971

GiteaMirror referenced this issue

2026-05-05 14:19:54 -05:00

[GH-ISSUE #6679] Support Multiple API Endpoints for Title and Tag Generatio #53109

Sign in to join this conversation.