Support Parent Workspace Folders for Multi-Project Workflows

What happened

I was actively working on one project, then started a second project online, and later needed to return to the original project. My primary workspace is my Content Knowledge Base located at C:\CKB\, which contains all of the folders and resources I use across projects.

With the current folder access model, I was unable to re-add my main C:\CKB\ directory and was limited to adding only individual subfolders. Because of that restriction, I had to work around the issue through the terminal instead of using the standard project setup workflow.

As a result, I also lost the context from my previous conversation thread and had to start over in a new session, creating unnecessary friction and lost productivity.

Expected behavior

I should be able to add my root knowledge-base folder (C:\CKB\) as a trusted project source and allow Claude Code to access the folders I need from that location.

Current limitation

The current implementation appears to restrict folder access to individual subfolders and limits the number of folders that can be added (currently six). This becomes problematic when:

Multiple projects depend on resources stored throughout a central knowledge base.
The required folders exceed the six-folder limit.
Different projects need different combinations of files located across the same root directory structure.
Why this matters

Many users organize their work around a centralized knowledge repository rather than isolated project folders. In my case, C:\CKB\ serves as the master knowledge base for all projects. Restricting access to only a handful of subfolders creates unnecessary management overhead and makes it difficult to maintain continuity across projects.

Suggested improvement

Allow users to add a parent knowledge-base directory (for example, C:\CKB\) as an approved workspace location. This would:

Eliminate the need to manually add multiple subfolders.
Remove artificial folder-count limitations for users with large knowledge bases.
Improve multi-project workflows.
Reduce context switching and project setup friction.
Better support users who maintain centralized documentation and resource repositories.

Environment

• Filed from: Report a problem in Claude Code
• Project ID: chan_01Vhf9p5rPHkBBQQia4nqfS7
• Thread ID: cmsg_01Vhf9p5rPHkBBQQia4nqfS7B3CFhJ4nnQHqQgd2EwH11U