[FEATURE] Thread folders with hierarchical read permissions

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

Claude Code currently presents all threads in a flat, unnamed list with no organizational tools whatsoever. There is no way to:

• Rename a thread (names are auto-generated from the first message)
• Pin or star important threads
• Group threads into folders or categories
• Control which threads can see into other threads' context

For users managing a single project with a handful of threads, this is inconvenient. For users managing multiple sub-projects with dozens of threads (50-60+), it's completely unworkable. Every thread looks identical in the sidebar, and the only way to find the right one is to click through each one and read the conversation history. There is no hierarchy, no permissions, and no organization of any kind.

Proposed Solution

1. Folder & Subfolder Structure

Users should be able to create folders and nested subfolders to organize threads, with the ability to rename any thread or folder.

Users should be able to drag/move threads between folders and pin important threads to the top within a folder. Folder structure should persist across sessions. Optionally, folders could be associated with a working directory so all threads in that folder auto-read the same CLAUDE.md.

1. Hierarchical Read Permissions (corporate org-chart model)

Folders should support inherited read permissions that follow a parent-child hierarchy — like a CEO/Manager/Worker org chart:

• Parent folders can always read down into all child folders and threads beneath them. A top-level "Master" thread can see everything across all sub-projects.
• Child threads cannot read up into parent folders. An individual author thread can't see the master coordination thread's context.
• Sibling folders cannot read across into each other by default. The Magazine folder can't see into the Calculators folder, and vice versa.
• A parent can explicitly grant cross-folder access. For example, the top-level project owner could grant the Magazine folder read access to the NewsMiner folder if needed.
• Permissions inherit downward automatically. If the Magazine folder is granted access to NewsMiner, all author threads within Magazine also get that access.

This matters because when working at a "manager" level (e.g., coordinating a 10-author magazine), you need visibility into all threads below you to maintain consistency. But individual worker threads shouldn't bleed into unrelated projects. And the master coordination thread at the top needs full visibility to make architectural decisions that affect everything.

Thanks much for all you're doing; I love it so far. Just needs more organizational capabilities.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Example:

1. Hierarchical Read Permissions (corporate org-chart model)

Folders should support inherited read permissions that follow a parent-child hierarchy — like a CEO/Manager/Worker org chart:

SFO Terminal (top-level project folder)
├── Magazine Project/
│ ├── Author: Market Analyst (thread)
│ ├── Author: Options Strategist (thread)
│ ├── Author: Crypto Columnist (thread)
│ └── ... (10+ threads)
├── Calculators/
│ ├── SPY Calculator (thread)
│ ├── Options Calculator (thread)
│ └── Dividend Calculator (thread)
├── NewsMiner/ (thread or subfolder)
├── Monetization/ (thread or subfolder)
└── Master Coordination Thread (thread)

Additional Context

_No response_