github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #10153] Models listed aren't in order #32421

New Issue
Closed
opened 2026-04-22 13:41:02 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 13:41:02 -05:00
Owner
Copy Link

Originally created by @iplayfast on GitHub (Apr 6, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10153

What is the issue?

https://ollama.com/search?o=newest should be showing the newest models, but scannng down the list it shows them in newish order instead.

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @iplayfast on GitHub (Apr 6, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10153 ### What is the issue? https://ollama.com/search?o=newest should be showing the newest models, but scannng down the list it shows them in newish order instead. ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bugollama.com labels 2026-04-22 13:41:02 -05:00
GiteaMirror commented 2026-04-22 13:41:05 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 7, 2025):

Models are listed in the order added. If the model is later updated. it changes the "Updated" value but not the ordering.

<!-- gh-comment-id:2782940832 --> @rick-github commented on GitHub (Apr 7, 2025): Models are listed in the order added. If the model is later updated. it changes the "Updated" value but not the ordering.
GiteaMirror commented 2026-04-22 13:41:06 -05:00
Author
Owner
Copy Link

@Qualzz commented on GitHub (Apr 7, 2025):

#4596

I opened an issue about this same thing a few months ago. The "Newest" sort should use the updated_at field instead of created_at — or at least there should be an option to sort by "Recently Updated."

Right now, it’s not intuitive to have to scroll — sometimes a long way — to find a model that was updated just two days ago, hidden among releases from two months ago, especially when the user has selected "Newest" as the sort.

<!-- gh-comment-id:2784076135 --> @Qualzz commented on GitHub (Apr 7, 2025): [#4596](https://github.com/ollama/ollama/issues/4596) I opened an issue about this same thing a few months ago. The "Newest" sort should use the updated_at field instead of created_at — or at least there should be an option to sort by "Recently Updated." Right now, it’s not intuitive to have to scroll — sometimes a long way — to find a model that was updated just two days ago, hidden among releases from two months ago, especially when the user has selected "Newest" as the sort.
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 bug ollama.com
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#32421
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?