[FEATURE] FleetView sidebar: option to group sessions by working directory instead of by inner project/solution file name.

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

The current "Group by project" option groups sessions by the project
or solution file name found inside the folder. This collapses multiple
parallel checkouts of the same repository into a single group, because
they share the same project name.

Example workflow:
C:\DEV\repo\ERP_3 (main checkout)
C:\DEV\repo\ERP_3_agent_2 (parallel agent worktree)
C:\DEV\repo\ERP_3_agent_3 (another parallel agent worktree)

All contain ERP.sln, so the sidebar shows them under one "ERP" group
and there is no way to tell which session belongs to which folder.

Meanwhile, ~/.claude/projects/ already stores each folder under its
own normalized key (c--DEV-repo-ERP-3, C--DEV-repo-ERP-3-agent-2,
etc.) — the data needed to distinguish them is already there.

<img width="539" height="630" alt="Image" src="https://github.com/user-attachments/assets/fb167485-6553-4aeb-b58a-91e94aac0d68" />

<img width="316" height="386" alt="Image" src="https://github.com/user-attachments/assets/e40294b5-d511-451b-9a7d-02e0d94d6c2b" />

Claude 1.8089.1 (b98a06) 2026-05-19T18:28:48.000Z

Proposed Solution

Any of the following would solve the problem:

1. Make "Group by project" key off the normalized working-directory

path (same key as ~/.claude/projects/) instead of the inner
project file name.

1. Add a separate option "Group by folder" / "Group by working

directory" alongside the existing one.

1. Allow a flat / no-grouping mode.

Option 2 is the most flexible — keeps existing behavior for users
who like it, and adds a working-directory mode for users with
multiple parallel checkouts.

Alternative Solutions

• I've tried renaming the folders to make their names more distinct,

but this breaks the ~/.claude/projects/ keys and loses session
history for those folders.

• Currently I work around this by remembering which session was

started from which folder, since the sidebar group label alone
doesn't tell me. With 3+ parallel checkouts this is error-prone.

• Other editors / multiplexers (VS Code, tmux session managers, etc.)

key off the working directory path, so different folders with the
same project file are shown as distinct entries. Same approach
would work here — the data is already in ~/.claude/projects/.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

Example scenario:

1. I'm working on a large ERP project in C:\DEV\repo\ERP_3.

1. I create two parallel agent worktrees of the same repo for

independent tasks:
C:\DEV\repo\ERP_3_agent_2 (refactoring branch)
C:\DEV\repo\ERP_3_agent_3 (bug-fix branch)
All three folders contain ERP.sln.

1. I open a Claude Code session in each of the three folders and

leave them running in parallel.

1. I switch to the FleetView sidebar to jump between sessions and

see them all collapsed under a single "ERP" group. The group
label is the project name from ERP.sln, so I cannot tell which
session belongs to the main checkout vs. agent_2 vs. agent_3.

1. To pick the right session I have to open each one and check the

working directory or recent file activity — which defeats the
purpose of the sidebar.

With grouping keyed off the working-directory path (the same key
already used in ~/.claude/projects/), each folder would show up
as its own group ("ERP_3", "ERP_3_agent_2", "ERP_3_agent_3") and
session switching would be instant.

This would save several minutes per day and eliminate the risk of
running a command in the wrong checkout — a real hazard when one
folder is on main and another is on a feature branch.

Additional Context

Evidence that the data needed is already available:

~/.claude/projects/ on disk already stores each folder under its
own normalized key, for example:
c--DEV-repo-ERP-3
C--DEV-repo-ERP-3-agent-2
C--DEV-MS-VS-ERP
C--DEV-MS-VS-ERP-Desktop

So distinct folders are already distinguishable at the storage
layer — only the FleetView grouping logic does not use this key.

Similar features in other tools:

• VS Code "Recent Folders" lists each working directory separately

regardless of the project name inside.

• tmux session managers (tmuxinator, zellij) key sessions off the

directory path.

• JetBrains "Recent Projects" shows the folder path as a tooltip

on each entry to disambiguate same-named projects.

If a screenshot would help, I'm happy to attach one showing the
collapsed group.