[GH-ISSUE #16624] issue: Model's default context window in Admin Panel/Settings/Models/Advanced Params is not used. #56645

Closed
opened 2026-05-05 19:52:38 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @mario-grgic on GitHub (Aug 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16624

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

0.6.22

Ollama Version (if applicable)

0.11.4 git-837379a9

Operating System

macOS 15.6 (24G84)

Browser (if applicable)

Brave 1.81.135 (Official Build) (arm64)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

I changed the model's default context window size in Admin settings, and I expected these settings to be used in chats with the model. However, default value of 2048 is always show in the UI instead the Admin set model's context window size.

Actual Behavior

open-webui does not respect Admin set context window size for the model and the chat UI controls always show default num_ctx value of 2048, completely ignoring admin setting.

Steps to Reproduce

I am using macOS and have python3.11 installed. I created virtual environment and installed open-webui in it. (pip install -U open-webui)

I start open-webui with open-webui serve.

I am also building ollama from source and running it with ollama serve.

If I open http://localhost:8080/ with Brave browser and log in with my account.

I typically use gemma3:27b which has 8192 context window size. However, open-webui chat controls always default to 2048 context window size.

So I wanted to change the model's default context size to something bigger. I opened Admin Panel, navigated to Settings, then Models. I edited the gemma3:27b model and in "Advanced Params" modified the num_ctx (ollama) value to 8192. I saved the model.

I started the new chat with gemma3:27b model. I expanded the chat controls and scrolled down to inspect the num_ctx (ollama) parameter's value, and it is set to Default. Clicking on Default indeed shows 2028 value.

Logs & Screenshots

localhost-1755182616439.log

open-webui.log

https://github.com/user-attachments/assets/a9094b84-9012-42a8-bc58-d2ece5e2fb48

Additional Information

No response

Originally created by @mario-grgic on GitHub (Aug 14, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16624 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Pip Install ### Open WebUI Version 0.6.22 ### Ollama Version (if applicable) 0.11.4 git-837379a9 ### Operating System macOS 15.6 (24G84) ### Browser (if applicable) Brave 1.81.135 (Official Build) (arm64) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior I changed the model's default context window size in Admin settings, and I expected these settings to be used in chats with the model. However, default value of 2048 is always show in the UI instead the Admin set model's context window size. ### Actual Behavior open-webui does not respect Admin set context window size for the model and the chat UI controls always show default num_ctx value of 2048, completely ignoring admin setting. ### Steps to Reproduce I am using macOS and have python3.11 installed. I created virtual environment and installed open-webui in it. (`pip install -U open-webui`) I start open-webui with `open-webui serve`. I am also building ollama from source and running it with `ollama serve`. If I open http://localhost:8080/ with Brave browser and log in with my account. I typically use `gemma3:27b` which has 8192 context window size. However, open-webui chat controls always default to 2048 context window size. So I wanted to change the model's default context size to something bigger. I opened Admin Panel, navigated to Settings, then Models. I edited the gemma3:27b model and in "Advanced Params" modified the `num_ctx (ollama)` value to 8192. I saved the model. I started the new chat with gemma3:27b model. I expanded the chat controls and scrolled down to inspect the `num_ctx (ollama)` parameter's value, and it is set to `Default`. Clicking on `Default` indeed shows 2028 value. ### Logs & Screenshots [localhost-1755182616439.log](https://github.com/user-attachments/files/21775253/localhost-1755182616439.log) [open-webui.log](https://github.com/user-attachments/files/21775256/open-webui.log) https://github.com/user-attachments/assets/a9094b84-9012-42a8-bc58-d2ece5e2fb48 ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-05 19:52:38 -05:00
Author
Owner

@mario-grgic commented on GitHub (Aug 14, 2025):

It seems that even customizing the chat configuration and increasing the num_ctx value has no effect either and this is definitely a regression.

<!-- gh-comment-id:3189358308 --> @mario-grgic commented on GitHub (Aug 14, 2025): It seems that even customizing the chat configuration and increasing the `num_ctx` value has no effect either and this is definitely a regression.
Author
Owner

@rgaricano commented on GitHub (Aug 14, 2025):

That it's just a confussion in interpretation (that was treated in other issues)

When Advanced Params are in Default it mean that it doesn't change the defaults ones (the ones from previous layers),
yes, when click on its appears a value, but this isn't the active value, it's just a default value for the var.

& yes, it could be a good idea that it will reflect the active value.

<!-- gh-comment-id:3189417875 --> @rgaricano commented on GitHub (Aug 14, 2025): That it's just a confussion in interpretation (that was treated in other issues) When Advanced Params are in Default it mean that it doesn't change the defaults ones (the ones from previous layers), yes, when click on its appears a value, but this isn't the active value, it's just a default value for the var. & yes, it could be a good idea that it will reflect the active value.
Author
Owner

@tjbck commented on GitHub (Aug 14, 2025):

Exactly what @rgaricano said, this is working as intended.

<!-- gh-comment-id:3189738359 --> @tjbck commented on GitHub (Aug 14, 2025): Exactly what @rgaricano said, this is working as intended.
Author
Owner

@neuhaus commented on GitHub (Jan 26, 2026):

That it's just a confussion in interpretation (that was treated in other issues)

When Advanced Params are in Default it mean that it doesn't change the defaults ones (the ones from previous layers), yes, when click on its appears a value, but this isn't the active value, it's just a default value for the var.

& yes, it could be a good idea that it will reflect the active value.

The culprit is the line
https://github.com/open-webui/open-webui/blob/2b26355002064228e9b671339f8f3fb9d1fafa73/src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte#L1361

<!-- gh-comment-id:3799960498 --> @neuhaus commented on GitHub (Jan 26, 2026): > That it's just a confussion in interpretation (that was treated in other issues) > > When Advanced Params are in Default it mean that it doesn't change the defaults ones (the ones from previous layers), yes, when click on its appears a value, but this isn't the active value, it's just a default value for the var. > > & yes, it could be a good idea that it will reflect the active value. The culprit is the line https://github.com/open-webui/open-webui/blob/2b26355002064228e9b671339f8f3fb9d1fafa73/src/lib/components/chat/Settings/Advanced/AdvancedParams.svelte#L1361
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#56645