github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-23 22:21:55 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #11743] [Feature Request] Add separate "Models" sidebar tab in Ollama GUI for installed & available models #69838

New Issue
Open
opened 2026-05-04 19:32:17 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-04 19:32:17 -05:00
Owner
Copy Link

Originally created by @muhammad-fiaz on GitHub (Aug 6, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11743

Originally assigned to: @hoyyeva on GitHub.

Currently, the only way to view or switch between models in the Ollama Chat UI is via a dropdown at the bottom. This mixes both installed and uninstalled models, leading to confusion and accidental downloads.

Image

🧠 Suggestions

Add a dedicated "Models" sidebar tab in the GUI with:

  1. ✅ Installed Models Section

    • List of all downloaded models
    • Model details: size, date downloaded, GPU/CPU usage stats, etc.
    • "Delete" or "Install" button for each

  2. 🌐 Available Models Section

    • Full list of models from Ollama registry
    • Install buttons, size info, and descriptions
    • Search/filter by model type, size, creator

  3. 🔄 Optional Features

    • Auto-update toggle for specific models
    • Download progress tracking
    • Sorting by recently used, size, etc.

🎯 Why This Matters

  • Improves user clarity by separating what’s installed vs. what’s available
  • Prevents accidental large downloads from dropdown misclicks
  • Adds full control over local models, helping with disk space and memory planning

📌 UI Suggestion (Sidebar)

🧠 Chats
📥 Models   ← NEW
⚙️ Settings
Originally created by @muhammad-fiaz on GitHub (Aug 6, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11743 Originally assigned to: @hoyyeva on GitHub. Currently, the only way to view or switch between models in the Ollama Chat UI is via a dropdown at the bottom. This mixes both installed and uninstalled models, leading to confusion and accidental downloads. <img width="1120" height="616" alt="Image" src="https://github.com/user-attachments/assets/7524d488-df89-4ad9-b273-78332761a714" /> ### 🧠 Suggestions Add a **dedicated "Models" sidebar tab** in the GUI with: 1. ✅ **Installed Models Section** * List of all downloaded models * Model details: size, date downloaded, GPU/CPU usage stats, etc. * "Delete" or "Install" button for each 2. 🌐 **Available Models Section** * Full list of models from Ollama registry * Install buttons, size info, and descriptions * Search/filter by model type, size, creator 3. 🔄 **Optional Features** * Auto-update toggle for specific models * Download progress tracking * Sorting by recently used, size, etc. --- ## 🎯 Why This Matters - Improves user clarity by separating what’s installed vs. what’s available - Prevents accidental large downloads from dropdown misclicks - Adds full control over local models, helping with disk space and memory planning --- ## 📌 UI Suggestion (Sidebar) ```plaintext 🧠 Chats 📥 Models ← NEW ⚙️ Settings ```
GiteaMirror added the appfeature request labels 2026-05-04 19:32:17 -05:00
GiteaMirror commented 2026-05-04 19:32:19 -05:00
Author
Owner
Copy Link

@PatrickDotStar commented on GitHub (Aug 6, 2025):

The first version of the GUI had dedicated icon next to each model name indicating whether it needed to be downloaded but is now missing in the latest release. Could be bug.

Image
<!-- gh-comment-id:3161004047 --> @PatrickDotStar commented on GitHub (Aug 6, 2025): The first version of the GUI had dedicated icon next to each model name indicating whether it needed to be downloaded but is now missing in the latest release. Could be bug. <img width="400" alt="Image" src="https://github.com/user-attachments/assets/1345d6b8-33cf-45a6-b934-217ea1471574" />
GiteaMirror commented 2026-05-04 19:32:19 -05:00
Author
Owner
Copy Link

@muhammad-fiaz commented on GitHub (Aug 6, 2025):

The first version of the GUI had dedicated icon next to each model name indicating whether it needed to be downloaded but now seems to have been removed in the latest release. Could be bug.

Image

Yeah But on Version 0.11.2 its gone completely but anyway it is still kind of not user-friendly when switching installed models, even accidentally selecting not download other models thats why it needs new sidebar tab :)

<!-- gh-comment-id:3161014045 --> @muhammad-fiaz commented on GitHub (Aug 6, 2025): > The first version of the GUI had dedicated icon next to each model name indicating whether it needed to be downloaded but now seems to have been removed in the latest release. Could be bug. > > <img width="400" alt="Image" src="https://github.com/user-attachments/assets/1345d6b8-33cf-45a6-b934-217ea1471574" /> Yeah But on Version 0.11.2 its gone completely but anyway it is still kind of not user-friendly when switching installed models, even accidentally selecting not download other models thats why it needs new sidebar tab :)
GiteaMirror commented 2026-05-04 19:32:20 -05:00
Author
Owner
Copy Link

@danieltomasz commented on GitHub (Aug 6, 2025):

It could be a toggle in settings : do not show not installed models, by default also proposed models to install might be shown for user installing it first time

<!-- gh-comment-id:3161246487 --> @danieltomasz commented on GitHub (Aug 6, 2025): It could be a toggle in settings : do not show not installed models, by default also proposed models to install might be shown for user installing it first time
GiteaMirror commented 2026-05-04 19:32:21 -05:00
Author
Owner
Copy Link

@brnt commented on GitHub (Aug 21, 2025):

I suspect that inadvertently invoking an unexpected (and un-downloaded) model might be one of the most frequent user errors in the current version of the app. Here's a list of ideas for improvements, escalating from trivial changes to major enhancements:

  1. Have the app remember the last model used on subsequent sessions. This appears to have been added (thanks!) ✅
  2. Sort the list of models with the downloaded models first and put a visual indicator (simple border line or de-emphasizing color for menu options) at the transition from downloaded to not downloaded.
  3. Implement a filter system and corresponding settings options. There are many ways to run with this.
<!-- gh-comment-id:3211043721 --> @brnt commented on GitHub (Aug 21, 2025): I suspect that inadvertently invoking an unexpected (and un-downloaded) model might be one of the most frequent user errors in the current version of the app. Here's a list of ideas for improvements, escalating from trivial changes to major enhancements: 1. Have the app **remember the last model used** on subsequent sessions. This appears to have been added (thanks!) ✅ 2. **Sort the list of models** with the downloaded models first and put a visual indicator (simple border line or de-emphasizing color for menu options) at the transition from downloaded to not downloaded. 3. Implement a filter system and corresponding settings options. There are many ways to run with this.
GiteaMirror commented 2026-05-04 19:32:22 -05:00
Author
Owner
Copy Link

@masukomi commented on GitHub (Aug 28, 2025):

Adding a use case to this.

what happened

Switched to a model good for coding stuff, asked some questions. Went to switch back to a different model that was better at other tasks. No idea which one I was using before, and without the icon indicating if they've been downloaded I just have to take a chance. tell it to stop, choose something else, repeat, until I figure out which one I already have.

User story:

As a user I want to be able to know which models I've used recently
so that I can switch back to one that was working well.

So, in addition to all the stuff listed above, I think there's an argument to be made for a list that's ordered by recency of use.

Alternately, and probably space saving, would be to let me hover over one of the chat entries in the sidebar and have a pop-over tell me meta-information about that interaction. Off the top of my head I'm thinking indicating what model, or models, were used in it, and the date, or date range the conversation transpired over. I don't think this negates the need for anything anyone else suggested. It's just a solution to the recently used problem.

<!-- gh-comment-id:3233821639 --> @masukomi commented on GitHub (Aug 28, 2025): Adding a use case to this. ## what happened Switched to a model good for coding stuff, asked some questions. Went to switch back to a different model that was better at other tasks. No idea which one I was using before, and without the icon indicating if they've been downloaded I just have to take a chance. tell it to stop, choose something else, repeat, until I figure out which one I already have. ## User story: As a user I want to be able to know which models I've used recently so that I can switch back to one that was working well. So, in addition to all the stuff listed above, I think there's an argument to be made for a list that's ordered by recency of use. Alternately, and probably space saving, would be to let me hover over one of the chat entries in the sidebar and have a pop-over tell me meta-information about that interaction. Off the top of my head I'm thinking indicating what model, or models, were used in it, and the date, or date range the conversation transpired over. I don't think this negates the need for anything anyone else suggested. It's just a solution to the recently used problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label app feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#69838
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?