[ChatGPT Web] Add multi-select / selective bulk archive for chats
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What feature would you like to see?
ChatGPT Web should support selecting multiple conversations and archiving them in one operation.
Current behavior
ChatGPT currently supports:
- Archiving one conversation at a time.
- Archiving all conversations from Data Controls.
There is no supported way to archive an arbitrary subset of conversations in bulk.
For users with hundreds or thousands of conversations, individually archiving old chats is impractical, while Archive all chats is too destructive as an organizational tool.
Requested behavior
Add multi-select to the chat/history interface, with at least:
- Select multiple chats.
- Archive selected.
- Select all currently visible/filtered chats.
- Clear confirmation showing how many chats will be archived.
Useful follow-ups could include filtering by age, project, pinned/starred state, or last activity before selecting chats.
Why this matters
The underlying archive capability already exists; the missing piece is bulk selection.
Without a supported selective bulk operation, power users are pushed toward browser automation or undocumented internal ChatGPT APIs to manage large histories. A first-party bulk archive UI would be safer, more reliable, and avoid users having to automate unsupported endpoints.
This request is specifically for ordinary ChatGPT conversations, including ChatGPT Web, rather than Codex-local session management.
Related
- #32070 — related batch/automatic archiving request for Codex sessions.
- #37791 — broader request for bulk organization in the unified desktop app.
This request is narrower: first-class selective bulk archiving of ordinary ChatGPT conversations.
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
The issue names no files, tests, or entry points, and requests a ChatGPT Web feature in the codex repository. First confirm whether this repository owns the chat/history interface; done would include selecting visible chats, archiving the selection, clearing the selection, and confirming the number of chats affected.
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
- 25/100