Skip to content

Instantly share code, notes, and snippets.

@mickert
Last active January 25, 2026 11:26
Show Gist options
  • Select an option

  • Save mickert/2aaece29b97b917b29c249522776b12b to your computer and use it in GitHub Desktop.

Select an option

Save mickert/2aaece29b97b917b29c249522776b12b to your computer and use it in GitHub Desktop.
Feature request for Microsoft Copilot: add a simple "Archive Chat" or "Hide Chat" option to clean up the chat list without deleting conversations.

Table of Contents

  1. Problem Statement
  2. Current Limitations
  3. Why This Matters
  4. Proposed Solution
  5. Scope
  6. Non-Goals
  7. Rationale
  8. User Stories
  9. Acceptance Criteria
  10. Minimal Viable Implementation (MVP)
  11. Risks and Mitigations
  12. Future Enhancements

Problem Statement

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 Limitations

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.


Why This Matters

  • 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.

Proposed Solution

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.


Scope

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.


Non-Goals

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.


Rationale

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.


User Stories

  • 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.

Acceptance Criteria

The feature is considered successful when the following conditions are met:

  1. Users can archive or hide individual conversations using a clear UI action.
  2. Archived conversations move to a collapsed "Archived" section.
  3. Archived conversations remain fully accessible and can be opened without data loss.
  4. Search returns results from both active and archived conversations.
  5. No changes occur to memory, personalization, privacy, or retention behavior.
  6. The archive option is intuitive and does not clutter the UI.
  7. Users can unarchive conversations.
  8. The feature behaves consistently across supported platforms.

Minimal Viable Implementation (MVP)

The smallest version of this feature that delivers user value includes:

  1. An "Archive" or "Hide" option in the conversation options menu.
  2. A collapsed "Archived" section at the bottom of the chat list.
  3. Ability to open archived chats.
  4. Ability to unarchive chats.
  5. Archived chats remain searchable.
  6. No backend changes required; archiving is a UI-level state.
  7. Consistent behavior across platforms.

Risks and Mitigations

Risk 1: Users may confuse "Archive" with "Delete"

Mitigation: Clear labeling and tooltips.

Risk 2: Increased UI complexity

Mitigation: Place archive option inside existing menu; keep archived section collapsed.

Risk 3: Users may forget where archived chats are stored

Mitigation: Visible "Archived" header; search includes archived chats.

Risk 4: Cross-platform consistency challenges

Mitigation: Define minimal platform-agnostic behavior.

Risk 5: Misinterpretation as a privacy feature

Mitigation: Clarify that archiving is UI-only.


Future Enhancements

1. Custom folders or categories

Allow users to organize chats into folders such as Work, Personal, or Projects.

2. Automatic archiving rules

Examples:

  • Archive chats older than X days
  • Archive inactive chats
  • Archive chats marked as completed

3. Pinning conversations

Allow important chats to be pinned at the top.

4. Multi-select actions

Enable bulk archiving or unarchiving.

5. Keyboard shortcuts

Examples:

  • A to archive
  • U to unarchive
  • P to pin

6. Improved search filters

Examples:

  • Show only archived chats
  • Show only pinned chats

7. Syncing folder structure across devices

Ensure organization choices sync across platforms.

8. Bulk cleanup suggestions

Examples:

  • "You have 42 inactive chats. Archive them?"
  • "These chats have not been opened in 30 days."
@mickert

mickert commented Jan 25, 2026

Copy link
Copy Markdown
Author

Call to Action

If you support this feature request, please consider:

  1. Leaving a comment with your use case or why this would help your workflow.
  2. Sharing the Gist with others who rely on Copilot Chat.
  3. Upvoting or referencing this request in related discussions on GitHub, Reddit, or Feedback Hub.
  4. Linking to this Gist when discussing Copilot Chat UX improvements.

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment