bug: Browser tools not available in non-workspace chats

[JKGeovision]

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:

1. Start an Open WebUI Computer (cptr) instance and open the web UI.
2. 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).
3. Create a new chat that is independent of any workspace.
4. Ask the model to list its available tools, or request a browser-related action (e.g., "navigate to https://example.com").
5. 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_navigate
• browser_snapshot
• browser_click
• browser_type
• browser_screenshot
• browser_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

[owui-terminator]

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

1. 🟢 #15 feat: computer control / computer use
   This is the core feature request for computer/browser control in cptr and establishes the browser tool subsystem that the new bug is missing from non-workspace chats. The reported missing tools are part of this computer-use feature set.
   by Classic298

2. 🟢 #230 feat: Move workspace-independent chats to the sidebar for easier management
   This issue is about workspace-independent chats, the same chat category affected by the bug. While it focuses on discoverability rather than tools, it confirms that non-workspace chats are a distinct path in the UI and thus likely share the same routing/context problem.
   by JKGeovision

---

💡 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.