Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2301] [FEAT]: Attach documents to messages #1501

New Issue
Closed
opened 2026-02-22 18:25:09 -05:00 by yindo · 8 comments
yindo commented 2026-02-22 18:25:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @blaineatnoeonai on GitHub (Sep 16, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2301

Originally assigned to: @timothycarambat on GitHub.

What would you like to see?

Currently, only administrators and managers can upload documents, and then those documents must be added to a workspace and accessed through RAG / pinning.

It would be good if users could upload attachments to messages. Attachments would be processed / OCRed and added to the context of the current conversation, but not added to the RAG system / made available to other users. This is a very common usage pattern, supported by ChatGPT, Claude, etc.

Originally created by @blaineatnoeonai on GitHub (Sep 16, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2301 Originally assigned to: @timothycarambat on GitHub. ### What would you like to see? Currently, only administrators and managers can upload documents, and then those documents must be added to a workspace and accessed through RAG / pinning. It would be good if users could upload attachments to messages. Attachments would be processed / OCRed and added to the context of the current conversation, but not added to the RAG system / made available to other users. This is a very common usage pattern, supported by ChatGPT, Claude, etc.
yindo added the enhancementfeature request labels 2026-02-22 18:25:09 -05:00
yindo closed this issue 2026-02-22 18:25:09 -05:00
yindo commented 2026-02-22 18:25:09 -05:00
Author
Owner
Copy Link
Copy Source

@petrusali commented on GitHub (Oct 5, 2024):

I'm asking for the same feature but too bad, my ticket got closed

@petrusali commented on GitHub (Oct 5, 2024): I'm asking for the same feature but too bad, my ticket got closed
yindo commented 2026-02-22 18:25:09 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 7, 2024):

@petrusali https://github.com/Mintplex-Labs/anything-llm/issues/2405
The issue was quite vague and ambiguous. If this issue is what you were asking we need a more verbose use-case and description as above.

We have to be pretty strict on pruning issues since a ton of people use GH issues for help/support or things get out of hand very fast for us.

@timothycarambat commented on GitHub (Oct 7, 2024): @petrusali https://github.com/Mintplex-Labs/anything-llm/issues/2405 The issue was quite vague and ambiguous. If this issue is what you were asking we need a more verbose use-case and description as above. We have to be pretty strict on pruning issues since a ton of people use GH issues for help/support or things get out of hand very fast for us.
yindo commented 2026-02-22 18:25:09 -05:00
Author
Owner
Copy Link
Copy Source

@manjotdhiman commented on GitHub (Jan 23, 2025):

@blaineatnoeonai Did you find workarounds for this ?

@manjotdhiman commented on GitHub (Jan 23, 2025): @blaineatnoeonai Did you find workarounds for this ?
yindo commented 2026-02-22 18:25:09 -05:00
Author
Owner
Copy Link
Copy Source

@blaineatnoeonai commented on GitHub (Jan 23, 2025):

I haven't found a workaround; we've been advising users to copy-paste document content into the message box in the mean time.

@blaineatnoeonai commented on GitHub (Jan 23, 2025): I haven't found a workaround; we've been advising users to copy-paste document content into the message box in the mean time.
yindo commented 2026-02-22 18:25:10 -05:00
Author
Owner
Copy Link
Copy Source

@manjotdhiman commented on GitHub (Jan 23, 2025):

What I am thinking is to Pin the docs which are currently dropped in the chat and unpin all other docs by doing some modifications

@manjotdhiman commented on GitHub (Jan 23, 2025): What I am thinking is to Pin the docs which are currently dropped in the chat and unpin all other docs by doing some modifications
yindo commented 2026-02-22 18:25:10 -05:00
Author
Owner
Copy Link
Copy Source

@scottybo commented on GitHub (May 7, 2025):

I've run into this issue today - a client was very confused about why the file they uploaded wasn't fully referenced by the AI modal being used.

I was surprised to see file uploads actually get embedded in the workspace, rather than just being "pinned" to the thread. It's an odd UX choice, as now a private file from a private thread has been embedded into the workspace and is available to all users of that workspace.

Related issues:

@scottybo commented on GitHub (May 7, 2025): I've run into this issue today - a client was very confused about why the file they uploaded wasn't fully referenced by the AI modal being used. I was surprised to see file uploads actually get embedded in the workspace, rather than just being "pinned" to the thread. It's an odd UX choice, as now a private file from a private thread has been embedded into the workspace and is available to all users of that workspace. Related issues: - https://github.com/Mintplex-Labs/anything-llm/issues/3347 - https://github.com/Mintplex-Labs/anything-llm/issues/1543 - https://github.com/Mintplex-Labs/anything-llm/issues/3287 - https://github.com/Mintplex-Labs/anything-llm/issues/3137
yindo commented 2026-02-22 18:25:10 -05:00
Author
Owner
Copy Link
Copy Source

@scottybo commented on GitHub (May 28, 2025):

Just adding some feedback to this one. I've got two fairly decent sized companies requesting this feature (each with about 30 users on the Docker version).

I'm getting inundated with questions about file uploads, and they tend to fall into two categories:

  • I can't upload files (they have the default permission, so aren't allowed to upload files to a workspace)
  • The AI isn't able to read the document (they expect the whole document to be kept in the context window, rather than a RAG lookup based on prompts)

I'm concerned that without the ability to simply upload a file to a chat thread, users will simply stop using AnythingLLM and revert back to big AI.

This is a real sticking point at the moment and could ultimately mean that people don't use the platform at all.

@scottybo commented on GitHub (May 28, 2025): Just adding some feedback to this one. I've got two fairly decent sized companies requesting this feature (each with about 30 users on the Docker version). I'm getting inundated with questions about file uploads, and they tend to fall into two categories: - I can't upload files (they have the default permission, so aren't allowed to upload files to a workspace) - The AI isn't able to read the document (they expect the whole document to be kept in the context window, rather than a RAG lookup based on prompts) I'm concerned that without the ability to simply upload a file to a chat thread, users will simply stop using AnythingLLM and revert back to big AI. This is a real sticking point at the moment and could ultimately mean that people don't use the platform at all.
yindo commented 2026-02-22 18:25:10 -05:00
Author
Owner
Copy Link
Copy Source

@blaineatnoeonai commented on GitHub (Jun 3, 2025):

We actually switched to Claude Enterprise a few months ago; the models were significantly better than anything we could run on-premise (enough to justify the privacy risks) and the UI was less flaky and more feature rich than any open-source UI we tried.

@blaineatnoeonai commented on GitHub (Jun 3, 2025): We actually switched to Claude Enterprise a few months ago; the models were significantly better than anything we could run on-premise (enough to justify the privacy risks) and the UI was less flaky and more feature rich than any open-source UI we tried.
yindo changed title from [FEAT]: Attach documents to messages to [GH-ISSUE #2301] [FEAT]: Attach documents to messages 2026-06-05 14:41:07 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1501
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?