[FEATURE] Group Claude Code sessions into folders that mirror project directories (like Codex) #60954

Preflight Checklist

• I have searched existing requests
• This is a single feature request (not multiple features)

Problem Statement

The Claude Code session list in the Desktop app is flat and chronological. There is no way to group sessions by the project they belong to.

I work across several separate projects on one machine. Each project already lives in its own folder on the filesystem. That separation exists today, but the app does not reflect it. Every session from every project lands in one shared list, sorted only by time. When I switch between projects I have to scan timestamps and guess which session belonged to which project.

This gets worse as the number of sessions grows. With sessions spread across multiple project directories, finding the right one means scrolling, searching by remembered keywords, or relying on manual renames.

Proposed Solution

Make the left pane reflect the existing filesystem project structure automatically.

• Group sessions by their working directory or git root.
• Show each project as a collapsible folder in the sidebar.
• Nest that project's sessions under its folder.
• Sort projects by most recent activity.

This is exactly how Codex works today: agents are organized by project, so you switch between projects without losing track of which session is which. It is the natural mental model for anyone working across multiple codebases or contexts.

Important distinction: this is not a request for arbitrary, manually created folders. The folders should be derived from where each session actually runs on disk. No manual filing. The projects are already separated in the filesystem, so the app just needs to surface that grouping.

Example:

RISM-Vault (4 sessions)
    Context load
    Backlink pass
    Blog draft
    Note analysis

RISM-Mac (2 sessions)
    Move To picker
    Bug 164 follow-up

GentleProgress (1 session)
    Task routing

Alternative Solutions

• Renaming sessions with project prefixes. Manual and clutters names.
• One terminal or window per project. Heavyweight, no unified view.
• Search. Requires remembering keywords and does not give an at-a-glance overview.

None of these scale once you have many sessions across several projects.

Priority

High. This is a daily friction point for anyone running multiple projects on one machine.

Feature Category

Interactive mode (TUI)

Use Case Example

1. I open the Desktop app and see my projects listed as folders, each matching a directory on my Mac.
2. I expand the project I want to work on.
3. Its sessions are right there, grouped, so I pick up where I left off without scanning a flat list.
4. Switching to a different project is one click on a different folder.

Additional Context

Issue #22617 proposed the same automatic project grouping months ago and is still open with no maintainer response. Filing this to surface continued demand. Project detection can use the git root or the working directory. Sessions without a git repo can group under their directory name. Worktree sessions could nest under their parent repo. Syncing the grouping across Desktop, CLI, and Web would be a bonus.