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 #3176] Update context window management to avoid context shifts #48467

New Issue
Open
opened 2026-04-28 08:32:28 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-28 08:32:28 -05:00
Owner
Copy Link

Originally created by @jmorganca on GitHub (Mar 16, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3176

What are you trying to do?

Today, upon reaching the context window limit, a "context shift" occurs, effectively halving the number of tokens in the context window to make room for new generations. However, we should avoid this – OpenAI and other tools instead have token limits that, when reached, stop generation and let the user know.

How should we solve this?

A few ideas:

  • Make sure at least x% of the prompt is available for generation beyond the prompt
  • Add a reason or similar key to /api/generate and /api/chat so it's obvious when the token limit is hit

What is the impact of not solving this?

Possible run-ons and poorer responses from context shifting

Anything else?

No response

Originally created by @jmorganca on GitHub (Mar 16, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3176 ### What are you trying to do? Today, upon reaching the context window limit, a "context shift" occurs, effectively halving the number of tokens in the context window to make room for new generations. However, we should avoid this – OpenAI and other tools instead have token limits that, when reached, stop generation and let the user know. ### How should we solve this? A few ideas: * Make sure at least x% of the prompt is available for generation beyond the prompt * Add a `reason` or similar key to `/api/generate` and `/api/chat` so it's obvious when the token limit is hit ### What is the impact of not solving this? Possible run-ons and poorer responses from context shifting ### Anything else? _No response_
GiteaMirror added the feature request label 2026-04-28 08:32:28 -05:00
GiteaMirror commented 2026-04-28 08:32:58 -05:00
Author
Owner
Copy Link

@bdqfork commented on GitHub (Jan 7, 2025):

Any update?

<!-- gh-comment-id:2574280091 --> @bdqfork commented on GitHub (Jan 7, 2025): Any update?
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#48467
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?