Currently, when a conversation is moved into a Project, it can continue to appear in the main Recents list based on recent activity.
For users who rely on Projects to organize a large number of conversations, this can quickly clutter the Recents list and make active conversations harder to find.
Rather than requiring the same behavior for every conversation, I would like to suggest two options when moving a conversation:
1. Move to Project
Move the conversation to the selected Project while allowing it to remain visible in Recents.
2. Move to Project + Remove from Recents
Move the conversation to the selected Project and remove it from the main Recents list. The conversation would remain fully accessible inside the Project.
This would be especially useful for workflows involving research, client work, project management, testing, or any other work that generates a large number of individual conversations. Once those conversations have been organized into their appropriate Projects, having all of them continue to appear in Recents can make it harder to locate other active conversations.
Previously, moving conversations into Projects kept them from appearing in the main Recents list. The newer activity-based Recents behavior may work well for some users, so I am not suggesting that the previous behavior simply replace the current one.
Giving users both options would preserve the current behavior while restoring the ability to use Projects to declutter Recents.
This would provide conversation-level control, since a user may want some Project conversations to remain in Recents while removing others.
