Feature request: Allow Claude Projects knowledge base access within Claude Code

Summary

Allow Claude Code to access/import a Claude Projects knowledge base (the files attached to a Project on claude.ai) so users can bring their existing project context directly into a Claude Code session.

Motivation

Many teams already maintain a Claude Project with a knowledge base of foundational documents for a codebase or initiative — PRDs, design documents, architecture decisions, style guides, etc. Today, moving from a Claude Project (web) to Claude Code means manually re-uploading or re-pasting these documents into the new environment, which is friction-heavy and easy to get out of sync.

If Claude Code could read from (or import/sync) a linked Claude Project's knowledge base, it would make the transition from ideation/planning in Projects to implementation in Claude Code seamless — no need to manually re-provide the same initial documents.

Proposed behavior

• Let a user link a Claude Code session/repo to an existing Claude Project.
• On linking (or on demand via a command, e.g. /project attach <project-name>), pull in the Project's knowledge base files (PRDs, design docs, specs, etc.) as available context/reference material for Claude Code.
• Optionally keep this in sync (or allow manual re-sync) so updates to the Project's knowledge base are reflected in Claude Code.

Example workflow

1. User creates a Claude Project on claude.ai and uploads a PRD and design doc while planning a feature.
2. User starts a Claude Code session for the related repo.
3. User runs a command (or is prompted) to attach the existing Claude Project.
4. Claude Code now has access to the PRD/design docs as context without the user needing to re-upload them.

Alternatives considered

• Manually copy/paste or re-upload documents into Claude Code each time (current workaround) — works but is repetitive and error-prone when documents change.

Additional context

This would primarily help users who plan and gather requirements in Claude Projects (web) and then move to Claude Code for implementation, keeping their initial context (PRD, design docs, etc.) accessible in both places.