[GH-ISSUE #21762] feat: How to remove previously attached knowledge from the same chat session? #106556

Closed
opened 2026-05-18 04:58:41 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @intelligenceabhii on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21762

Check Existing Issues

  • 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

Hi team,

I’m using Open WebUI with the Knowledge / Document feature. I have a use case where users attach different knowledge sources during the same conversation.

Problem
When a user attaches a new document or knowledge source in an existing chat, the previously attached knowledge still remains in the context. I want the new knowledge to replace the previous one, not merge with it.

Currently:

Knowledge attached earlier continues to influence responses

There is no clear way to fully remove previous knowledge from the same chat

Even after attaching a new document, responses sometimes include information from older knowledge

Questions

Is there a supported way to clear or replace knowledge within the same chat?

If not, is this feature planned?

What is the recommended workflow for switching knowledge dynamically?

Use Case
I’m building a chatbot where users upload different documents (one at a time). Each new upload should be treated independently without requiring a new chat.

Desired Solution you'd like

Expected behavior
One of the following options would solve the issue:

Ability to remove previously attached knowledge from the current chat session

An option like “Replace existing knowledge” when attaching new documents

A way to reset RAG context without starting a new chat

API or configuration to clear conversation-level document context

Alternatives Considered

No response

Additional Context

No response

Originally created by @intelligenceabhii on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21762 ### 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 Hi team, I’m using Open WebUI with the Knowledge / Document feature. I have a use case where users attach different knowledge sources during the same conversation. Problem When a user attaches a new document or knowledge source in an existing chat, the previously attached knowledge still remains in the context. I want the new knowledge to replace the previous one, not merge with it. Currently: Knowledge attached earlier continues to influence responses There is no clear way to fully remove previous knowledge from the same chat Even after attaching a new document, responses sometimes include information from older knowledge Questions Is there a supported way to clear or replace knowledge within the same chat? If not, is this feature planned? What is the recommended workflow for switching knowledge dynamically? Use Case I’m building a chatbot where users upload different documents (one at a time). Each new upload should be treated independently without requiring a new chat. ### Desired Solution you'd like Expected behavior One of the following options would solve the issue: Ability to remove previously attached knowledge from the current chat session An option like “Replace existing knowledge” when attaching new documents A way to reset RAG context without starting a new chat API or configuration to clear conversation-level document context ### Alternatives Considered _No response_ ### Additional Context _No response_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#106556