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

[GH-ISSUE #11409] Add force num_ctx option #69590

New Issue
Open
opened 2026-05-04 18:35:33 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-04 18:35:33 -05:00
Owner
Copy Link

Originally created by @xhejtman on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11409

Hello,

would it be possible to add an env option so that num_ctx from the request is ignored and always set to the value of OLLAMA_CONTEXT_LENGTH?

The rationale behind this is that for a shared Ollama instance, it's unfortunate if users cause a runner restart by setting an incorrect num_ctx value (even one smaller than the current value).

Originally created by @xhejtman on GitHub (Jul 14, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11409 Hello, would it be possible to add an env option so that `num_ctx` from the request is ignored and always set to the value of `OLLAMA_CONTEXT_LENGTH`? The rationale behind this is that for a shared Ollama instance, it's unfortunate if users cause a runner restart by setting an incorrect `num_ctx` value (even one smaller than the current value).
GiteaMirror added the feature request label 2026-05-04 18:35:33 -05:00
GiteaMirror commented 2026-05-04 18:35:36 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jul 14, 2025):

As a work-around, you could have the clients use the OpenAI API endpoint, or use a proxy to remove num_ctx from the request.

<!-- gh-comment-id:3069466741 --> @rick-github commented on GitHub (Jul 14, 2025): As a work-around, you could have the clients use the OpenAI API [endpoint](https://github.com/ollama/ollama/blob/main/docs/openai.md), or use a [proxy](https://github.com/ollama/ollama/issues/11002#issuecomment-2959740647) to remove `num_ctx` from the request.
GiteaMirror commented 2026-05-04 18:35:37 -05:00
Author
Owner
Copy Link

@xhejtman commented on GitHub (Jul 14, 2025):

As a work-around, you could have the clients use the OpenAI API endpoint, or use a proxy to remove num_ctx from the request.

indeed, I patched ollama sources to ignore num_ctx, but it would be nice, if supported directly by ollama.

openai is not always desired, as some tools such as Continue from VS Code do not work correctly via openai API while via ollama api they do.

<!-- gh-comment-id:3069510862 --> @xhejtman commented on GitHub (Jul 14, 2025): > As a work-around, you could have the clients use the OpenAI API [endpoint](https://github.com/ollama/ollama/blob/main/docs/openai.md), or use a [proxy](https://github.com/ollama/ollama/issues/11002#issuecomment-2959740647) to remove `num_ctx` from the request. indeed, I patched ollama sources to ignore `num_ctx`, but it would be nice, if supported directly by ollama. openai is not always desired, as some tools such as `Continue` from `VS Code` do not work correctly via openai API while via ollama api they do.
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#69590
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?