[ChatGPT] Add filters for bulk chat management by age and project membership
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What feature would you like to see?
Please add filtering and bulk actions for ChatGPT conversation history, especially by conversation age and Project membership.
A common cleanup workflow is:
Archive or delete chats older than a certain date, but only if they are not inside a Project.
Today, ChatGPT supports acting on one conversation at a time, or using broad actions such as Archive all chats. That makes cleanup difficult for users who want to preserve Project conversations while clearing older standalone chats.
Requested behavior
Add filters to the chat/history management UI such as:
- Project membership
- In a Project
- Not in any Project
- Specific Project
- Age / last activity
- Older than 7 days / 30 days / 90 days
- Before a custom date
- Optional additional filters such as archived state or pinned state
Then allow bulk actions on the filtered result set:
- Archive selected / filtered chats
- Delete selected / filtered chats
- Select all matching chats
- Show a confirmation with the number of affected conversations
Example workflow
- Open chat history management.
- Filter:
Not in any Project. - Filter:
Older than 30 days. - Select all matching chats.
- Choose
ArchiveorDelete.
Project conversations should remain untouched.
Why this matters
Users with a large chat history often use Projects as the boundary between conversations that should be retained long-term and ordinary standalone chats that can be cleaned up later.
The current all-or-nothing bulk controls are too coarse, while managing old conversations one by one does not scale.
This would make ChatGPT history management significantly safer and more practical, especially for users with hundreds or thousands of conversations.
Related issue
- #41052 — requests multi-select / selective bulk archive for ChatGPT chats.
This request is more specifically about filtering by age and Project membership before applying bulk archive/delete actions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking whether this repository contains the ChatGPT conversation-history UI described in the issue; the payload names no files, tests, or entry points. Review related issue #41052 and determine the product scope before implementation. Done would require age and Project-membership filters, safe bulk archive/delete actions, and confirmation that Project conversations remain untouched.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100