[GH-ISSUE #14067] Ability to hide or archive models from the UI selection menu #34949

Open
opened 2026-04-22 18:59:31 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @elajep on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14067

Is your feature request related to a problem? Please describe. Currently, the model selection dropdown becomes cluttered as more models are pulled. There is no native way to "hide" specific models from the interface without fully deleting them. This is especially cumbersome for:

Models used only for specific API tasks.

Experimental models that I don't want to see in my daily chat rotation.

(Optional) Models that appear in the library but aren't locally downloaded yet.

Describe the solution you'd like I would like a way to toggle the visibility of models in the UI.

Visibility Toggle: A setting (either in the config or a simple 'eye' icon in the model list) to hide a model from the main selection menu.

Archiving: An "Archive" state where the model remains on disk but is moved to a "Hidden/Archived" section of the dropdown.

Filter for Downloaded Only: An option to hide models that are available in the registry but not yet present on the local machine.

Describe alternatives you've considered The only current workaround is deleting the model using ollama rm, but this is inefficient if I need to use the model occasionally for testing or via API without it cluttering my primary chat interface.

Additional context Adding a hidden: true flag in the model metadata or a simple exclusion list in the UI settings would greatly improve the user experience for those managing large libraries.

Originally created by @elajep on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14067 Is your feature request related to a problem? Please describe. Currently, the model selection dropdown becomes cluttered as more models are pulled. There is no native way to "hide" specific models from the interface without fully deleting them. This is especially cumbersome for: Models used only for specific API tasks. Experimental models that I don't want to see in my daily chat rotation. (Optional) Models that appear in the library but aren't locally downloaded yet. Describe the solution you'd like I would like a way to toggle the visibility of models in the UI. Visibility Toggle: A setting (either in the config or a simple 'eye' icon in the model list) to hide a model from the main selection menu. Archiving: An "Archive" state where the model remains on disk but is moved to a "Hidden/Archived" section of the dropdown. Filter for Downloaded Only: An option to hide models that are available in the registry but not yet present on the local machine. Describe alternatives you've considered The only current workaround is deleting the model using ollama rm, but this is inefficient if I need to use the model occasionally for testing or via API without it cluttering my primary chat interface. Additional context Adding a hidden: true flag in the model metadata or a simple exclusion list in the UI settings would greatly improve the user experience for those managing large libraries.
GiteaMirror added the appfeature request labels 2026-04-22 18:59:32 -05:00
Author
Owner

@jgmio commented on GitHub (Mar 25, 2026):

Second this feature request.

<!-- gh-comment-id:4124798007 --> @jgmio commented on GitHub (Mar 25, 2026): Second this feature request.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#34949