[GH-ISSUE #22781] issue: Thread Sidebar in Channel Remains Open After Message Deletion

Originally created by @silentoplayz on GitHub (Mar 18, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22781 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) v0.18.0 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit) ### 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 The thread sidebar should automatically close or provide a visual indication that the parent message has been deleted, preventing further interaction with an orphaned thread. ### Actual Behavior In any channel type (Channel, Group Channel, Direct Message), if a message is sent and a reply is started in a thread sidebar, deleting the original message does not close the thread sidebar. The thread sidebar remains open and fully interactable after the parent message is deleted, allowing further messages to be sent in an orphan thread that becomes inaccessible once the sidebar is closed. ### Steps to Reproduce 1. Open any channel (Public Channel, Group Channel, or Direct Message). 2. Send a new message (e.g., "Test"). 3. Hover over the message and click the **Reply in Thread** button to open the thread sidebar on the right. 4. While the thread sidebar is open, delete the original message in the main channel. 5. Observe that the thread sidebar remains visible and you can still type and send messages into it. 6. Close the thread sidebar. 7. Observe that there is no longer any way to access the messages sent in that thread, as the parent message is gone. ### Logs & Screenshots **Step 3:** Hover over the message and click the **Reply in Thread** button. <img width="2557" height="1274" alt="Clicking Reply in Thread" src="https://github.com/user-attachments/assets/2acdffd1-5721-4a65-9069-ab7525e4e502" /> **Step 5:** While the thread sidebar is open, delete the original message. Observe that the thread sidebar remains visible. <img width="2557" height="1274" alt="Thread sidebar remains open after parent deletion" src="https://github.com/user-attachments/assets/4eeb32f7-117d-45bb-8f9c-10b74cc269a3" /> **Step 5 (continued):** Observe that you can still send messages in the thread sidebar. <img width="2557" height="1274" alt="Orphaned thread reply" src="https://github.com/user-attachments/assets/cd183fce-4acb-45ad-8245-ef6b4ab3beea" /> ### Additional Information This issue affects all conversation types where threads are enabled.

GiteaMirror commented

2026-05-05 23:15:41 -05:00

Owner

Originally created by @silentoplayz on GitHub (Mar 18, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22781

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

v0.18.0

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit)

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

The thread sidebar should automatically close or provide a visual indication that the parent message has been deleted, preventing further interaction with an orphaned thread.

Actual Behavior

In any channel type (Channel, Group Channel, Direct Message), if a message is sent and a reply is started in a thread sidebar, deleting the original message does not close the thread sidebar. The thread sidebar remains open and fully interactable after the parent message is deleted, allowing further messages to be sent in an orphan thread that becomes inaccessible once the sidebar is closed.

Steps to Reproduce

Open any channel (Public Channel, Group Channel, or Direct Message).
Send a new message (e.g., "Test").
Hover over the message and click the Reply in Thread button to open the thread sidebar on the right.
While the thread sidebar is open, delete the original message in the main channel.
Observe that the thread sidebar remains visible and you can still type and send messages into it.
Close the thread sidebar.
Observe that there is no longer any way to access the messages sent in that thread, as the parent message is gone.