[FEATURE] Bring back grouping by date at the top level

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 14, 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

Today when I opened Claude Desktop the sidebar UI seems to have changed to match the feature requested in https://github.com/anthropics/claude-code/issues/101307. Specifically it seems to be organized by section and each section now has options within it to group by date, status, etc.

This is nice! However, sometimes its really useful to be able to group by date at the top level - basically so I can see everything that I've been working on recently (which may be in different sections) near the top. In my working style I would prefer to be able to toggle between those - seeing my work organized by functional area (eg section) and by date. But there doesn't seem to be a control for switching what the top-level grouping is - at least I can't find it - it seems like the top-level grouping is now fixed to be by section.

Proposed Solution

Please bring back the top-level grouping control. It would be great to have both - a top-level grouping control that determines whether the top-level grouping is by section, date, status, etc. then for each section a control for determining how it's sub-grouped.

Alternative Solutions

I haven't thought of any yet. One option I guess is using "pinned" section to keep track of what I am currently working on, but that feels like more of a hassle.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

As I am working and switching between active tasks, I prefer the top-level grouping to be by date, so my active tasks are near the top. When I am reviewing the overall state of work from more of a "30,000 ft" view or deciding on what to start next, I prefer the top-level grouping to be by section.

Additional Context

_No response_

View original on GitHub ↗