[FEATURE] Allow archiving chats within a Project

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When working with Projects, I often accumulate chats that are no longer active or relevant to my current work, but that I still want to keep for future reference.

At the moment, the only way to remove these chats from the Project's chat list is to delete them. This creates a difficult choice: either keep old conversations visible indefinitely, which makes it harder to find and focus on active chats, or delete conversations that may still contain useful information and that I may want to revisit later.

My workflow would benefit from being able to distinguish between chats that I no longer need to see regularly and chats that I no longer need at all. The current behavior does not provide a way to make that distinction without permanently deleting the conversation.

Proposed Solution

Add an "Archive" option to chats within Projects, alongside the existing "Delete" option.

When a chat is archived:

It should be removed from the main chat list within the Project, so the Project stays focused on active conversations.

The chat and all of its contents should remain preserved and accessible.

Archived chats should be available from an "Archived chats" section within the Project.

Users should be able to open an archived chat and unarchive it, returning it to the main Project chat list.

Archiving should not remove the chat from the Project or affect its contents, context, or attachments.

The interaction could follow the same pattern as the existing chat archive functionality outside of Projects, so the behavior feels consistent across Claude.

The key distinction would be:

Archive: hide the chat from the active Project chat list while keeping it available.

Delete: permanently remove the chat.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_