LibreChat
LibreChat copied to clipboard
danny-avila
Enhancement: Organization of chats into folders and/or "projects"
What features would you like to see added?
I would love to see two related features:
- The ability to group chats and conversations into folders. Call this "basic" organization.
- The ability to have a special type of folder called "projects". In addition to simply being an organizational tool, it would allow you to have shared context such as files (or a selection of specific files already uploaded and indexed by the RAG system) as well as a shared system prompt or context.
I go into greater detail below as I have a specific vision in mind. As someone who is a heavy .NET IDE user, I think in "solutions", folders, and projects - so what I'm describing is just my current mental model. Could this be accomplished in other ways? Perhaps. I know I need to start leveraging the existing bookmark and RAG system much more, and I will try to do so in the upcoming days. I'm open to alternative approaches so long as they capture the essence of what I'd like to see.
More details
Folders / Groups
Other open web UIs have the ability to organize conversations into folders. This would be an extremely useful feature to have as I tend to start many conversations on related topics. I also retain my chat history, so finding a previous conversation by date is starting to get challenging. Search helps, but sometimes I'd rather just see everything that I think is related be in one spot.
For basic folder management, I would expect:
- Button / toggle in main conversation list to switch between current by-date organization and folder view (P1)
- Move conversations from one folder to another (P1)
- Rename / delete folders (P1)
- On delete, should conversations be deleted, moved to parent, or moved to root/global? (P2)
- Multiple levels of nesting (P2)
- Share / export entire folder (P3)
I see #3021 that essentially covers this feature. I'm happy to see this request scoped to the second part, Projects. But I mention both because I think they could actually blend together and augment each other.
Projects
I would love to see something similar to Claude's project system. I see #4730 that talks about groups and workspaces - but that seems to focus more on the team and collaboration aspects.
To me, a "project" is a special kind of folder that has shared context built in. A project could be as simple as a shared system or context prompt. But I think it would also make sense for it to share selected files from the RAG system and to also potentially share generated artifacts.
Call me crazy, but I think projects could/should also support nesting - where context is additive (i.e. additional files, prompts).
For example, a project structure could be:
- LibreChat (includes main developer documentation as context)
- Front-end (includes additional documentation and context related to front end. May include system prompt stating that XYZ libraries are used and a certain style should be followed)
- Back-end (ditto)
So, I would expect:
- Project rename / delete (P1)
- Shared system / user prompt (P1)
- Shared files from the RAG database (P1)
- Select which specific files to use (P2)
- Shared artifacts (P2)
- Nested projects (P3)
Combining folders and projects
Here is why I consider these features related: I think folders should be allowed to contain projects and vice versa.
Example of folders containing projects: "Personal projects", "React projects", ".NET projects" - and these are simply groupings of related projects.
Example of projects containing folders: Perhaps I don't need the extra overhead and context for a certain feature to warrant a new sub-project. I just want to create a folder underneath "Front-end" - to use the above example - where I collect all of my conversations about one thing.
This is definitely a "nice-to-have" feature. But I could envision an implementation where mixing and matching projects and folders in a hierarchy isn't a complete implementation and UX nightmare.
I recognize as a whole, this is likely a lot of work and effort. I'd love to support in any way I can.
Which components are impacted by your request?
General, UI
Pictures
No response
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
+1 love this idea! I use Claude Projects at work, it's a game changer for shared context across multiple chats.
The biggest downside to the Claude implementation is the limited size of document context you can add to the project. If LibreChat could provide access to larger sets of documents in project context, it would be a huge advantage.
Would like to echo the idea of Claude Projects! The document context for me is really limited but Projects is incredibly useful for a range of research work.
This is what I want when comparing LibreChat to the Claude chat interface! I am looking forward to using this feature soon.
This is the exact feature that I want in LibreChat as well, Claude style project management will be so good
I came from OpenWebUI due to the other features such as MCP and agents.
First thing I looked for was folders. Even basic chat in folder would be amazing.
@craftyshaun thanks, this is duly noted and will be part of the 2025 roadmap. It's worth noting that we have "bookmarks," which are functionally similar to organizing folders in a basic way.
The proposed usage in this issue is good, and would clearly differentiate it from bookmarks.
Thanks @danny-avila, I appreciate the consideration. I started using the bookmark feature after coming across it in other related enhancement requests. It's basic, like you say, but is certainly helping me keep things better organized.
@danny-avila what would you need to see in a PR for this? I'm interested in contributing to build this feature.
@danny-avila what would you need to see in a PR for this? I'm interested in contributing to build this feature.
Agreed.
This would be excellent and is really important for a team environment where you have different departments or different special areas of work and you want to set up a kind of pre-configured workspace for users so they have all the tools that prompts the data they need at hand. The way the app called anythingLLM does this is a good example of part of this concept it doesn't extend to the full settings but it does let you have a set of documents or sets of documents in the rag for just that workspace so effective you can make a knowledge base that's contained to that workspace. I thought was quite a good feature.
Agreed. Very helpful feature. I have some renderings from Figma that I created some time ago. More than happy to contribute.
Do you want to collaborate on this?
I can share my Figma and concepts, and I have also begun researching some OS libraries that could be used with React.
Hi guys, any updates on this? I'd love to collaborate on this feature if possible.
For the love of everything that's holy, guys, please don't comment "+1". I'm following this issue to hear when there are any updates, not to be spammed by your +1s. Leave an emoji on the main post if you wish to show your interest.
On topic: I'm also willing to contribute to make this happen. I know very little about AI though, so I imagine this would need the lead of someone who knows how to put this together.
Would also love this. To be honest, its the only thing keeping me on Open-Webui.
For the love of everything that's holy, guys, please don't comment "+1". I'm following this issue to hear when there are any updates, not to be spammed by your +1s. Leave an emoji on the main post if you wish to show your interest.
On topic: I'm also willing to contribute to make this happen. I know very little about AI though, so I imagine this would need the lead of someone who knows how to put this together.
On the contrary, I love seeing the +1s...it helps boost visibility and draw attention to the issue. I’m more than happy to be “annoyed.” My take: have at it, plus-one people!
+1
Everyone who is interested on this functionality. We are building it as well. DM me.
ᐧ
On Thu, Oct 9, 2025 at 3:44 PM Jakub @.***> wrote:
ableitung left a comment (danny-avila/LibreChat#4848) https://github.com/danny-avila/LibreChat/issues/4848#issuecomment-3387267785
This exactly. It would be a great improvement for studying.
— Reply to this email directly, view it on GitHub https://github.com/danny-avila/LibreChat/issues/4848#issuecomment-3387267785, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGFKMSU752UOWKK7OFBWOX33W23JPAVCNFSM6AAAAABS6AZO2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBXGI3DONZYGU . You are receiving this because you commented.Message ID: @.***>
We also see this request often. Additionally - we currently enforce a 30-day retention lifecycle for messages/conversations/files in MongoDB, but it would be great to consider per-folder / per-project retention as a stretch goal e.g. per-project TTL overrides, archive/export workflows or a “pinned/never-expire” toggle. That would let teams preserve important contexts without changing the global lifecycle policy.
We also see this request often. Additionally - we currently enforce a 30-day retention lifecycle for messages/conversations/files in MongoDB, but it would be great to consider per-folder / per-project retention as a stretch goal e.g. per-project TTL overrides, archive/export workflows or a “pinned/never-expire” toggle. That would let teams preserve important contexts without changing the global lifecycle policy.
Can I ask how do you enforce this? Do you have a script that directly deletes in the database all messages, conversations and files older than 30 days? If you do could you share it?
I think that by now almost all competing solutions - TypingMind, AnythingLLM have this, so it would be so nice to have LibreChat have it too. I'm new to LibreChat having tried several of the others and like many things in LibreChat, for me and our organization the lack of "Projects" is the biggest gap as we can't have Marketing, Finance etc. have their own, shared areas at the moment. I really hope we will see this in LibreChat.
Yes, folders and project-based thread grouping would be a stunning feature as ungrouped thread lists become a little tricky to navigate effectively. Still love the platform, so thanks to the team!
