I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
While it's true that the majority of tools are designed to output JSON, this is not universal. In my case, I've deliberately written tools which output a multi line python string.
Unfortunately, while this works great for the LLM, the user-facing display is suboptimal, displaying the string in __repr__ format (double quotes, with escaped newlines).
Desired Solution you'd like
If the tool call output is a python string, it should be displayed naturally in a monospace block instead of quoted/escaped.
Alternatives Considered
I guess I could resolve some of this by providing an HTML representation of the output for display, but this feels heavy-handed when a simple string presentation would be sufficient.
Additional Context
No response
Originally created by @Bickio on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21553
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
While it's true that the majority of tools are designed to output JSON, this is not universal. In my case, I've deliberately written tools which output a multi line python string.
Unfortunately, while this works great for the LLM, the user-facing display is suboptimal, displaying the string in `__repr__` format (double quotes, with escaped newlines).
### Desired Solution you'd like
If the tool call output is a python string, it should be displayed naturally in a monospace block instead of quoted/escaped.
### Alternatives Considered
I guess I could resolve some of this by providing an HTML representation of the output for display, but this feels heavy-handed when a simple string presentation would be sufficient.
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Bickio on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21553
Check Existing Issues
Verify Feature Scope
Problem Description
While it's true that the majority of tools are designed to output JSON, this is not universal. In my case, I've deliberately written tools which output a multi line python string.
Unfortunately, while this works great for the LLM, the user-facing display is suboptimal, displaying the string in
__repr__format (double quotes, with escaped newlines).Desired Solution you'd like
If the tool call output is a python string, it should be displayed naturally in a monospace block instead of quoted/escaped.
Alternatives Considered
I guess I could resolve some of this by providing an HTML representation of the output for display, but this feels heavy-handed when a simple string presentation would be sufficient.
Additional Context
No response
@tjbck commented on GitHub (Feb 22, 2026):
Addressed in dev.