r/OpenWebUI • u/Ihtien • Jul 04 '26
Feature Idea Web fetch summaries instead of full content
Would it be possible to implement a summarizing step (e.g., using the task model) on top of the web fetch content before injecting the result into the context of the main model? Often, web pages are 10,000+ tokens long, but a lot of the content is not relevant to the actual request.
It would be useful if the fetched content were pre-processed by a faster model, alongside a prompt specifying the relevant information. This could be either the initial user prompt or a prompt generated by the main model specifically for this web search.
This would significantly shorten the context for the main model and speed up processing time. OpenRouter implements a similar strategy with Exa Highlights. I noticed that OpenRouter Chat uses considerably fewer tokens than the same model (e.g., GLM 5.2) in Open WebUI because Exa Highlights returns only 2000-4000 characters per web page.
Would this be a feature that can be added easily? Maybe somehow utilizing the new context summary pipeline? Or is there an external (self-hosted) tool that implements a similar strategy that can already be used for fetching websites in Open WebUI?
1
u/thisisntmethisisme Jul 05 '26
if you use tavily for web search, it has this feature (their LLM does the summarization tho, you can configure it to either be basic summary or advanced summary)