github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-08-30 17:25:30 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

feat: Add Frontend Configuration for RAG_WEB_LOADER_ENGINE #4813

New Issue
Closed
opened 2025-11-11 16:03:39 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 16:03:39 -06:00
Owner
Copy Link
Copy Source

Originally created by @tth37 on GitHub (Apr 11, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Currently, users can configure the RAG_WEB_SEARCH_ENGINE (e.g., DuckDuckGo, Google) directly from the Open WebUI frontend settings. However, the related configuration RAG_WEB_LOADER_ENGINE, which controls the method used to fetch and parse web page content for RAG, appears to only be configurable via environment variables or backend configuration (on latest main branch). This makes it less convenient to switch or experiment with different loading mechanisms compared to the search engine setting.

Desired Solution you'd like

I propose adding a setting in the Open WebUI frontend (perhaps in the "Settings" -> "Web Search" section, near the Web Search Engine selector) that allows users to select the desired RAG_WEB_LOADER_ENGINE. This could be a dropdown menu listing the available loader engines supported by the backend.

Alternatives Considered

No response

Additional Context

No response

Originally created by @tth37 on GitHub (Apr 11, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Currently, users can configure the `RAG_WEB_SEARCH_ENGINE` (e.g., DuckDuckGo, Google) directly from the Open WebUI frontend settings. However, the related configuration `RAG_WEB_LOADER_ENGINE`, which controls the method used to fetch and parse web page content for RAG, appears to only be configurable via environment variables or backend configuration (on latest main branch). This makes it less convenient to switch or experiment with different loading mechanisms compared to the search engine setting. ### Desired Solution you'd like I propose adding a setting in the Open WebUI frontend (perhaps in the "Settings" -> "Web Search" section, near the Web Search Engine selector) that allows users to select the desired `RAG_WEB_LOADER_ENGINE`. This could be a dropdown menu listing the available loader engines supported by the backend. ### Alternatives Considered _No response_ ### Additional Context _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4813