Skip to content

[FEATURE]: Allow disabling a provider without removing credentials #53532

New issue
New issue
Open
Open
[FEATURE]: Allow disabling a provider without removing credentials#53532
Assignees
nexxeln

Description

@CristianJ12
CristianJ12
opened on Oct 6, 2026

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I’d like to temporarily disable a provider without disconnecting it or removing its credentials.

V2 already has provider activation states (auto, enabled, disabled), so could disabled represent a provider disabled by the user? The action would preserve accounts, credentials, provider configuration, models, and model visibility preferences while preventing new use of that provider. Re-enabling it should restore its normal activation source instead of forcing enabled.

This should remain separate from provider.use: policy-denied providers must stay blocked and the Settings action should not edit policy rules.

Related issues: #39065 covers credential precedence and an unrecoverable Disconnect flow; #19572, #24832, and #31920 focus on hiding or filtering providers; #39637 covers incomplete provider setup and editing. This request is narrower: a reversible user-disabled state that preserves the existing connection and credentials.

Before implementation, would reusing activation: "disabled" be the intended model? Where should this preference live, how should disabled providers be exposed to Settings, and how should existing sessions that selected one behave?

Activity

  1. github-actions
    assigned
    nexxeln
    on Oct 6, 2026

  2. github-actions commented on Oct 6, 2026

    @github-actions
    github-actionsBot
    on Oct 6, 2026 – with GitHub Actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    • #24832: requests a menu to enable or disable providers instead of manually configuring disabled_providers.
    • #19572: requests disabling built-in providers to hide unused providers and models.
    • #39065: covers Disconnect disabling a provider with no UI way to restore it, overlapping with reversible disabling while preserving credentials.

  3. opencodejr commented on Oct 27, 2026

    @opencodejr
    opencodejrBot
    on Oct 27, 2026
    Contributor

    Thanks for the detailed request! In short: you'd like to temporarily disable a provider from Settings while keeping its connection, credentials, configuration and model preferences. Re-enabling it would bring back its original activation instead of forcing enabled, and this would stay separate from provider.use policy rules.

    Today a provider can only be switched off in two ways. One is Disconnect. The other is disabled_providers / enabled_providers in the config, which are converted into provider.use deny rules. The provider model already has an activation state (auto / enabled / disabled), and disabled providers are already filtered out of the available list. So your proposal fits the existing design, but where the preference is stored, how Settings shows it and how existing sessions behave are decisions for the maintainers. They will consider it.

    Related issues, which you've already linked, for context:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions