[GH-ISSUE #10510] Feature Request: More control over uploaded files: full context / analyze with code interpreter #15922

New Issue

GiteaMirror · 2026-04-19T21:59:50-05:00

GiteaMirror commented

2026-04-19 21:59:50 -05:00

Originally created by @Capsar on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10510

Feature Request

Thank you for the recent updates with the code interpreter! They have made it apparent that more file control would be very nice to have.

Problem: It seems that now, documents that are uploaded in a chat are always automatically loaded in through the RAG / Embedding system (Admin Panel -> Settings -> Documents).

Solution: It would be nice to also have an option in the admin panel / chat where file extensions can be defined that should be handled through this system and which should not. Because sometimes the full content of the file is wanted. Sometimes the file should be made available to the code execution / interpreter for further analysis.

So to conclude, the feature request is:

Feature to enable / disable uploaded files be accessible to the pyodide or jupyter code execution / interpreter backend.
Feature to decide which file extensions are loaded in through the RAG / embedding system.
Feature to include entire document as context to the prompt. (instead of embedded & RAG-ed)

Originally created by @Capsar on GitHub (Feb 21, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/10510 # Feature Request Thank you for the recent updates with the code interpreter! They have made it apparent that more file control would be very nice to have. Problem: It seems that now, documents that are uploaded in a chat are always automatically loaded in through the RAG / Embedding system (Admin Panel -> Settings -> Documents). Solution: It would be nice to also have an option in the admin panel / chat where file extensions can be defined that should be handled through this system and which should not. Because sometimes the full content of the file is wanted. Sometimes the file should be made available to the code execution / interpreter for further analysis. So to conclude, the feature request is: - Feature to enable / disable uploaded files be accessible to the pyodide or jupyter code execution / interpreter backend. - Feature to decide which file extensions are loaded in through the RAG / embedding system. - Feature to include entire document as context to the prompt. (instead of embedded & RAG-ed)

GiteaMirror closed this issue

2026-04-19 21:59:50 -05:00

GiteaMirror commented

2026-04-19 21:59:51 -05:00

@BK-HK commented on GitHub (Feb 21, 2025):

Agree! I am facing the same issue!!

Or simply break the "+upload document" into two menu items: "+upload document (RAG)" and "+upload document (Full)". Or model level enable/disable RAG

@BK-HK commented on GitHub (Feb 21, 2025): Agree! I am facing the same issue!! Or simply break the "+upload document" into two menu items: "+upload document (RAG)" and "+upload document (Full)". Or model level enable/disable RAG

GiteaMirror commented

2026-04-19 21:59:51 -05:00

@Capsar commented on GitHub (Feb 21, 2025):

That sounds like a good way of going about it, maybe it would then also be possible to include an option: "+upload document (Code)" for the code interpreter.

Again, I really appreciate all of the work you guys are doing @tjbck.

@Capsar commented on GitHub (Feb 21, 2025): That sounds like a good way of going about it, maybe it would then also be possible to include an option: "+upload document (Code)" for the code interpreter. Again, I really appreciate all of the work you guys are doing @tjbck.

GiteaMirror referenced this issue

2026-04-19 23:35:21 -05:00

[GH-ISSUE #15922] issue: Cannot update to version 0.6.18 using uv sync #17722

GiteaMirror referenced this issue

2026-04-25 07:09:56 -05:00

[GH-ISSUE #15922] issue: Cannot update to version 0.6.18 using uv sync #33251

GiteaMirror referenced this issue

2026-05-05 19:19:08 -05:00

[GH-ISSUE #15922] issue: Cannot update to version 0.6.18 using uv sync #56388

GiteaMirror referenced this issue

2026-05-13 04:20:58 -05:00

[GH-ISSUE #15922] issue: Cannot update to version 0.6.18 using uv sync #72326