mirror of
https://github.com/open-webui/computer.git
synced 2026-11-05 01:17:24 +00:00
[GH-ISSUE #270] issue: ui/ux improvement - add more details on placeholders like run_command #179
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/computer#179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @johnnynanjiang on GitHub (Sep 7, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/270
Before Submitting
devbranch or latest source.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 asComputer(data source).https://github.com/open-webui/open-webui/discussions/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,fetchLogs, Screenshots, and Config
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Sep 7, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #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_commandand similar tool placeholders display richer details instead of a generic placeholder.by m-ibm ·
bug🟣 #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
🟣 #24634 issue:
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
🟣 #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_commandto 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 commented on GitHub (Sep 8, 2026):
Would this issue be prioritised high as there are a lot of reporting out there?
@Philogag commented on GitHub (Oct 14, 2026):
And the think context block between tool calls also not show on WebUI side