[PR #24920] feat: add web search support to channels #131589

New Issue

GiteaMirror · 2026-05-21T17:16:45-05:00

GiteaMirror commented

2026-05-21 17:16:45 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/24920
Author: @jqqin
Created: 5/19/2026
Status: 🔄 Open

Base: dev ← Head: feat/channel-web-search

📝 Commits (1)

0b66a8e feat: add web search support to channels

📊 Changes

4 files changed (+167 additions, -25 deletions)

View changed files

📝 backend/open_webui/routers/channels.py (+69 -1)
📝 backend/open_webui/socket/main.py (+10 -1)
📝 src/lib/components/channel/MessageInput.svelte (+63 -1)
📝 src/lib/components/chat/MessageInput/IntegrationsMenu.svelte (+25 -22)

📄 Description

Channel Post: #8050
Issue: #21578

Channels previously did not support web search, while normal chat did. This adds web search support to channels by reusing existing generate_queries and process_web_search functions, displaying a toggle in the IntegrationsMenu, and appending sources to the response footer to verify web search was applied. The implementation mirrors normal chat behavior and respects the same permission checks.

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:

Linked Issue/Discussion: This PR references an existing Issue or Discussion — Closes #___ / Relates to #___. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review.
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:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Add web search support to channels, aligning with existing chat functionality. When users enable web search in a channel message, the system generates search queries, retrieves web results, and includes them as context for the model response.

Added

Web search toggle in channel message input via IntegrationsMenu
Visual indicator (blue pill) when web search is enabled
Search sources displayed at the end of model responses
showToolsButton prop to IntegrationsMenu to control tools visibility

Changed

IntegrationsMenu hides tools section in channels (only web search is supported)

Deprecated

N/A

Removed

N/A

Fixed

N/A

Security

N/A

Breaking Changes

N/A

Additional Information

Reuses existing generate_queries and process_web_search functions from normal chat
Web search results are prepended to user message as context
Sources displayed at the end of responses for transparency and to verify web search was applied
Sources stored in message data before streaming, then appended by the channel emitter when streaming completes (event-driven)
Respects same permission checks as normal chat (config.features.enable_web_search and user permissions)

Screenshots or Videos

After applied the changes:

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/24920 **Author:** [@jqqin](https://github.com/jqqin) **Created:** 5/19/2026 **Status:** 🔄 Open **Base:** `dev` ← **Head:** `feat/channel-web-search` --- ### 📝 Commits (1) - [`0b66a8e`](https://github.com/open-webui/open-webui/commit/0b66a8e12ae9580c872f6e15836530234eab1f52) feat: add web search support to channels ### 📊 Changes **4 files changed** (+167 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/routers/channels.py` (+69 -1) 📝 `backend/open_webui/socket/main.py` (+10 -1) 📝 `src/lib/components/channel/MessageInput.svelte` (+63 -1) 📝 `src/lib/components/chat/MessageInput/IntegrationsMenu.svelte` (+25 -22) </details> ### 📄 Description Channel Post: #8050 Issue: #21578 Channels previously did not support web search, while normal chat did. This adds web search support to channels by reusing existing `generate_queries` and `process_web_search` functions, displaying a toggle in the IntegrationsMenu, and appending sources to the response footer to verify web search was applied. The implementation mirrors normal chat behavior and respects the same permission checks.  # 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] **Linked Issue/Discussion:** This PR references an existing [Issue](https://github.com/open-webui/open-webui/issues) or [Discussion](https://github.com/open-webui/open-webui/discussions) — `Closes #___` / `Relates to #___`. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review. - [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. - [x] **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: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Add web search support to channels, aligning with existing chat functionality. When users enable web search in a channel message, the system generates search queries, retrieves web results, and includes them as context for the model response. ### Added - Web search toggle in channel message input via IntegrationsMenu - Visual indicator (blue pill) when web search is enabled - Search sources displayed at the end of model responses - `showToolsButton` prop to IntegrationsMenu to control tools visibility ### Changed - IntegrationsMenu hides tools section in channels (only web search is supported) ### Deprecated - N/A ### Removed - N/A ### Fixed - N/A ### Security - N/A ### Breaking Changes - N/A --- ### Additional Information - Reuses existing `generate_queries` and `process_web_search` functions from normal chat - Web search results are prepended to user message as context - Sources displayed at the end of responses for transparency and to verify web search was applied - Sources stored in message data before streaming, then appended by the channel emitter when streaming completes (event-driven) - Respects same permission checks as normal chat (`config.features.enable_web_search` and user permissions) ### Screenshots or Videos After applied the changes: <img width="441" height="182" alt="image" src="https://github.com/user-attachments/assets/092bf2c3-8552-49cf-abc4-13f9ca105510" /> <img width="1065" height="408" alt="image" src="https://github.com/user-attachments/assets/4b3d10e4-8b35-42f3-93bc-4db5901c179c" /> ### Contributor License Agreement  - [x] 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-05-21 17:16:45 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#131589