Desktop app groups sessions from multiple projects under a single project name

Summary

In the Claude Code desktop app (macOS), the session history sidebar shows sessions from many different projects all grouped under a single project — in my case historicalyearbook-frontend. The grouping in the UI does not reflect the actual project the sessions belong to.

On disk, sessions are stored correctly: each project has its own directory under ~/.claude/projects/, and each .jsonl session file contains a cwd field pointing to the real working directory where the session ran. So this appears to be a UI/display bug, not a data-corruption bug.

Reproduction

1. Run claude from many different project directories over time (I have ~30+ distinct project directories under ~/.claude/projects/).
2. Open the Claude Code desktop app on macOS.
3. Open the sessions / history view.

Expected: Sessions grouped by the project they ran in (matching the cwd of each session).

Actual: All sessions appear grouped under one project name (in my case historicalyearbook-frontend), even though only 1 session file actually exists in that directory on disk and the others belong to many different projects (btb, kluris, specmint, etc.).

Verification on disk

$ ls ~/.claude/projects/ | wc -l
54

$ ls ~/.claude/projects/-Users-gabrielvoicu-Projects-zeespire-historicalyearbook-frontend/
c90b05e6-406c-404d-9c04-9439b07dd0a2.jsonl   # only 1 session

# A session from a different project directory has the correct cwd:
$ head -3 ~/.claude/projects/-Users-gabrielvoicu-Projects-ngvoicu-kluris/<some>.jsonl | jq -r .cwd
/Users/gabrielvoicu/Projects/ngvoicu/kluris

So the on-disk layout is correct — the desktop app is mis-grouping them when rendering.

Environment

• OS: macOS (Darwin 25.5.0)
• Claude Code CLI version: 2.1.111
• Desktop app version: (happy to add — please tell me where to find it if not in About menu)

Guess at root cause

Looks like the desktop app might be collapsing all sessions under a single project label — possibly the most recently used one, or one where a caching/indexing key is shared. Could be worth checking how the sessions view derives the project name (from the directory name decoding vs. reading cwd from the jsonl).