Enhance Transparency with User-Facing Tool Usage Indicators #3238

New Issue

2025-11-11T15:26:33-06:00

GiteaMirror commented

2025-11-11 15:26:33 -06:00

Originally created by @jeannotdamoiseaux on GitHub (Jan 10, 2025).

Feature Request

Is your feature request related to a problem? Please describe.
Currently, users cannot see when and which tools (e.g., web searches, code execution) are used to generate answers. This lack of visibility makes responses less transparent and complicates debugging.

Describe the solution you'd like
Introduce a clear, user-facing indicator that displays the tools used during the interaction, including their names and purpose. This could be implemented as a small, expandable section within the interface that logs tool usage in real-time or after a response is generated.

Describe alternatives you've considered

Providing a summary of tool usage in a system-generated note appended to responses.
Adding an optional "debug mode" for users who want detailed logs of tool activity.
Making tool usage visible only in specific views, such as in developer settings.

Additional context
This feature will enhance transparency and trust by showing users how their answers are generated. It will also simplify debugging for maintainers and contributors. Below is a mock example of how the tool usage display might look in the UI:

Originally created by @jeannotdamoiseaux on GitHub (Jan 10, 2025). # Feature Request **Is your feature request related to a problem? Please describe.** Currently, users cannot see when and which tools (e.g., web searches, code execution) are used to generate answers. This lack of visibility makes responses less transparent and complicates debugging. **Describe the solution you'd like** Introduce a clear, user-facing indicator that displays the tools used during the interaction, including their names and purpose. This could be implemented as a small, expandable section within the interface that logs tool usage in real-time or after a response is generated. **Describe alternatives you've considered** - Providing a summary of tool usage in a system-generated note appended to responses. - Adding an optional "debug mode" for users who want detailed logs of tool activity. - Making tool usage visible only in specific views, such as in developer settings. **Additional context** This feature will enhance transparency and trust by showing users how their answers are generated. It will also simplify debugging for maintainers and contributors. Below is a mock example of how the tool usage display might look in the UI:

GiteaMirror closed this issue

2025-11-11 15:26:33 -06:00

GiteaMirror referenced this issue

2026-04-19 19:59:01 -05:00

[GH-ISSUE #3238] Segmentation fault when starting backend on intel cpu. #13185

GiteaMirror referenced this issue

2026-04-25 03:18:13 -05:00

[GH-ISSUE #3238] Segmentation fault when starting backend on intel cpu. #28713

GiteaMirror referenced this issue

2026-05-05 13:04:53 -05:00

[GH-ISSUE #3238] Segmentation fault when starting backend on intel cpu. #51851

GiteaMirror referenced this issue