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
Currently, turning on web search in a chat or as a native tool available by default to a model makes two tools available to the model, search_web and fetch_url. The global toggle for web search within the admin panel also toggles both of these tools at once.
This is not usually an issue as the features are intended to be used together. However, I've found fetch_url to be quite limiting in its customizability, even when using a locally hosted instance of firecrawl. So far I've solved the issue by having a custom web scrape tool and a custom web search tool, and disabling the built-in web search altogether. However, while a custom web scrape tool can work better than the built-in fetch_url tool, there is no real reason not to use the built-in search_web tool, which has the added benefit of allowing models in chat to attribute sources, something that isn't possible with a custom tool configuration (at least not easily as far as I can tell).
Desired Solution you'd like
I would like a separate toggle, both in the admin panel under web search and also on a per-chat/per-model basis, for the web_search and and fetch_url tools separately.
Alternatives Considered
The purpose of this request was to add more customizability, specifically for a replacement of fetch_url. I've also considered suggesting adding the desired customizations to fetch_url, but given the broad range of customizations people may like to have, that path seems like a fool's errand and it's much easier to just create separate toggles and let end users create their own tools to their own specifications.
Additional Context
No response
Originally created by @DanielHe212 on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23964
### 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
Currently, turning on web search in a chat or as a native tool available by default to a model makes two tools available to the model, search_web and fetch_url. The global toggle for web search within the admin panel also toggles both of these tools at once.
This is not usually an issue as the features are intended to be used together. However, I've found fetch_url to be quite limiting in its customizability, even when using a locally hosted instance of firecrawl. So far I've solved the issue by having a custom web scrape tool and a custom web search tool, and disabling the built-in web search altogether. However, while a custom web scrape tool can work better than the built-in fetch_url tool, there is no real reason not to use the built-in search_web tool, which has the added benefit of allowing models in chat to attribute sources, something that isn't possible with a custom tool configuration (at least not easily as far as I can tell).
### Desired Solution you'd like
I would like a separate toggle, both in the admin panel under web search and also on a per-chat/per-model basis, for the web_search and and fetch_url tools separately.
### Alternatives Considered
The purpose of this request was to add more customizability, specifically for a replacement of fetch_url. I've also considered suggesting adding the desired customizations to fetch_url, but given the broad range of customizations people may like to have, that path seems like a fool's errand and it's much easier to just create separate toggles and let end users create their own tools to their own specifications.
### 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 @DanielHe212 on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23964
Check Existing Issues
Verify Feature Scope
Problem Description
Currently, turning on web search in a chat or as a native tool available by default to a model makes two tools available to the model, search_web and fetch_url. The global toggle for web search within the admin panel also toggles both of these tools at once.
This is not usually an issue as the features are intended to be used together. However, I've found fetch_url to be quite limiting in its customizability, even when using a locally hosted instance of firecrawl. So far I've solved the issue by having a custom web scrape tool and a custom web search tool, and disabling the built-in web search altogether. However, while a custom web scrape tool can work better than the built-in fetch_url tool, there is no real reason not to use the built-in search_web tool, which has the added benefit of allowing models in chat to attribute sources, something that isn't possible with a custom tool configuration (at least not easily as far as I can tell).
Desired Solution you'd like
I would like a separate toggle, both in the admin panel under web search and also on a per-chat/per-model basis, for the web_search and and fetch_url tools separately.
Alternatives Considered
The purpose of this request was to add more customizability, specifically for a replacement of fetch_url. I've also considered suggesting adding the desired customizations to fetch_url, but given the broad range of customizations people may like to have, that path seems like a fool's errand and it's much easier to just create separate toggles and let end users create their own tools to their own specifications.
Additional Context
No response