- Status: Public feature request
- Scope: Microsoft Copilot (Chat UI - copilot.microsoft.com)
- Type: UX improvement
- Requestor: Michel Sijmons (https://mickert.dev)
- Source: https://gists.mickert.dev/2aaece29b97b917b29c249522776b12b#file-copilot-feature-request-archive-chat-md
- Problem Statement
- Current Limitations
- Why This Matters
- Proposed Solution
- Scope
- Non-Goals
- Rationale
- User Stories
- Acceptance Criteria
- Minimal Viable Implementation (MVP)
- Risks and Mitigations
- Future Enhancements
Copilot users often create many short, task-focused conversations throughout the day. These chats accumulate quickly and clutter the chat list, making it harder to locate important or long-running threads. At the moment, there is no lightweight way to clean up the chat list without deleting conversations entirely.
Current options are limited to:
- Deleting a conversation, which is too destructive if the user might need it later.
- Disabling chat history entirely, which is not practical for most users.
There is no simple way to hide or archive chats while keeping them accessible.
- Reduces clutter for users who generate many short-lived chats.
- Keeps important or ongoing conversations easy to find.
- Matches common UX patterns found in modern productivity and messaging tools.
- Improves day-to-day usability without affecting privacy or retention policies.
- Provides a high-impact quality-of-life improvement with minimal UI changes.
Add a simple "Archive" or "Hide" option to each conversation. Archived chats move to a separate, collapsed section at the bottom of the chat list. They remain searchable and can be restored at any time.
This solution is lightweight, intuitive, and requires no backend changes.
This feature request applies specifically to the Copilot chat interface across supported platforms.
The scope includes:
- Adding a UI option to archive or hide individual conversations.
- Providing a collapsed "Archived" section where archived chats are stored.
- Ensuring archived chats remain searchable.
- Keeping the implementation lightweight and UI-focused.
This proposal does not require changes to backend systems, privacy models, or data retention behavior.
This feature request does not aim to change or affect the following:
- No changes to Copilot memory behavior or personalization logic.
- No changes to data retention, privacy policies, or storage mechanisms.
- No export, backup, or long-term archival system for conversations.
- No modifications to how search, indexing, or chat history sync works.
- No redesign of the chat UI beyond adding a simple archive or hide option.
- No impact on how conversations are processed or analyzed.
The goal is strictly limited to adding a lightweight UI option for organizing conversations.
Copilot is used for both short, one-off tasks and long-running conversations. Without an archive option, the chat list becomes cluttered and difficult to navigate. A simple archive or hide feature aligns with common UX patterns and provides immediate usability improvements.
The feature requires minimal UI changes, introduces no backend complexity, and benefits a wide range of users, especially those who rely on Copilot heavily throughout the day.
- As a user who creates many short-lived chats, I want to archive or hide conversations so that my chat list stays clean and manageable.
- As a user who works on long-term projects, I want to keep important conversations visible while moving older or irrelevant chats out of the way.
- As a user who does not want to delete conversations, I want a non-destructive way to remove them from the main view without losing access.
- As a user who searches for past information, I want archived chats to remain searchable so I can still find them when needed.
- As a user who values a simple interface, I want the archive option to be lightweight and easy to use without adding complexity.
The feature is considered successful when the following conditions are met:
- Users can archive or hide individual conversations using a clear UI action.
- Archived conversations move to a collapsed "Archived" section.
- Archived conversations remain fully accessible and can be opened without data loss.
- Search returns results from both active and archived conversations.
- No changes occur to memory, personalization, privacy, or retention behavior.
- The archive option is intuitive and does not clutter the UI.
- Users can unarchive conversations.
- The feature behaves consistently across supported platforms.
The smallest version of this feature that delivers user value includes:
- An "Archive" or "Hide" option in the conversation options menu.
- A collapsed "Archived" section at the bottom of the chat list.
- Ability to open archived chats.
- Ability to unarchive chats.
- Archived chats remain searchable.
- No backend changes required; archiving is a UI-level state.
- Consistent behavior across platforms.
Mitigation: Clear labeling and tooltips.
Mitigation: Place archive option inside existing menu; keep archived section collapsed.
Mitigation: Visible "Archived" header; search includes archived chats.
Mitigation: Define minimal platform-agnostic behavior.
Mitigation: Clarify that archiving is UI-only.
Allow users to organize chats into folders such as Work, Personal, or Projects.
Examples:
- Archive chats older than X days
- Archive inactive chats
- Archive chats marked as completed
Allow important chats to be pinned at the top.
Enable bulk archiving or unarchiving.
Examples:
- A to archive
- U to unarchive
- P to pin
Examples:
- Show only archived chats
- Show only pinned chats
Ensure organization choices sync across platforms.
Examples:
- "You have 42 inactive chats. Archive them?"
- "These chats have not been opened in 30 days."
Call to Action
If you support this feature request, please consider:
Your feedback helps demonstrate real-world demand and strengthens the case for implementation.
Canonical link:
https://gists.mickert.dev/2aaece29b97b917b29c249522776b12b#file-copilot-feature-request-archive-chat-md
Support My Work
If this Gist helped you — saved you time or money, solved a problem, or taught you something — consider supporting my work:
• Explore my work (Gists + GitHub projects) and maybe drop a ⭐ or follow
https://gists.mickert.dev/ • https://github.mickert.dev/
• Support my work on Ko-fi
https://support.mickert.dev
Thanks for reading!