Allow grouping sessions into folders/collections (Projects-style organization)
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 a single project involves many long-running sessions — for example migrating a
large legacy codebase step by step, with one session per step — all those threads pile
up under one project with no further structure. There is no way to keep related or
parallel threads grouped together, so finding the right one gets harder as the list
grows. Renaming, archiving and filtering help, but there is no real grouping. Tools like
ChatGPT solve this with "Projects" (folders that hold related chats), which makes
navigating many related conversations much easier.
Proposed Solution
Let users create folders/collections to group sessions, independent of the working
directory (ideally nestable). I'd like to create a folder (e.g. "Migration – step by
step"), move related sessions into it, collapse/expand it in the sidebar, and have it
persist. This would complement the existing "group by project" toggle, not replace it.
Alternative Solutions
Currently I rename sessions descriptively, archive finished ones, and use the
"group by project" toggle and status filters. It helps but does not actually group
related active threads. ChatGPT's Projects feature solves this with user-created folders.
Priority
Low - Nice to have
Feature Category
Other
Use Case Example
_No response_
Additional Context
_No response_
5 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1 — I'd love nested groups in the sidebar. My concrete use case: I have a top-level "YouTubeShorts" group and want to nest related sessions (e.g. an idea-mining pipeline, a rendering pipeline, an upload pipeline) underneath it as children, rather than having them all sit flat in the same group or scattered across separate groups. Collapsible, nestable folders would make managing multi-session projects far more practical.
Another use case here, multi brand operation. I run ~12 projects in Claude Code across a fragrance store, a film review site, a finance OS, a handful of trading agents, plus system tools. Each brand owns 5 to 15 working dirs and the sidebar has become a flat sprawl. Manual naming conventions like ca_console and ca_agents are the only thing keeping it sane.
What would actually unlock this:
The "ideally nestable" phrasing in the original ask is the missing piece. Without nesting, sidebar grouping flattens at the first level and the same scaling problem recurs.
+1.
I have the same problem as @bigbamwolf where I have to manually rename conversations to identify projects and types (BUG/FEAT/ etc.). The conversation filter is nice and working, but after filtering, there is no visual aid or indicator showing what has been filtered, unless I press the filter icon. That's why I manually rename the conversation, to serve a visual aid, which should be a feature Claude Code has.
+1 for folders/collections. (Edit: an earlier version of this comment asked for automatic grouping by working directory — turns out that already exists via the sidebar's "Group by: Project" view, so this issue's manual-organization ask is the part that remains.)