Operator and Deep Learning have become very useful tools that would make OpenWebUI that much better. If we could either develop our own, or implement an integration with Browser Use or Open Operator.
I have seen the discussion about this #8917 This would be a great addition to OpenWebUI and I would like to know if this is on the timeline, if so, how far down the line until we see this into some production releases?
Originally created by @uwzis on GitHub (Feb 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10151
# Feature Request
Operator and Deep Learning have become very useful tools that would make OpenWebUI that much better. If we could either develop our own, or implement an integration with [Browser Use](https://github.com/browser-use) or [Open Operator](https://github.com/browserbase/open-operator).
I have seen the discussion about this #8917 This would be a great addition to OpenWebUI and I would like to know if this is on the timeline, if so, how far down the line until we see this into some production releases?
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 @uwzis on GitHub (Feb 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10151
Feature Request
Operator and Deep Learning have become very useful tools that would make OpenWebUI that much better. If we could either develop our own, or implement an integration with Browser Use or Open Operator.
I have seen the discussion about this #8917 This would be a great addition to OpenWebUI and I would like to know if this is on the timeline, if so, how far down the line until we see this into some production releases?