mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
feat: Secure Client-Side Web Browsing for browse_url Feature #4550
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#4550
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 @flefevre on GitHub (Mar 25, 2025).
Check Existing Issues
Problem Description
Description:
Currently, the browse_url feature in Open WebUI is implemented server-side, which poses several challenges:
Server-side internet access is restricted via whitelisting, limiting its usability.
Users lack control over the exact queries sent by the LLM, which can lead to unintended data exposure.
Proposed Solution:
Implement a client-side browsing approach, allowing the user's local machine to handle web requests instead of the server.
Desired Solution you'd like
Key Features:
Offload web search and browsing tasks to the user's machine.
Use browser APIs (e.g., fetch, WebView, or an extension) to perform searches directly.
Provide an interactive mode where users can review and approve search queries before they are executed.
Display the exact request generated by the LLM, giving full transparency.
Ensure that sensitive data is not accidentally sent to external services.
Allow users to define custom filtering rules or manually edit queries before execution.
Alternatives Considered
No response
Additional Context
Expected Benefits:
✅ Bypasses server-side internet restrictions (whitelist issues).
✅ Improves user control and transparency over web queries.
✅ Reduces risks of unintended data exposure by enforcing query validation.
Would love to hear thoughts from the maintainers on feasibility and best practices for implementation!
François