Better Multi-project workflow

Claude Code Session Naming Workflow Issue

Problem Statement

When using Claude Code's --resume feature to maintain multiple parallel work sessions, the tool automatically renames sessions based on conversation content, making it difficult to identify and resume specific sessions after restarting the application.

Use Case

A developer maintains 4-6 concurrent sessions across different aspects of a large project. These are distinct projects, but inter-related enough to justify being in the same "solution" tree folder. For example:

• Session 1: Working on reactive state management library
• Session 2: Database schema design and migrations
• Session 3: Frontend UI components
• Session 4: Testing framework improvements
• Session 5: Documentation updates
• Session 6: Performance optimization

Being able to have very specific conversations with each, by moving from terminal to terminal is fantastic -- until forced to exit the Claude Code app. Trying to figure out which session to associate with the terminal is very challenging and annoying.

Imagine, for instance, if vs code did not allow you to name your source files and instead created a summary name that changed each time you saved a file -- super annoying.

Impact

• Lost Context: Difficult to resume the correct session, leading to context switching overhead
• Productivity Loss: Time spent identifying sessions that could be spent coding
• Workflow Interruption: Breaks the mental model of organizing work by logical boundaries
• Multi-Project Challenges: Especially problematic when working across multiple repositories

Request: Cones of Silence

Adding a way to permanently name a session would be fantastic, however, there may be a better workflow you could create entirely.

For instance, instead of user having to create n terminals (in my case I show terminals in a right, not bottom, orientation mode so they show up as vertical stack of names that I rename e.g. "claude - project_a", "claude_project_b" etc., you could provide similar UX:

• Allow distinct sessions to be managed and viewed through a vertical list, with the current selected showing its contents in adjent area to the left (or right)
• User could rename sessions in situ
• Sessions could also have descriptions
• You could borrow your sub-agent's pre-declared prompt concept for each session, or just defer entirely to user, e.g. user could direct claude to a CLAUDE.md etc.

This may seem to encroach into your sub-agent feature. It shares some characteristics but is fundamentally different; it's not about having a master session coordinating sub-agents, it's about distinct unrelated cones of silence.

The user has the master solution's file structure and can drag in content that may be outside of the current cone's context, e.g. "hey, I'm working in a different session but this material may help, as you are downstream from them..."

Conclusion

Both the low-rent option of allowing session names, or the UX improvement would make life much nicer.

Keep up the great work!