mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-15 21:19:39 -05:00
[GH-ISSUE #3518] enh: confusing LLM feedback when no retrieval happened because of high RAG_RELEVANCE_THRESHOLD #51959
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#51959
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Robinsane on GitHub (Jun 29, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/3518
Is your feature request related to a problem? Please describe.
When no RAG context is used because all results were lower than the value in RAG_RELEVANCE_THRESHOLD, the user is made to think no file is provided (based on how the LLMs respond).
Describe the solution you'd like
I think it would be very nice to provide a hard coded context that explains the situation in these cases, so the LLM's response will be adjusted and relevant.
hard coded context example.:
"No context was added to this prompt. It's possible that a file was added correctly, but no text was relevant enough according to the setting RAG_RELEVANCE_THRESHOLD."
Additional context
