[FEATURE] Structure in the session sidebar for multi-agent work — derived status + nesting

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 run several Claude sessions in parallel across a few projects — a coordinating session plus task-specific ones. At that scale the flat session list stops holding the work: I can't tell at a glance which session is running, which is waiting, which is done, or which one is the coordinator. I rebuild that map in my head on every context switch, and the cost grows with the number of sessions — exactly when I can least afford it. Projects gives me grouping, but not visibility into the state of parallel work.

Proposed Solution

Two additions, in order of value:

1. Derived status on each session in the list — active / waiting / done — read from the session's own state (is it running? idle?), not set by hand. The desktop app already tracks running + last-activity, so this just surfaces data that already exists. A small status dot/label per row would, on its own, remove most of the pain.

1. Two-level nesting inside a project (project → named groups → sessions), so parallel branches read as distinct lanes instead of one flat column.

Beyond that — a designated "control" session, a manual queue/priority, and dependency links between sessions — would form a full multi-agent control view, but I assume that's a larger effort you'd scope yourselves. The high-value front edge is just: derived status first, nesting second. (Mockup in Additional Context.)

Alternative Solutions

Today I approximate it myself: a small script reads the desktop app's own session state and renders an always-on status board in a browser tab. It works, but it can't live in the sidebar, isn't clickable, and depends on internal file layout — which is exactly why a native treatment matters: the data is already there, only you can surface it in the product.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Five sessions open: 2 running, 1 waiting on another to finish, 1 idle, 1 done. I switch to another project for 20 minutes. Coming back, instead of reading five ambiguous titles (some near-identical) and reconstructing what each was doing, I glance at the list: green = running, the waiting one shows what it's blocked on, the done one is checked. I pick up exactly where it matters in seconds.

<img width="880" height="1000" alt="Image" src="https://github.com/user-attachments/assets/be8e11e1-e8ad-4b08-b8b3-2f3401c4f7de" />

Additional Context

Mockup of the desired sidebar attached below (generic — no real data). I currently approximate this myself with a small script that reads the desktop app's own session state and renders an always-on status board in a browser tab; happy to share details. The point: the data already exists — only a native sidebar treatment can make it always-on and clickable.