[FEATURE] Treat Claude Project as the parent container for Code and Cowork sessions

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, Claude Code, and Cowork are all tabs in the Claude desktop app but operate as isolated contexts. There is no shared knowledge layer, no automatic artifact persistence, and no way for a Code session to push context back to its parent Project without manual copy/paste or file uploads. This creates friction that undermines the value of having all three tools in a single application.

Current workaround is a manual multi-step workflow:

• Ask Project Chat to summarize session outcomes and generate CLAUDE.md
• Ask Code to generate context documents, then manually upload them back into the Project
• Copy/paste outputs between sessions at each handoff

Proposed Solution

Treat a Claude Project as the parent container for Chat, Code, and Cowork sessions. Concretely:

• Shared context: Project knowledge (files, custom instructions, notes) should be accessible from Code and Cowork sessions without manual re-upload.
• Artifact persistence: Artifacts generated in Code sessions (e.g., CLAUDE.md, architecture docs, progress notes) should be pushable back to the parent Project automatically or via a single action.
• Session continuity: Starting a Code or Cowork session from within a Project should carry relevant Project context forward rather than starting from a blank slate.

Alternative Solutions

Manual multi-step workflow as described above. No viable third-party alternative exists — this requires first-party integration between the three tools.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

1. Architecture and planning work happens in a Claude Project (Chat tab)
2. Project Chat output is used to kick off a Code session — specifically generating a CLAUDE.md and a starter prompt
3. Code session produces artifacts (CLAUDE.md, implementation notes, etc.)
4. Those artifacts need to be reflected back in the Project for the next planning cycle
5. Currently every handoff between steps 1-4 requires manual file management (copy/paste or upload)

With this feature: artifacts from Code would be automatically available in the parent Project, and starting a Code session from within a Project would carry Project context forward without re-upload.

Additional Context

_No response_