[Feature]: Archive enhancements

[bzbetty]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

My archive list is getting unmanagable.

• hard to find projects in the archive list when it's really long (they're sorted in order of adding, not alphabetically or anything)
• hard to find specific conversations for a project

Proposed solution

I would recommend making it a 2 tier list eg first pick project then conversation. make both lists search/filterable.

Generally i'm after recently archived conversations, so could also be something as simple as changing it to a flat list (not grouped by projects) and let me sort/filter it.

Why this matters

anyone who accidentally archives a conversation and has a long list (more users over time)

Smallest useful scope

filter at the top of the list to let me filter to a specific project

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[Pearcekieser]

+1 - also and option to sort by last archive date be great those recently archived convos could be right at the top of the list

[OliverGamborg]

I already made a PR to fix some of these concerns
#2758

[lastobelus]

I opened #7282 to address the "smallest useful scope"

It adds a Archive / Project breadcrumb at the top, similar to the project settings breadcrumb, where Project defaults to All, and is a dropdown that let's you choose an individual project.

[OffCrazyFreak]

Adding my use case. I keep a lot of threads in the archive and go back to them often, so for me it is where I find old work, not a legacy feature. With five projects the page is one long flat list and the project I want is usually at the bottom, so I scroll past everything every time.

What would help most: keep the grouping by project, but make each project a collapsed section by default with a small open/close animation, so the page starts as a short list of project headers and I expand only the one I need. The project crumb from #10639 helps, and #7387 looks close to this. Happy to test a build or a PR.

[lastobelus]

Update: the smallest requested scope—filtering the archive by project—is now supported by #10639. In Settings → Archive, use the All projects picker in the header to select a project; the environment picker can narrow it further. Choosing All projects clears the project filter.

I tried this in stock T3 Code and prefer the shared upstream implementation, so I closed #7282 as superseded. Its custom archive picker and filtering code are no longer needed.

This addresses the project-filtering part of this discussion; it does not claim to implement all the broader search, sorting, or two-tier navigation suggestions.

[Quicksaver]

I've built this in my fork, on top of the project filter from #10639. The PR (#12708) was closed pending maintainer approval of direction and scope, so I'd like to propose it here.

Interactive demo: https://quicksaver-piz.vercel.app/t3code/archive-settings-ux

What it does (web, desktop and mobile)

• Archived threads are grouped by project, each group collapsed by default, with project icons and environment labels.
• Search across archived titles, with results ranked when the query has several words.
• Sort by archived date or created date.
• Restore or delete a single thread (hover or keyboard focus on web, swipe or long-press on mobile). A project group can also restore or delete the threads matching the current search, with a confirmation and a report of any partial failures. This covers the bulk cleanup asked for in [Feature]: Bulk delete archived threads #6927.
• Archive loads every configured environment, including ones without active projects. An environment that fails to load shows an error with a retry button.

Scope I'm asking approval for: the grouping, search and sorting, plus project-level restore/delete. If that's too much at once, I can split it: grouping, search and sorting first, then the project-level actions as a follow-up, although I feel together they are a very intuitive match.