Skip to content

Feature: Unarchive accidentally archived conversations #41070

Closed

Description

@lucascaro

Problem

There is currently no way to unarchive a conversation that was accidentally archived. Once a conversation is archived, it's effectively gone from the active list with no recovery path.

This is easy to trigger accidentally — a misclick or hasty action can archive an important conversation with no undo.

Proposed Solution

Add an "unarchive" capability so users can restore accidentally archived conversations. This could take several forms:

  • Undo toast: After archiving, show a brief "Undo" prompt (similar to Gmail's undo send) that lets the user immediately reverse the action
  • Archive view: A /archived command or menu that lists archived conversations and allows restoring them
  • Unarchive command: A /unarchive command that lists recently archived conversations for restoration

Alternatives Considered

  • Making archive require confirmation — adds friction to the happy path for every archive action
  • Making archive harder to trigger accidentally — still doesn't solve the problem once it happens

Additional Context

This is a quality-of-life improvement that reduces anxiety around the archive action. Users should feel confident that archiving is reversible.

Activity

  1. github-actions commented on Mar 30, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [FEATURE] Unarchive conversation feature request #41060
    2. [FEATURE] Unarchive Claude Code sessions in desktop app option #30869
    3. [BUG] Archived Code session cannot be unarchived - equivalent to permanent deletion #32018

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. github-actions commented on Apr 7, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  3. locked as resolved and limited conversation to collaborators on Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions