I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
When you assign knowledge to a specific model, alot of the knowledgebase tools are unavailable.
That means the model cannot perform a list_knowledge_bases to find out specific KB id's
Thus queries with query_knowledge_files are done without a specific KB id and search is done on all available files.
Tools without KBs assigned:
list_knowledge_bases: List the user's accessible knowledge bases
search_knowledge_bases: Search the user's accessible knowledge bases by name and description
query_knowledge_bases: Search knowledge bases by semantic similarity to query
search_knowledge_files: Search files across knowledge bases the user has access to
query_knowledge_files: Search knowledge base files using semantic/vector search
view_knowledge_file: Get the full content of a file from a knowledge base
Tools with KBs assigned:
query_knowledge_files: Search knowledge base files using semantic search across collections, files, and notes
view_file: Get the full content of a file by its ID
Desired Solution you'd like
Inject KB names, description and ID's in starting prompt, and/or make all tools available when working with a model with assigned KBs.
Alternatives Considered
Multiple models with more specific KBs;
Could work, but we're trying to make users be less prone to making bad choices.
Additional Context
No response
Originally created by @HenkieTenkie62 on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21624
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
When you assign knowledge to a specific model, alot of the knowledgebase tools are unavailable.
That means the model cannot perform a list_knowledge_bases to find out specific KB id's
Thus queries with query_knowledge_files are done without a specific KB id and search is done on all available files.
Tools without KBs assigned:
list_knowledge_bases: List the user's accessible knowledge bases
search_knowledge_bases: Search the user's accessible knowledge bases by name and description
query_knowledge_bases: Search knowledge bases by semantic similarity to query
search_knowledge_files: Search files across knowledge bases the user has access to
query_knowledge_files: Search knowledge base files using semantic/vector search
view_knowledge_file: Get the full content of a file from a knowledge base
Tools with KBs assigned:
query_knowledge_files: Search knowledge base files using semantic search across collections, files, and notes
view_file: Get the full content of a file by its ID
### Desired Solution you'd like
Inject KB names, description and ID's in starting prompt, and/or make all tools available when working with a model with assigned KBs.
### Alternatives Considered
Multiple models with more specific KBs;
Could work, but we're trying to make users be less prone to making bad choices.
### Additional Context
_No response_
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 @HenkieTenkie62 on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21624
Check Existing Issues
Verify Feature Scope
Problem Description
When you assign knowledge to a specific model, alot of the knowledgebase tools are unavailable.
That means the model cannot perform a list_knowledge_bases to find out specific KB id's
Thus queries with query_knowledge_files are done without a specific KB id and search is done on all available files.
Tools without KBs assigned:
list_knowledge_bases: List the user's accessible knowledge bases
search_knowledge_bases: Search the user's accessible knowledge bases by name and description
query_knowledge_bases: Search knowledge bases by semantic similarity to query
search_knowledge_files: Search files across knowledge bases the user has access to
query_knowledge_files: Search knowledge base files using semantic/vector search
view_knowledge_file: Get the full content of a file from a knowledge base
Tools with KBs assigned:
query_knowledge_files: Search knowledge base files using semantic search across collections, files, and notes
view_file: Get the full content of a file by its ID
Desired Solution you'd like
Inject KB names, description and ID's in starting prompt, and/or make all tools available when working with a model with assigned KBs.
Alternatives Considered
Multiple models with more specific KBs;
Could work, but we're trying to make users be less prone to making bad choices.
Additional Context
No response
@Classic298 commented on GitHub (Feb 19, 2026):
Duplicate
@tjbck commented on GitHub (Feb 19, 2026):
Intended.