github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-22 06:02:06 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

enh: option to disable artifacts automatically opening #2355

New Issue
Closed
opened 2025-11-11 15:05:34 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-11 15:05:34 -06:00
Owner
Copy Link

Originally created by @chrisoutwright on GitHub (Oct 11, 2024).

Bug Report

Bug Summary:
The artifact sidetab opens repeatedly when switching between conversation threads. If one thread has an artifact (e.g., HTML), this causes the artifact tab to show up constantly, even when switching to other threads without artifacts, breaking the overview sidetab functionality and workflow.

Second Problem: Chat Overview will be also constantly suppressed by this behaviour of course!

Installation Method

Manual installation on Windows 10

Environment

  • Open WebUI Version: open-webui-0.3.32

  • Ollama (if applicable): v0.3.12

  • Operating System: Windows 10

  • Browser (if applicable): Chrome Version 129.0.6668.100

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.
  • I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

When switching between conversation threads where only one thread has artifacts (such as HTML to render), the artifacts should display correctly only when selected.

Actual Behavior:

When one conversation thread contains an artifact (HTML), clicking between threads causes the artifact sidetab to constantly open, even when the other thread has no artifacts. This results in continuous sidetab spam, affecting both the artifact overview and breaking the flow when copying information.

Description

Bug Summary:
The artifact sidetab opens repeatedly when switching between conversation threads. If one thread has an artifact (e.g., HTML), this causes the artifact tab to show up constantly (even when closing the sidetab), when switching to other threads without artifacts, breaking the overview sidetab functionality and workflow.

Reproduction Details

Steps to Reproduce:

  1. Open Open WebUI v0.3.32 in Chrome.
  2. Create two conversation threads:
    • One thread contains an artifact (e.g., HTML).
    • The other has no artifact.
  3. Click between the two conversation threads.
  4. Notice that the artifact sidetab continues to open in artifact-less thread regardless if one has closed the sidetab ONCE.

Logs and Screenshots

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

See attached clip!

https://github.com/user-attachments/assets/20a796f2-5be6-4860-87da-4029067ddc4d

Docker Container Logs:
N/A

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

Additional Information

This issue affects the usability of switching between conversation threads and disrupts the workflow, especially when copying data from threads. It appears to be related to how artifacts are handled across multiple threads.

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!

Originally created by @chrisoutwright on GitHub (Oct 11, 2024). # Bug Report **Bug Summary:** The artifact sidetab opens repeatedly when switching between conversation threads. If one thread has an artifact (e.g., HTML), this causes the artifact tab to show up constantly, even when switching to other threads without artifacts, breaking the overview sidetab functionality and workflow. Second Problem: Chat Overview will be also constantly suppressed by this behaviour of course! ## Installation Method Manual installation on Windows 10 ## Environment - **Open WebUI Version:** open-webui-0.3.32 - **Ollama (if applicable):** v0.3.12 - **Operating System:** Windows 10 - **Browser (if applicable):** Chrome Version 129.0.6668.100 **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] 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. - [ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: When switching between conversation threads where only one thread has artifacts (such as HTML to render), the artifacts should display correctly only when selected. ## Actual Behavior: When one conversation thread contains an artifact (HTML), clicking between threads causes the artifact sidetab to constantly open, even when the other thread has no artifacts. This results in continuous sidetab spam, affecting both the artifact overview and breaking the flow when copying information. ## Description **Bug Summary:** The artifact sidetab opens repeatedly when switching between conversation threads. If one thread has an artifact (e.g., HTML), this causes the artifact tab to show up constantly (even when closing the sidetab), when switching to other threads without artifacts, breaking the overview sidetab functionality and workflow. ## Reproduction Details **Steps to Reproduce:** 1. Open Open WebUI v0.3.32 in Chrome. 2. Create two conversation threads: - One thread contains an artifact (e.g., HTML). - The other has no artifact. 3. Click between the two conversation threads. 4. Notice that the artifact sidetab continues to open in artifact-less thread regardless if one has closed the sidetab ONCE. ## Logs and Screenshots **Browser Console Logs:** [Include relevant browser console logs, if applicable] See attached clip! https://github.com/user-attachments/assets/20a796f2-5be6-4860-87da-4029067ddc4d **Docker Container Logs:** N/A **Screenshots/Screen Recordings (if applicable):** [Attach any relevant screenshots to help illustrate the issue] ## Additional Information This issue affects the usability of switching between conversation threads and disrupts the workflow, especially when copying data from threads. It appears to be related to how artifacts are handled across multiple threads. ## 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!
GiteaMirror commented 2025-11-11 15:05:35 -06:00
Author
Owner
Copy Link

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

Could you share your chat export here?

@tjbck commented on GitHub (Oct 12, 2024): Could you share your chat export here?
GiteaMirror commented 2025-11-11 15:05:35 -06:00
Author
Owner
Copy Link

@chrisoutwright commented on GitHub (Oct 13, 2024):

Could you share your chat export here?

chat-export-1728780188184.json
The json, will this suffice?

@chrisoutwright commented on GitHub (Oct 13, 2024): > Could you share your chat export here? [chat-export-1728780188184.json](https://github.com/user-attachments/files/17352581/chat-export-1728780188184.json) The json, will this suffice?
GiteaMirror commented 2025-11-11 15:05:35 -06:00
Author
Owner
Copy Link

@iambari commented on GitHub (Jan 3, 2025):

Really need this setting, it is a harsh to use openweb ui with the artifacts...

@iambari commented on GitHub (Jan 3, 2025): Really need this setting, it is a harsh to use openweb ui with the artifacts...
GiteaMirror commented 2025-11-11 15:05:35 -06:00
Author
Owner
Copy Link

@tempppabx1 commented on GitHub (Feb 14, 2025):

This option is also needed. Sometimes you are just discussing code snippets with the AI, and in this case the artifacts that pop up automatically are actually a nuisance.

@tempppabx1 commented on GitHub (Feb 14, 2025): This option is also needed. Sometimes you are just discussing code snippets with the AI, and in this case the artifacts that pop up automatically are actually a nuisance.
GiteaMirror commented 2025-11-11 15:05:35 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 13, 2025):

Added to dev.

@tjbck commented on GitHub (Apr 13, 2025): Added to dev.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#2355
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?