mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 19:38:46 -05:00
[GH-ISSUE #3030] Regenerating first message duplicates chat #51769
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 @mr-gepardas on GitHub (Jun 11, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3030
Bug Report
Description
Bug Summary:
When regenerating first Assistant response, or editing User first message, the chat gets duplicated.
Steps to Reproduce:
Select any model, write first message, wait for Assistant to respond. Click regenerate button. Or Click edit on the first user message, 'send' message.
Expected Behavior:
The new response is generated, still in the same chat. Would see the new number for the messages 2/2
Actual Behavior:
The new response is generated, in a new chat. The old chat is unaffected, the new chat is a duplicate with messages showing 2/2. The name of the chat is sometimes the same or different, but if tags were applied to the original chat, this new chat will not have any tags applied.
Environment
Open WebUI Version:
v0.3.2
Ollama (if applicable):
0.1.42
Operating System:
Windows 11
Browser (if applicable):
Chrome
Reproduction Details
Confirmation:
Logs and Screenshots
AbortController
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):

Installation Method
Docker WebUI + Local Ollama
Additional Information
The bug keeps happening each time you regenerate the first Assistant or User message, so can quickly end up with a lot of duplicates of the same chat.
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@silentoplayz commented on GitHub (Jun 11, 2024):
This should be fixed on the dev branch. Keep us updated here if you try out the dev branch and let us know if the problem is solved. Otherwise, v0.3.3 should have this fixed when it is released.