Feature Request: Two-Level Project Hierarchy (Workspaces containing Projects)

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 Projects are currently flat: a single list of isolated workspaces. This works well for individual tasks, but breaks down for users who manage several distinct life or work domains simultaneously.

Today, I have to choose between two bad options:

• Merge unrelated work into one project → losing meaningful isolation
• Duplicate the same foundational context (who I am, my goals, my working style) across every project → losing efficiency and consistency

This isn't a niche use case. Any serious user manages multiple domains: professional projects (business plan, marketing, finance), personal projects (health, nutrition, sport, finances), side projects, etc. The flat structure doesn't scale to real life.

Proposed Solution

Add a parent layer — call it "Workspace" or "Folder" — that can contain multiple existing Projects, following the same isolation logic that already makes Projects valuable.

Introduce a two-level hierarchy:

Workspace: "Company A"                ← e.g. a first venture
├── Project: Business Plan
├── Project: Marketing Strategy
└── Project: Financial Projections

Workspace: "Company B"                ← e.g. a second venture
├── Project: Product Roadmap
├── Project: Investor Relations
└── Project: Legal & Compliance

Workspace: "Wellbeing"                ← personal health domain
├── Project: Nutrition
├── Project: Sport & Training
├── Project: Health Tracking
└── Project: Supplements & Research

Workspace: "Real Estate Investment"   ← a specific life project
├── Project: Market Research
├── Project: Financing & Mortgage
├── Project: Property Search
└── Project: Legal & Notary

The design principle mirrors what already exists:

• Each Workspace is fully isolated from other Workspaces (same as Projects today)
• Each Workspace holds shared context, instructions, and documents inherited by all its child Projects
• Each child Project retains its own specific context, instructions, and chat history on top of that

Alternative Solutions

• Global Instructions in Claude are too broad — they apply to everything, with no domain scoping. They don't allow having a different shared context per domain.
• Local folder hierarchy in Claude Desktop is a technical workaround, not a native UX solution — and it doesn't exist at all in Claude Web.
• Neither option provides a visual, manageable parent layer in the interface.

The key distinction: this request is not about navigation UX (grouping sessions visually). It's about shared context inheritance — a Workspace-level system prompt / document set that all child Projects automatically inherit. That's an architectural need, not a cosmetic one.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I'm a founder running two ventures simultaneously while also managing personal health and a real estate investment project.

Today (painful):

1. I open Claude and see a flat list of ~12 unrelated Projects
2. I need to work on my "Business Plan" for Company A → I enter the project, but it has no awareness of my other Company A projects or the shared context (my role, the company's mission, its positioning)
3. To keep consistency, I've had to manually copy the same foundational CLAUDE.md into every Company A project — and keep it in sync when things change

With Workspaces:

1. I create a Workspace: "Company A" with a shared CLAUDE.md describing the company, my role, and the shared context
2. Under it, I create Projects: Business Plan, Marketing Strategy, Financial Projections
3. Each child Project inherits the Workspace context automatically — no duplication
4. Switching between domains is clean: "Wellbeing" workspace has its own shared health context inherited by Nutrition, Sport, and Health Tracking projects
5. Each domain is fully isolated from the others, just like Projects are isolated today

Additional Context

Scope

Two levels would already be a significant improvement. No need for unlimited nesting. The ask is minimal: apply the isolation logic that makes Projects work today, one level up.

Affects: Claude Web, Claude Desktop (Cowork), potentially mobile

Related Issues

#22617 requests visual folder/grouping of sessions in the Claude Code Desktop sidebar (primarily a navigation UX ask). This request is different: it targets Claude Projects (not sessions), and its core ask is shared context inheritance — a Workspace-level CLAUDE.md / system prompt / document set that all child Projects automatically inherit. The distinction is architectural, not just cosmetic.