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
I have no knowledge bases, but the LLM sees the KB tools and tries to use them.
I can disable the built-in tools, but then it doesn't have access to memory, chat history etc.
Desired Solution you'd like
Separate options to enable/disable individual built-in tools or groups of built-in tools. For my use-case this could be global, but I imagine some people would want it per-model.
Alternatives Considered
Maybe automatically disable knowledge base tools if there are no knowledge bases? But it would be better to be able to control all tools
Originally created by @Bickio on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20986
### 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
I have no knowledge bases, but the LLM sees the KB tools and tries to use them.
I can disable the built-in tools, but then it doesn't have access to memory, chat history etc.
### Desired Solution you'd like
Separate options to enable/disable individual built-in tools or groups of built-in tools. For my use-case this could be global, but I imagine some people would want it per-model.
### Alternatives Considered
Maybe automatically disable knowledge base tools if there are no knowledge bases? But it would be better to be able to control all tools
### Additional Context
A single toggle was added to enable/disable all built-in tools together, but as above this is not sufficient. Related issue: https://github.com/open-webui/open-webui/issues/20429
@Classic298 I'd appreciate your thoughts on this. The native tool calling for built-in tools is a huge upgrade, but currently not usable for me due to the above
<!-- gh-comment-id:3808759806 -->
@Bickio commented on GitHub (Jan 28, 2026):
@Classic298 I'd appreciate your thoughts on this. The native tool calling for built-in tools is a huge upgrade, but currently not usable for me due to the above
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 @Bickio on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20986
Check Existing Issues
Verify Feature Scope
Problem Description
I have no knowledge bases, but the LLM sees the KB tools and tries to use them.
I can disable the built-in tools, but then it doesn't have access to memory, chat history etc.
Desired Solution you'd like
Separate options to enable/disable individual built-in tools or groups of built-in tools. For my use-case this could be global, but I imagine some people would want it per-model.
Alternatives Considered
Maybe automatically disable knowledge base tools if there are no knowledge bases? But it would be better to be able to control all tools
Additional Context
A single toggle was added to enable/disable all built-in tools together, but as above this is not sufficient. Related issue: https://github.com/open-webui/open-webui/issues/20429
@Bickio commented on GitHub (Jan 28, 2026):
@Classic298 I'd appreciate your thoughts on this. The native tool calling for built-in tools is a huge upgrade, but currently not usable for me due to the above
@Classic298 commented on GitHub (Jan 28, 2026):
Should be already implemented in dev