I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
Latest docker cuda image (0.8.10)
Ollama Version (if applicable)
N/A
Operating System
Linux with Docker
Browser (if applicable)
Firefox
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
When it finds the relevant knowledgebase it should use just that one
Actual Behavior
It's not doing that. Instead, tools knowledgebase search (regular knowledgebase search is fine) runs out of context.
See attached images.
Steps to Reproduce
Create several knowledgebases with large files.
When using tool search (not manually specifying the knowledgebase) watch as it runs itself out of context by searching through the knowledgebase.
Logs & Screenshots
Additional Information
No response
Originally created by @frenzybiscuit on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22624
### 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 have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
Latest docker cuda image (0.8.10)
### Ollama Version (if applicable)
N/A
### Operating System
Linux with Docker
### Browser (if applicable)
Firefox
### 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
When it finds the relevant knowledgebase it should use just that one
### Actual Behavior
It's not doing that. Instead, tools knowledgebase search (regular knowledgebase search is fine) runs out of context.
See attached images.
### Steps to Reproduce
Create several knowledgebases with large files.
When using tool search (not manually specifying the knowledgebase) watch as it runs itself out of context by searching through the knowledgebase.
### Logs & Screenshots
<img width="839" height="836" alt="Image" src="https://github.com/user-attachments/assets/c3b10875-59ad-4e99-b54a-facbfb08fd67" />
<img width="1876" height="62" alt="Image" src="https://github.com/user-attachments/assets/775d593c-5b38-4e54-9f03-d063124621a1" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-05 23:09:09 -05:00
@frenzybiscuit commented on GitHub (Mar 12, 2026):
I renamed lore.txt to Stargate Lore.txt and it seems to have fixed the issue.. although, I don't really understand why this would matter, since the lore.txt is within a knowledgebase called stargate?
<!-- gh-comment-id:4049040643 -->
@frenzybiscuit commented on GitHub (Mar 12, 2026):
I renamed lore.txt to Stargate Lore.txt and it seems to have fixed the issue.. although, I don't really understand why this would matter, since the lore.txt is within a knowledgebase called stargate?
If you mean search_ ... tool calls and view_knowledge_file for example, then you need to tell your model to avoid these tools (or only "query" the knowledge base, is sufficient as a prompt) as to avoid out of context errors.
Not really an open webui issue. Tools work as intended. Files are too large/model shouldn't use these tools in that case
<!-- gh-comment-id:4049157347 -->
@Classic298 commented on GitHub (Mar 12, 2026):
no image attached (?)
If you mean search_ ... tool calls and view_knowledge_file for example, then you need to tell your model to avoid these tools (or only "query" the knowledge base, is sufficient as a prompt) as to avoid out of context errors.
Not really an open webui issue. Tools work as intended. Files are too large/model shouldn't use these tools in that case
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 @frenzybiscuit on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22624
Check Existing Issues
Installation Method
Docker
Open WebUI Version
Latest docker cuda image (0.8.10)
Ollama Version (if applicable)
N/A
Operating System
Linux with Docker
Browser (if applicable)
Firefox
Confirmation
README.md.Expected Behavior
When it finds the relevant knowledgebase it should use just that one
Actual Behavior
It's not doing that. Instead, tools knowledgebase search (regular knowledgebase search is fine) runs out of context.
See attached images.
Steps to Reproduce
Create several knowledgebases with large files.
When using tool search (not manually specifying the knowledgebase) watch as it runs itself out of context by searching through the knowledgebase.
Logs & Screenshots
Additional Information
No response
@frenzybiscuit commented on GitHub (Mar 12, 2026):
I renamed lore.txt to Stargate Lore.txt and it seems to have fixed the issue.. although, I don't really understand why this would matter, since the lore.txt is within a knowledgebase called stargate?
@Classic298 commented on GitHub (Mar 12, 2026):
no image attached (?)
If you mean search_ ... tool calls and view_knowledge_file for example, then you need to tell your model to avoid these tools (or only "query" the knowledge base, is sufficient as a prompt) as to avoid out of context errors.
Not really an open webui issue. Tools work as intended. Files are too large/model shouldn't use these tools in that case