I’m currently facing a challenge that I believe many of you might find intriguing or share similar frustrations. When using the Brave browser integrated with my custom ollama server setup for web page queries via Leo UI, I encounter an issue where the context length is automatically cropped by default.
This crop affects not only user experience but also impedes my RAG (Retrieval Augmented Generation) middleware efforts to enhance response quality on these web page queries within a single platform.
The goal here is simple – we need users of Brave browser with Leo integration the ability to decide and control how much context they want their queries should include when performing web page lookups, without inadvertently cutting off essential information that would otherwise enrich responses from both ollama server (our conversational model) as well as RAG supported pipeline end points.