[FEATURE] Organize sessions into folders/groups in the recents list

Open 💬 1 comment Opened Jul 4, 2026 by miguexis

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

I use Claude Code as an ongoing operations hub for a small business (a pizzeria), not just for coding. I run many separate chat sessions covering different areas — marketing campaigns, pricing/margin analysis, ad creative, customer segmentation — all within the same project folder.

Over weeks, the "recents" list fills up with dozens of sessions on unrelated topics, and it becomes hard to find a specific past conversation. There's currently no way to visually group related sessions together.

Proposed Solution

I'd like to be able to create folders/groups within the sessions list (e.g. "Marketing," "Pricing," "Client X") and move existing sessions into them. Groups could be collapsed/expanded to keep the recents list clean, similar to how folders work in note-taking or email apps.

Alternative Solutions

Right now the only options are keeping a session in the flat recents list or archiving it entirely. Archiving removes it from view, which isn't the same as organizing — I still want related sessions visible and grouped, just not mixed with everything else.

Priority

Low - Nice to have

Feature Category

Interactive mode (TUI)

Use Case Example

Example scenario:

  1. I manage a pizzeria's operations entirely through Claude Code — marketing, pricing, customer data, all in one project.
  2. Over a month I create 15+ sessions: coupon campaigns, price calculators, ad creative, etc.
  3. With this feature, I could group them into folders like "Marketing," "Finance," and "Campaigns."
  4. This would save time when I need to find a past conversation about a specific topic, instead of scrolling through a long unsorted list.

Additional Context

This would be especially valuable for non-developer users running Claude Code as a general business assistant across multiple ongoing workstreams.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗