bug: Browser tools not available in non-workspace chats
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- full-stack
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.
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
- Dominant language
- Python
- Stars
- 570
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
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.
More from open-webui/computer
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#293 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#286 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-webui/computer#276 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-webui/computer#271 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/computer#269 · 1 comment ·
All issues in open-webui/computer
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·