issue: ui/ux improvement - add more details on placeholders like `run_command`

[johnnynanjiang]

Before Submitting

• I searched open and closed issues and discussions for an existing report.
• I checked whether this is already fixed on the dev branch or latest source.
• I understand that maintainers want a well-written issue before any code pull request.
• I am using the latest available version of Open WebUI for my install method.
• This is not a security vulnerability.

Installation Method

Docker

Open WebUI Version

v0.11.0

Operating System

macOS 26.5.1 (25F80)

Browser

No response

Ollama Version

No response

Summary

A discussion and some exploration took place already, and confirmed it is a real issue with both Open WebUI Interface (rendering) as well as Computer (data source).
open-webui/open-webui#28762

Expected Behavior

Would be better to add more details on it. e.g. run_command: command name, parameters, ... (similar to Bash)

---

Or something constant with current ui, like below

Actual Behavior

Currently run_command appears in answers more like a placeholder without giving much information.

Steps to Reproduce

Any prompts that trigger tools, such as bash, fetch

Logs, Screenshots, and Config

Additional Information

No response

[owui-terminator]

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

1. 🟣 #14835 issue: Tools info not shown in UI
   This issue is directly about tool information not being shown in the UI, including the tool name, parameters, and response. It matches the new report’s request to make run_command and similar tool placeholders display richer details instead of a generic placeholder.
   by m-ibm · bug

2. 🟣 #5520 Show tool usage in chat
   The request is the same broad UX problem: showing tool usage in chat with the tool name, parameters, and result. The new issue is a more specific rendering improvement for run_command, but it belongs to the same feature area.
   by MindFreeze

3. 🟣 #24634 issue:

   Details

   tag not rendered, displayed as raw text
   This is another tool-rendering problem in the chat UI, where tool-call markup is not displayed properly and instead appears as raw text. It is related because the new issue also concerns how tool-call information is presented to the user.
   by sharyuke

4. 🟣 #9768 API Tool arguments formatting issue
   This issue covers incorrect formatting of tool-call arguments in Open WebUI’s API response. It is related because the new report asks for tool placeholders like run_command to expose more meaningful parameter details, and both involve how tool arguments are represented.
   by Seniorsimo

---

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

[johnnynanjiang]

Would this issue be prioritised high as there are a lot of reporting out there?