github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-25 13:22:59 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

BUG: Merged Responses is deleted when sending follow up requests to multi-model chat #2471

New Issue
Open
opened 2025-11-11 15:08:02 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 15:08:02 -06:00
Owner
Copy Link
Copy Source

Originally created by @guibirow on GitHub (Oct 26, 2024).

Bug Report

Installation Method

I have OpenWebUI installed on docker with remove Ollama running on MacOS

Environment

  • Open WebUI Version: v0.3.34

  • Ollama (if applicable): 0.3.13

  • Operating System: macOS Sonoma

  • Browser (if applicable): Firefox 131

Expected Behavior:

When chatting with multiple models, the answer of each model is output into separate collumns. When we click merge responses, a new response is created below them. When a follow up question is submitted, I would expect the merged response to be used for follow up chats and the merged reponse stays in the message history to track the conversation.

Actual Behavior:

After merging the responses of multiple models, if I submit follow up questions, the merged response is deleted and it seems the message is not used as context to follow up questions

Description

Bug Summary:

If you send a follow up message to a multi-model chat after a merged response is generated, the UI will delete the merged response before proceeding to respond the follow-up questions

Reproduction Details

Steps to Reproduce:

  • Start a new chat and select 2 or more models
  • Submit a request and wait for completion
  • Click merge responses (Icon on bottom right of the answers)
  • Wait for model to complete the response merge
  • Submit a follow up request
  • Merged response is deleted (bug)
  • New responses are generated based on previous model responses
Originally created by @guibirow on GitHub (Oct 26, 2024). # Bug Report ## Installation Method I have OpenWebUI installed on docker with remove Ollama running on MacOS ## Environment - **Open WebUI Version:** v0.3.34 - **Ollama (if applicable):** 0.3.13 - **Operating System:** macOS Sonoma - **Browser (if applicable):** Firefox 131 ## Expected Behavior: When chatting with multiple models, the answer of each model is output into separate collumns. When we click merge responses, a new response is created below them. When a follow up question is submitted, I would expect the merged response to be used for follow up chats and the merged reponse stays in the message history to track the conversation. ## Actual Behavior: After merging the responses of multiple models, if I submit follow up questions, the merged response is deleted and it seems the message is not used as context to follow up questions ## Description **Bug Summary:** If you send a follow up message to a multi-model chat after a merged response is generated, the UI will delete the merged response before proceeding to respond the follow-up questions ## Reproduction Details **Steps to Reproduce:** - Start a new chat and select 2 or more models - Submit a request and wait for completion - Click merge responses (Icon on bottom right of the answers) - Wait for model to complete the response merge - Submit a follow up request - Merged response is deleted (bug) - New responses are generated based on previous model responses
GiteaMirror added the bug label 2025-11-11 15:08:03 -06:00
GiteaMirror commented 2025-11-11 15:08:04 -06:00
Author
Owner
Copy Link
Copy Source

@tjbck commented on GitHub (Oct 26, 2024):

Fixed on dev, 0.3.35 coming right up!

@tjbck commented on GitHub (Oct 26, 2024): Fixed on dev, 0.3.35 coming right up!
GiteaMirror commented 2025-11-11 15:08:04 -06:00
Author
Owner
Copy Link
Copy Source

@silentoplayz commented on GitHub (Jun 16, 2025):

I am re-opening this issue myself because I have searched for existing issues or discussions to see if a similar issue has already been reported and came across this issue. I have this bug sometimes (hit-or-miss during testing) on the latest version of Open WebUI (v0.6.14), but the issue DOES exist and should be examined for reproducibility.

Here's a screen recording that I managed to capture of this bug in action:

https://github.com/user-attachments/assets/ef70378b-f9dc-417c-87bf-c0b82041f245

@silentoplayz commented on GitHub (Jun 16, 2025): I am re-opening this issue myself because I have searched for existing issues or discussions to see if a similar issue has already been reported and came across this issue. I have this bug sometimes (hit-or-miss during testing) on the latest version of Open WebUI (v0.6.14), but the issue **DOES** exist and should be examined for reproducibility. ### Here's a screen recording that I managed to capture of this bug in action: https://github.com/user-attachments/assets/ef70378b-f9dc-417c-87bf-c0b82041f245
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2471