open-webui / open-webui/computer
bug: Browser tools not available in non-workspace chats
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I noticed that the browser tools are not available for chats created outside of a workspace, while chats inside a workspace do have full access to them.
Steps to reproduce:
- Start an Open WebUI Computer (cptr) instance and open the web UI.
- Create a chat inside a workspace and ask the model to list its available tools. All browser tools are present (see attached screenshot for reference).
- Create a new chat that is independent of any workspace.
- Ask the model to list its available tools, or request a browser-related action (e.g., "navigate to https://example.com").
- Observe that the browser tools are missing and no browser actions can be performed in the non-workspace chat.
The following tools are not available in non-workspace chats:
browser_navigatebrowser_snapshotbrowser_clickbrowser_typebrowser_screenshotbrowser_evaluate
Expected behavior: Non-workspace chats should have access to the browser tools, just like workspace chats.
I've attached a screenshot showing the toolset that is missing from non-workspace chats. Happy to provide any further details if helpful.
Thank you for looking into this!
Best regards,
Joshua Krimmer
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing how browser tools are exposed in workspace chats versus independent chats in the Open WebUI Computer web UI. Trace the chat tool-availability entry point and verify that non-workspace chats expose browser_navigate, browser_snapshot, browser_click, browser_type, browser_screenshot, and browser_evaluate; done means the listed tools are available in both chat types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100