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

[GH-ISSUE #14964] Add capabilities field to /api/tags response #71682

New Issue
Open
opened 2026-05-05 02:20:04 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 02:20:04 -05:00
Owner
Copy Link

Originally created by @serbangeorge-m on GitHub (Mar 19, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14964

Problem

The /api/tags endpoint lists all local models but does not include any capability information (chat, embedding, vision,
etc.). Clients building model selectors for chat need to know which models support chat/completion vs embedding-only.

Currently, the only way to get this information is by calling /api/show for each model individually, which results in
N+1 API calls just to filter a model list.

This was originally requested in #3117. The capabilities field was added to /api/show, which is great, but it was not
added to /api/tags.

Proposed Solution

Include the capabilities array in each model object returned by /api/tags:

{
"models": [
{
"name": "llama3:latest",
"modified_at": "...",
"size": 123456,
"digest": "...",
"details": { ... },
"capabilities": ["completion", "tools"]
},
{
"name": "nomic-embed-text:latest",
"modified_at": "...",
"size": 123456,
"digest": "...",
"details": { ... },
"capabilities": ["embedding"]
}
]
}

Use Case

Desktop applications and web UIs that integrate with Ollama need to show only chat-capable models in their chat model
selector. Without this field on /api/tags, clients must make an extra /api/show call per model to determine
capabilities, which is inefficient and unnecessary since the data already exists.

Originally created by @serbangeorge-m on GitHub (Mar 19, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14964 Problem The /api/tags endpoint lists all local models but does not include any capability information (chat, embedding, vision, etc.). Clients building model selectors for chat need to know which models support chat/completion vs embedding-only. Currently, the only way to get this information is by calling /api/show for each model individually, which results in N+1 API calls just to filter a model list. This was originally requested in #3117. The capabilities field was added to /api/show, which is great, but it was not added to /api/tags. Proposed Solution Include the capabilities array in each model object returned by /api/tags: { "models": [ { "name": "llama3:latest", "modified_at": "...", "size": 123456, "digest": "...", "details": { ... }, "capabilities": ["completion", "tools"] }, { "name": "nomic-embed-text:latest", "modified_at": "...", "size": 123456, "digest": "...", "details": { ... }, "capabilities": ["embedding"] } ] } Use Case Desktop applications and web UIs that integrate with Ollama need to show only chat-capable models in their chat model selector. Without this field on /api/tags, clients must make an extra /api/show call per model to determine capabilities, which is inefficient and unnecessary since the data already exists.
GiteaMirror added the feature request label 2026-05-05 02:20:04 -05:00
GiteaMirror commented 2026-05-05 02:20:32 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Mar 19, 2026):

https://github.com/ollama/ollama/pull/10174

<!-- gh-comment-id:4093451630 --> @rick-github commented on GitHub (Mar 19, 2026): https://github.com/ollama/ollama/pull/10174
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 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#71682
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?