mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #19154] issue: model streaming parameter set to True, even though the setting is set to False #34318
Reference in New Issue
Block a user
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?
Originally created by @DirkRemmers on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19154
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.6.36
Ollama Version (if applicable)
No response
Operating System
Windows 11
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When I set a models
Stream Chat Responseparameter toOffin the Admin Panel, the request to the model should include the'stream': Falsesetting in the request. This works perfectly fine in version 0.6.34.Actual Behavior
In version 0.6.36, this seems to be broken. When I set a models
Stream Chat Responseparameter toOffin the Admin Panel, the request to the model now includes include the'stream': Truesetting in the request.Steps to Reproduce
Stream Chat Responseparameter toOffTest this both in versions 0.6.34 and 0.6.36 to see the difference. I did not test 0.6.35.
Logs & Screenshots
Both requests are made while the
Stream Chat Responseparameter is set toOff:Request contents version 0.6.34:
request = {'stream': False, 'model': 'test-model', 'messages': [{'role': 'user', 'content': 'hi there'}]}
Request contents version 0.6.36:
request = {'stream': True, 'model': 'test-model', 'messages': [{'role': 'user', 'content': 'hi there'}]}
Additional Information
No response
@silentoplayz commented on GitHub (Nov 13, 2025):
I believe this issue is valid, as toggling
Stream Chat ResponsetoOffat the model level for an external GroqCloud model isn't resulting in the model's responses NOT being streamed in chats on my end.Edit: I believe these two screenshots validates the issue existing.

@DirkRemmers commented on GitHub (Nov 13, 2025):
Thanks for visualizing it!
@tjbck commented on GitHub (Nov 17, 2025):
Addressed in dev!
f138be9d8a