[FEATURE] Visual project-based session organization with folders and pinning

1. TITLE

Visual project-based session organization with folders and pinning

2. PREFLIGHT CHECKLIST

• [ ] I have searched existing requests and this feature hasn't been requested yet
• [ ] This is a single feature request (not multiple features)

3. PROBLEM STATEMENT

Sessions accumulate quickly when working across multiple projects. The current session list is flat - finding a specific session requires:

• Remembering the exact name (if I renamed it)
• Scrolling through a chronological list
• Using search (but I need to remember keywords)

When I have 20+ sessions across 5 projects, the list becomes overwhelming. I lose track of:

• Which sessions belong to which project
• Which sessions are "active work" vs. "completed"
• Which sessions I want to revisit vs. can archive

4. PROPOSED SOLUTION

Add project-based organization to the Claude Code Desktop session list:

Automatic Grouping:

• Sessions are automatically grouped by git repository/project directory
• Each project becomes a collapsible folder in the sidebar
• Projects sorted by most recent activity

Visual Hierarchy:

▼ ~/projects/frontend (3 sessions)
    ★ Auth refactor (pinned)
    Dashboard polish
    Bug #423 fix

▼ ~/projects/backend (2 sessions)
    API redesign
    Performance optimization

▼ ~/scripts (1 session)
    Deployment automation

▶ Archived (5 sessions) [collapsed]

Session Actions:

• Pin: Keep important sessions at top of project group
• Archive: Move to collapsed archive folder (not deleted)
• Tag/Label: Add custom tags like "WIP", "Review", "Done"
• Color coding: Optional visual distinction

Filtering:

• Filter by project
• Filter by tag
• Filter by date range
• Search within project or globally

Keyboard Navigation:

• Arrow keys to navigate projects and sessions
• Enter to expand/collapse project
• p to pin/unpin
• a to archive

5. ALTERNATIVE SOLUTIONS

Current workarounds:

1. Descriptive names: /rename "frontend: auth refactor" - works but manual, clutters names
2. Delete old sessions: Lose context and history
3. Mental mapping: Remember which session was which - doesn't scale
4. Separate Claude instances: One terminal per project - heavyweight, no unified view

What Codex does:
"Agents run in separate threads organized by projects, so you can seamlessly switch between tasks without losing context."

Project-based organization is the natural mental model for developers.

6. PRIORITY

• [ ] Critical - Blocking my work
• [ ] High - Significant impact on productivity
• [ ] Medium - Would be very helpful
• [x] Low - Nice to have

7. FEATURE CATEGORY

• [ ] CLI commands and flags
• [x] Interactive mode (TUI)
• [ ] File operations
• [ ] API and model interactions
• [ ] MCP server integration
• [ ] Performance and speed
• [ ] Configuration and settings
• [ ] Developer tools/SDK
• [ ] Documentation
• [ ] Other

8. USE CASE EXAMPLE

Scenario: Typical week working on multiple projects

Monday:

• Start session in ~/frontend: "Implement user dashboard"
• Start session in ~/backend: "Add REST API for dashboard"
• Start session in ~/frontend: "Fix mobile responsive layout"

Tuesday:

• Start session in ~/scripts: "Write deployment script"
• Continue ~/backend API session
• Start new ~/frontend session: "Add dark mode"

Wednesday:

• Need to revisit Monday's dashboard implementation

With project organization:

1. Open Claude Code Desktop
2. See projects listed:

``
▼ frontend (3 sessions)
★ User dashboard (pinned Monday)
Mobile responsive
Dark mode
▼ backend (1 session)
REST API
▼ scripts (1 session)
Deployment
``

1. Expand frontend, click "User dashboard", immediately back in context

Without project organization:

1. See flat list of 5 sessions with generic timestamps
2. Scroll, try to remember which was which
3. Maybe find it, maybe click wrong one first

Time saved: 30 seconds per context switch × many switches per day = significant cumulative benefit.

9. ADDITIONAL CONTEXT

Implementation considerations:

• Project detection via git root or working directory
• Sessions without git could group under "Ungrouped" or directory name
• Preserve existing /rename functionality within this structure
• Consider syncing organization across Desktop/CLI/Web

Related features:

• Worktree sessions could be sub-grouped under their parent repo
• Automation results could integrate into project groups
• Session search could scope to current project by default

Prior art:

• VS Code's workspace/folder organization
• Browser tab groups
• Slack's channel organization by workspace
• Linear's project/team hierarchy