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 #9229] add token counting api call #6016

New Issue
Closed
opened 2026-04-12 17:21:36 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 17:21:36 -05:00
Owner
Copy Link

Originally created by @trebor on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9229

in general, the context window size is super important. however i often feel like i am working blind as it is hard to identify the actual prompt size to see if it fits in context. as far as i can tell, the only way to know a prompt's token count, is to send it off and inspect prompt_eval_count in the result. this is very slow, and if the prompt exceeds the context window, the context window value is returned.

i'd love to be able to query for the token size of my prompt. with that, i could:

  • automatically adjust the context window to fit the prompt.
  • warn in a UI when a prompt exceeds the maximum context, especially if we could know what the maximum context is - see #9228.
Originally created by @trebor on GitHub (Feb 19, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9229 in general, the context window size is **super important**. however i often feel like i am working blind as it is hard to identify the actual prompt size to see if it fits in context. as far as i can tell, the only way to know a prompt's token count, is to send it off and inspect **prompt_eval_count** in the result. this is very slow, and if the prompt exceeds the context window, the context window value is returned. i'd love to be able to query for the token size of my prompt. with that, i could: - automatically adjust the context window to fit the prompt. - warn in a UI when a prompt exceeds the maximum context, especially if we could know what the maximum context is - see #9228.
GiteaMirror added the feature request label 2026-04-12 17:21:36 -05:00
GiteaMirror commented 2026-04-12 17:21:37 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Feb 19, 2025):

https://github.com/ollama/ollama/issues/3582

<!-- gh-comment-id:2669713121 --> @rick-github commented on GitHub (Feb 19, 2025): https://github.com/ollama/ollama/issues/3582
GiteaMirror commented 2026-04-12 17:21:38 -05:00
Author
Owner
Copy Link

@trebor commented on GitHub (Feb 25, 2025):

tis a dup.

<!-- gh-comment-id:2683485200 --> @trebor commented on GitHub (Feb 25, 2025): tis a dup.
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#6016
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?