I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.32
Ollama Version (if applicable)
No response
Operating System
Linux
Browser (if applicable)
No response
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
The Web Search tool should retrieve multiple relevant sources from the web.
The assistant should generate context-rich answers with proper citations or summarized context from all retrieved URLs.
Actual Behavior
When using the built-in Web Search feature in OpenWebUI, search results are often incomplete, inconsistent, or truncated, the assistant retrieves only a few sources and generates short, low-context answers.
Only 1–2 sources are fetched for most queries (even general ones).
The assistant gives very short answers without context or depth.
Steps to Reproduce
Open the chat UI and ask any query .
Observe that only 1–2 sources are fetched and the answer is very short.
Logs & Screenshots
Additional Information
No response
Originally created by @aimendenche-nw on GitHub (Oct 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18290
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.32
### Ollama Version (if applicable)
_No response_
### Operating System
Linux
### Browser (if applicable)
_No response_
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
The Web Search tool should retrieve multiple relevant sources from the web.
The assistant should generate context-rich answers with proper citations or summarized context from all retrieved URLs.
### Actual Behavior
When using the built-in Web Search feature in OpenWebUI, search results are often incomplete, inconsistent, or truncated, the assistant retrieves only a few sources and generates short, low-context answers.
Only 1–2 sources are fetched for most queries (even general ones).
The assistant gives very short answers without context or depth.
### Steps to Reproduce
Open the chat UI and ask any query .
Observe that only 1–2 sources are fetched and the answer is very short.
### Logs & Screenshots
<img width="1580" height="613" alt="Image" src="https://github.com/user-attachments/assets/04c89980-1444-4583-b76b-fff606b15373" />
<img width="1592" height="809" alt="Image" src="https://github.com/user-attachments/assets/ed5f7373-1624-4cd8-9593-144d0881ac66" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-20 00:46:36 -05:00
@aimendenche-nw commented on GitHub (Oct 13, 2025):
Hello @tjbck do you know about this and if there is a quick fix for this issue?
Thanks!
<!-- gh-comment-id:3397338717 -->
@aimendenche-nw commented on GitHub (Oct 13, 2025):
Hello @tjbck do you know about this and if there is a quick fix for this issue?
Thanks!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @aimendenche-nw on GitHub (Oct 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18290
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.32
Ollama Version (if applicable)
No response
Operating System
Linux
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
The Web Search tool should retrieve multiple relevant sources from the web.
The assistant should generate context-rich answers with proper citations or summarized context from all retrieved URLs.
Actual Behavior
When using the built-in Web Search feature in OpenWebUI, search results are often incomplete, inconsistent, or truncated, the assistant retrieves only a few sources and generates short, low-context answers.
Only 1–2 sources are fetched for most queries (even general ones).
The assistant gives very short answers without context or depth.
Steps to Reproduce
Open the chat UI and ask any query .
Observe that only 1–2 sources are fetched and the answer is very short.
Logs & Screenshots
Additional Information
No response
@aimendenche-nw commented on GitHub (Oct 13, 2025):
Hello @tjbck do you know about this and if there is a quick fix for this issue?
Thanks!