Bug Report

Description

Bug Summary:
Response lost if chat is switched during generation

Steps to Reproduce:

1. Ask something in the chat window
2. LLM starts generating the response
3. Switch to another topic by selecting previous chats
4. Return to original topic
5. Realize that you can't see what is going on. CPU is busy, but nothing is being shown in the UI, there is no ⏹️ button, etc. There is no way to abort the generation.
6. Only after LLM finishes generation the whole reply is shown, all at once.

Expected Behavior:
I expect that the generation would happen in the background and I would be able to see the progress when I return to the chat where the question was asked. I should have an option to abort the generation before it finishes.

Actual Behavior:
Reply being generated is invisible, no way to abort.

Environment

• Open WebUI Version: v0.1.123

• Ollama (if applicable): 0.1.39

• Operating System: Ubuntu 22.04

• Browser (if applicable): Firefox 125.0

Reproduction Details

Confirmation:

• I have read and followed all the instructions provided in the README.md.
• I am on the latest version of both Open WebUI and Ollama.
• I have included the browser console logs.
• I have included the Docker container logs.

Logs and Screenshots

Browser Console Logs:
[Include relevant browser console logs, if applicable]

Docker Container Logs:
[Include relevant Docker container logs, if applicable]

Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]

Installation Method

[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]

Additional Information

[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]

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!