mirror of
https://github.com/Mintplex-Labs/anything-llm.git
synced 2026-03-02 22:57:05 -05:00
[FEAT]: Memory Management UI/UX #3084
Labels
No 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
question
stage: specifications
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anything-llm#3084
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @timothycarambat on GitHub (Jan 9, 2026).
What would you like to see?
As a user, It would be nice if I could add "memories" to a workspace chat that is also user-specific. These memories can be dynamically created via the RAG memory tool and be visible and managed via the UI by a user.
The RAG and memory tool should likely be split into two tools now since they are two distinct processes with the inclusion of this feature.
@kellyelton commented on GitHub (Jan 10, 2026):
funny, I just stumbled across this project today and was wondering about memory support, kind of critical to what I was hoping to use it for.
I'm glad to see you guys are working on it!
@geheimniskonto commented on GitHub (Jan 12, 2026):
To be honest it is not much of an assistant without persistent memory. Who hires office help that forgets things and has to relearn them every time you meet them...
@ender3 commented on GitHub (Jan 29, 2026):
Agreed that RAG and memory tool should be separate, if only for the reason that it is not intuitive to many users that they can add a MEMORIES.md file to the RAG document collection to simulate this feature. Being able to CRUD memories from within the UI would be ideal. In the simplest possible implementation, a table that simply associated name value pairs would be a huge step in the right direction.
For example:
user name: Fred McFredson
user preferred name: Fred
user occupation: Political advocate for people named Fred
agent preferred tone: professional, concise, non-sycophant
user location: Fredsville, Nebraska
and so on. Being able to manipulate these "memories" individually and having the changes reflected immediately in the workspace would be highly desirable.