Feature request for product/service
Cursor IDE
Describe the request
I’d like to be able to create a “project” or “group” for my chats, making them easier to find and organize.
Hey, thanks for the feature request.
This isn’t the first request about organizing chats. There’s a similar thread about folders for agent chats. The navigation issue with a growing chat list is definitely real.
There’s also a related request about sorting by last updated. That’s also about making it easier to find the right chats.
The team is aware of these requests. If you have any specific use cases or details on how you’d like grouping to work (tags, folders, projects), feel free to add them to the thread. It’ll help us as we think through the feature.
1 Like
Not sure how best to solve this, but I’m feeling this pain. Most of my feature builds require several chats for context management, and I’m handling maybe 3-4 per project at any one time - so 10-20 chats per repo that I’m actively working on. I’m leaving and coming back to these over the days and weeks and it’s always hard to get situated and figure out which chats are relevant to what I want to do. This is exasperated by the need to remember to manually name each chat with a task Id to easily identify them. I’d love it if the agent intelligently suggested chat names based on ongoing convos - not just the initial chat.
1 Like
Hey @Alex_Chapman, good addition. Having 10 to 20 active chats per repo is really a lot, and the idea of automatically suggesting names based on the full conversation context, not just the first message, makes sense.
The team is aware of the request. Similar discussions about folders and sorting were already mentioned in the thread. Your case adds useful detail. It is not only about grouping, but also the pain of manually naming a large number of chats.
If you have more details on how you imagine auto naming working, like when in the chat it should suggest a name, or whether it should automatically rename when the topic changes, feel free to add that to the thread. It will help when we work on the feature.