github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

feat: Unified Frontend Components for Native and Default Tool Calling #6843

New Issue
Closed
opened 2025-11-11 17:07:15 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 17:07:15 -06:00
Owner
Copy Link

Originally created by @piotrkramek on GitHub (Nov 6, 2025).

Check Existing Issues

  • I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Problem Description

I've noticed that native and default tool calling modes present tool results quite differently to users. With default mode, tool results appear naturally in the conversation as sources. With native mode, the technical details feel a bit more raw - the metadata and results can look intimidating to non-technical users.

The inconsistency between these two modes creates a gap where users might avoid native tool calling simply because of how it looks, even though it offers real benefits. It would be better if both modes provided the same user experience while keeping their backend benefits intact.

Desired Solution you'd like

Add a setting in the Admin Panel under Settings -> Interface:

Tool Result Display Mode (dropdown):

  • Detailed: Shows all tool metadata
  • Compact: Minimal tool indicators, expandable on demand like in the default mode

This way if someone deploys native tool calling for better performance, they could choose "clean" mode and users would see the same friendly interface they're used to with default mode.

Alternatives Considered

No response

Additional Context

Why This Matters

  • Users won't feel intimidated by raw technical output
  • Teams get consistent UI regardless of which tool calling mode they pick
  • Admins can customize the experience for their specific audience
  • Adoption of native tool calling would likely improve since it wouldn't carry that "technical" stigma
Originally created by @piotrkramek on GitHub (Nov 6, 2025). ### Check Existing Issues - [x] I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request. ### Problem Description I've noticed that native and default tool calling modes present tool results quite differently to users. With default mode, tool results appear naturally in the conversation as sources. With native mode, the technical details feel a bit more raw - the metadata and results can look intimidating to non-technical users. The inconsistency between these two modes creates a gap where users might avoid native tool calling simply because of how it looks, even though it offers real benefits. It would be better if both modes provided the same user experience while keeping their backend benefits intact. ### Desired Solution you'd like Add a setting in the Admin Panel under Settings -> Interface: Tool Result Display Mode (dropdown): - Detailed: Shows all tool metadata - Compact: Minimal tool indicators, expandable on demand like in the default mode This way if someone deploys native tool calling for better performance, they could choose "clean" mode and users would see the same friendly interface they're used to with default mode. ### Alternatives Considered _No response_ ### Additional Context Why This Matters - Users won't feel intimidated by raw technical output - Teams get consistent UI regardless of which tool calling mode they pick - Admins can customize the experience for their specific audience - Adoption of native tool calling would likely improve since it wouldn't carry that "technical" stigma
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
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#6843
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?