github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 11:28:35 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[PR #21599] [MERGED] feat: Adding You.com as a web search provider #41788

New Issue
Closed
opened 2026-04-25 13:55:31 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 13:55:31 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21599
Author: @lazariv
Created: 2/19/2026
Status: ✅ Merged
Merged: 2/21/2026
Merged by: @tjbck

Base: dev ← Head: youcom-websearch

📝 Commits (6)

  • d46cfc1 Add ydc.py provider implementation
  • e755262 Add PersistentConfig entry for you.com
  • 7a4f7de Add Youcom search function import
  • 71f40e0 Update you.com configuration
  • 6c660d6 Add you.com as a web search engine option in frontend
  • 1a57e1f Add YOUCOM_API_KEY to main.py

📊 Changes

5 files changed (+110 additions, -1 deletions)

View changed files

📝 backend/open_webui/config.py (+6 -0)
📝 backend/open_webui/main.py (+2 -0)
➕ backend/open_webui/retrieval/web/ydc.py (+73 -0)
📝 backend/open_webui/routers/retrieval.py (+14 -0)
📝 src/lib/components/admin/Settings/WebSearch.svelte (+15 -1)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

  • Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
  • Description: Provide a concise description of the changes made in this pull request down below.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
  • Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
  • Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
  • Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
  • Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
  • Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:

Changelog Entry

Description

  • API Reference: https://docs.you.com/api-reference/search/v1-search
  • Concatenating the web search description and snippets fields, in order to enrich content:
    • In bypass-web-loader mode: page_content will contain the description plus every snippet passage, giving the LLM significantly more context than just the short description alone.
    • In normal mode (URLs are fetched): the snippet still ends up in the document metadata as "snippet", which enriches BM25 hybrid search scoring via get_enriched_texts(). The full page content comes from the web loader, but the richer snippet metadata improves ranking.
    • No changes needed to SearchResult, process_web_search, get_enriched_texts, or any other file — everything just works through the existing snippet: Optional[str] field.

Added

  • New web search provider you.com

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/21599 **Author:** [@lazariv](https://github.com/lazariv) **Created:** 2/19/2026 **Status:** ✅ Merged **Merged:** 2/21/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `youcom-websearch` --- ### 📝 Commits (6) - [`d46cfc1`](https://github.com/open-webui/open-webui/commit/d46cfc18b3555f78f4fa0d17740da382fbc2995c) Add ydc.py provider implementation - [`e755262`](https://github.com/open-webui/open-webui/commit/e75526212d0957edb64364586b872ace582e4b77) Add PersistentConfig entry for you.com - [`7a4f7de`](https://github.com/open-webui/open-webui/commit/7a4f7de61cb7bea8299d91b15d00cd3f67408ebb) Add Youcom search function import - [`71f40e0`](https://github.com/open-webui/open-webui/commit/71f40e068d457ade522675d46362cc21fe9ef288) Update you.com configuration - [`6c660d6`](https://github.com/open-webui/open-webui/commit/6c660d61d8de85b3940d236f1908c59a302dddf9) Add you.com as a web search engine option in frontend - [`1a57e1f`](https://github.com/open-webui/open-webui/commit/1a57e1ff24f4b2130eac1825d77b94edd2ce993f) Add YOUCOM_API_KEY to main.py ### 📊 Changes **5 files changed** (+110 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+6 -0) 📝 `backend/open_webui/main.py` (+2 -0) ➕ `backend/open_webui/retrieval/web/ydc.py` (+73 -0) 📝 `backend/open_webui/routers/retrieval.py` (+14 -0) 📝 `src/lib/components/admin/Settings/WebSearch.svelte` (+15 -1) </details> ### 📄 Description <!-- ⚠️ CRITICAL CHECKS FOR CONTRIBUTORS (READ, DON'T DELETE) ⚠️ 1. Target the `dev` branch. PRs targeting `main` will be automatically closed. 2. Do NOT delete the CLA section at the bottom. It is required for the bot to accept your PR. --> # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps. - [x] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash. - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes. - [x] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening. - [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: # Changelog Entry ### Description - API Reference: https://docs.you.com/api-reference/search/v1-search - Concatenating the web search `description` and `snippets` fields, in order to enrich content: - In bypass-web-loader mode: `page_content` will contain the description plus every snippet passage, giving the LLM significantly more context than just the short description alone. - In normal mode (URLs are fetched): the snippet still ends up in the document metadata as "snippet", which enriches BM25 hybrid search scoring via `get_enriched_texts()`. The full page content comes from the web loader, but the richer snippet metadata improves ranking. - No changes needed to `SearchResult`, `process_web_search`, `get_enriched_texts`, or any other file — everything just works through the existing `snippet: Optional[str]` field. ### Added - New web search provider you.com --- ### Contributor License Agreement <!-- 🚨 DO NOT DELETE THE TEXT BELOW 🚨 Keep the "Contributor License Agreement" confirmation text intact. Deleting it will trigger the CLA-Bot to INVALIDATE your PR. --> By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 13:55:31 -05:00
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 Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#41788
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?