[FEATURE] Starred & Recents Roll-up

Resolved 💬 2 comments Opened May 13, 2026 by reneessance Closed Jun 13, 2026

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

We work with a million different chats every day that are "RECENT" or "STARRED". When I go to find a single chat, it takes more time than the chat does. Yes, we have SEARCH, but I have a different feature request for that. This is a simple request for a roll-up feature for the "RECENT" and "STARRED" sections in the sidebar that would make so many lives better when working with a million chats in Claude. This is a quality-of-life request.

Proposed Solution

I am mobile-first and a non-linear thinker, both of which are relevant to this request.
Please add a "roll-up feature" for the "STARRED" and "RECENT" chat sections in the left sidebar.
Your one addition of this feature would save us so much time!

Alternative Solutions

Can we please have a way to move away from or provide an alternative to linear lists, scrolling lists, and use a node-based interface instead - map me a network or mindmap of my chats? OK, I'll admit this one isn't tricky to do, but it may be tricky to use on mobile
And for those where that solution may annoy them
How about an option to choose linear with a carrot to roll up if you want, or a setting where you choose the option you want - node/network map or linear?

These aren't original ideas, but they are certainly better than nothing at all. Just eternal scrolling to find my chat........
Because well, Claude "SEARCH" I'll submit that separately.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Look at the number of chats in your left sidebar. I know I'm not the only one with this challenge. Seeing them all (even the ones I haven't deleted yet - and so do you) at once is overwhelming and distracting from real work.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗