github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #500] feat: verbose debug mode for admins #27622

New Issue
Closed
opened 2026-04-25 02:22:03 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 02:22:03 -05:00
Owner
Copy Link

Originally created by @hemangjoshi37a on GitHub (Jan 17, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/500

Debug Mode for showing debug info in web page for admins.

Originally created by @hemangjoshi37a on GitHub (Jan 17, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/500 `Debug Mode` for showing debug info in web page for admins.
GiteaMirror added the non-core label 2026-04-25 02:22:03 -05:00
GiteaMirror commented 2026-04-25 02:22:05 -05:00
Author
Owner
Copy Link

@hemangjoshi37a commented on GitHub (Jan 19, 2024):

Feature Description:
I propose the addition of a 'Copy Debug Info' button in the chat window. This feature would allow users to easily copy relevant debug information from the chat interface and paste it directly into GitHub issues.

Purpose and Benefits:

  • This button would streamline the process of reporting bugs or issues encountered within the chat interface.
  • It ensures that essential debug information is accurately and effortlessly shared with developers, enhancing the efficiency of issue resolution.
  • Reduces the manual effort required by users to gather and report technical details.

Suggested Implementation:

  • The 'Copy Debug Info' button could be positioned conveniently in the chat interface, possibly near the chat input or the 'send' button.
  • Upon clicking, it should automatically copy relevant information such as error logs, state of the application, user actions leading up to the bug, and any other pertinent technical details.
  • The copied information should be formatted in a way that is easily pastable into a GitHub issue, aiding in clarity and readability.

Additional Considerations:

  • The feature should respect user privacy and security, ensuring that no sensitive or personal data is included in the copied debug information.
  • Providing an option for the user to review and edit the copied information before pasting it into a GitHub issue could be beneficial.

Potential Impact:
Implementing this feature could significantly improve user experience in terms of ease of reporting issues and could aid developers in receiving more consistent and detailed bug reports, thereby accelerating the debugging and resolution process.

<!-- gh-comment-id:1899900005 --> @hemangjoshi37a commented on GitHub (Jan 19, 2024): **Feature Description:** I propose the addition of a `'Copy Debug Info'` button in the chat window. This feature would allow users to easily copy relevant debug information from the chat interface and paste it directly into GitHub issues. **Purpose and Benefits:** - This button would streamline the process of reporting bugs or issues encountered within the chat interface. - It ensures that essential debug information is accurately and effortlessly shared with developers, enhancing the efficiency of issue resolution. - Reduces the manual effort required by users to gather and report technical details. **Suggested Implementation:** - The `'Copy Debug Info'` button could be positioned conveniently in the chat interface, possibly near the chat input or the 'send' button. - Upon clicking, it should automatically copy relevant information such as error logs, state of the application, user actions leading up to the bug, and any other pertinent technical details. - The copied information should be formatted in a way that is easily pastable into a GitHub issue, aiding in clarity and readability. **Additional Considerations:** - The feature should respect user privacy and security, ensuring that no sensitive or personal data is included in the copied debug information. - Providing an option for the user to review and edit the copied information before pasting it into a GitHub issue could be beneficial. **Potential Impact:** Implementing this feature could significantly improve user experience in terms of ease of reporting issues and could aid developers in receiving more consistent and detailed bug reports, thereby accelerating the debugging and resolution process.
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 Label non-core
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#27622
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?