Skip to content

[FEATURE]:clean model list on /models /connect #18393

Closed as not planned
Closed as not planned

Description

@framefutura

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

it will be great, if i can manually disconnect the model companies form /connect, and remove the models that i don't need from /models, right now, /models shows all the model from connected model company, and i don't use all the models, it become a very long list, i want to remove some of not using models

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Mar 20, 2026
  2. github-actions commented on Mar 20, 2026

    @github-actions
    Contributor

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

    Please review these issues and consider adding a 👍 reaction or commenting there if they cover your use case.

  3. framefutura commented on Mar 20, 2026

    @framefutura
    Author

    tried to add the disable_providers and disable models lists on opencode.json, but /model still show those provides and models, the code line didn't work.

  4. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    webRelates to opencode on web / desktop
    on May 3, 2026
  5. YoungJurry commented on May 14, 2026

    @YoungJurry

    I ran into a very concrete version of this problem with the built-in Gemini/Google provider.

    After connecting a valid GOOGLE_API_KEY, OpenCode still shows many models in /models that are either:

    • not actually available to the current API key/account,
    • not intended for normal chat/coding use,
    • or simply not models I want to keep in the picker.

    The current workaround is to:

    1. disable the built-in gemini provider,
    2. create a custom provider,
    3. manually re-list only the allowed models.

    That workaround is functional, but it has two downsides:

    • it is much more cumbersome than /connect,
    • and it loses the benefits of built-in provider metadata unless everything is re-declared manually (for example model capability/limit metadata).

    A very helpful improvement would be:

    • after /connect succeeds, allow the user to optionally customize the model list for that connected provider,
    • ideally as an allowlist / "keep these models" step,
    • and persist that selection so hidden models do not appear in /models or model pickers.

    This would solve the common "connected provider but noisy/unusable model list" problem without forcing users into custom provider config just to hide models.

    In other words: /connect should support a user-curated model list for built-in providers.

  6. github-actions commented on Jul 14, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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