Feature request: drag-to-reorder session groups + folder-linked groups (shared context, progress roll-up, concurrent-write gating)
Feature request: reorderable session groups + folder-aware groups (shared context, rolled-up logs, write-gating)
1. Let us drag/reorder groups in the sidebar
Newly created groups are pinned to the bottom of the list with no way to move them. If I create a group for the project I'm actively working on, it ends up below older, less-used groups. Please allow drag-and-drop reordering of groups (and ideally sessions within/between groups).
2. Assign folders to groups
Today we link a folder to a session at creation time. It would be more powerful to link a folder to a group, so the group becomes the unit of project organization:
- New sessions started inside the group inherit the folder automatically.
- The group could point at existing context (CLAUDE.md, memory, notes) that applies to all sessions/files in that group's chats, instead of each session rediscovering it.
3. Group/folder-level session log ("Progress" roll-up)
When working on 3 features across 3 parallel sessions in the same project, there's no shared record of overall progress. A group-level log that updates as its member sessions do work — "what changed across all sessions in this folder" — would make multi-session projects much easier to track and resume.
4. Folder-level write gating for concurrent sessions
The biggest pain point: multiple related sessions overwrite the same files at the same time — especially shared logs and memory/status docs. Some form of coordination at the folder/group level would help, e.g.:
- advisory locks or a write queue for files under the group's folder,
- conflict detection ("another session in this group modified SESSION_STATUS.md since you read it") instead of silent last-write-wins,
- or routing log/memory updates through a group-level triage step that merges rather than clobbers.
Environment
- Claude Code desktop app on Windows 11
- Heavy multi-session workflow: several concurrent sessions per project sharing one working folder and shared status/memory markdown files
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗