mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #24681] feat: Enable open-terminal based automations #91118
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#91118
Reference in New Issue
Block a user
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 @tkg61 on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24681
Check Existing Issues
Verify Feature Scope
Problem Description
Unable to access open-terminal integration from an automation
Desired Solution you'd like
Add a check box in the workspace model config or automation creation panel to enable open-terminal to be a tool that is able to be used in an automation
Alternatives Considered
No response
Additional Context
Have an automation be able to work on things in a terminal would be amazing!
@owui-terminator[bot] commented on GitHub (May 13, 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:
🟣 #22137 issue: No tools added when Open Terminal is used via direct connection
This issue reports that when Open Terminal is connected, the model receives no terminal tools at all. The new feature request is also about making Open Terminal available to automations, so both center on exposing Open Terminal capabilities to the LLM/tooling layer.
by karuko24 ·
bug🟢 #22528 feat: Sync chat file uploads to Open Terminal filesystem when terminal is connected
This request is specifically about Open Terminal integration gaps in file/automation workflows. It shows related Open Terminal usability friction and depends on the same terminal connection plumbing that the new issue wants to extend into automations.
by fplonka-ft
🟣 #12324 feat: system prompt for tools
Although broader than Open Terminal, it is directly about tool awareness in the system prompt and models not recognizing tools. That is closely related to enabling Open Terminal as an automation tool, which likely requires the same tool-prompting/integration path.
by skyer9
🟣 #8907 Request for a feature similar to ChatGPT operator or Browser Use (Web Tasks Automation)
This is a broader automation feature request for web-task automation similar to Operator/Browser Use. It is conceptually aligned with the new issue’s request to enable terminal-based automations, even though it is not Open Terminal-specific.
by prudhvi6e
💡 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.
@Classic298 commented on GitHub (May 13, 2026):
uhh pretty sure thats possible if you give the model access to your open terminal by default hmmm but i think you mean to toggle it from the automation window?
@tkg61 commented on GitHub (May 13, 2026):
Correct, if i create an automation that asks the model what tools it has available i get this:
If i ask the same model inside the same chat after the automation has run what tools it has access to it shows:
@tkg61 commented on GitHub (May 13, 2026):
Ok, i found my issue, the terminal selector in the model config was totally overlooked on my end since it was a little blended together in teh dark mode version in my other test instance. After assigning a terminal from the drop down to the model, this solved my issue!