Feature Request: Share project context between Claude.ai Chat and Claude Code

Resolved 💬 1 comment Opened Jun 5, 2026 by guillermodabove66 Closed Jul 13, 2026

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

Summary

When a user uploads files or builds project memory in a Claude.ai Chat project,
that context is not accessible from Claude Code (CLI / desktop Code tab), even
when both are running in the same desktop app under the same account.

Current behavior

  • Files uploaded to a Claude.ai Chat project live only in that system
  • Claude Code sessions have no way to access them
  • Users must re-upload the same files manually in the Code tab

Expected behavior

Files and project context added to a Claude.ai Chat project should be accessible
from Claude Code sessions linked to the same project, without requiring the user
to duplicate uploads.

Why this matters

Many users work with both interfaces simultaneously — Chat for discovery/analysis,
Code for implementation. Forcing re-uploads breaks the workflow and creates
redundancy, especially for large or frequently updated reference files.

Example use case

A user maintains a project called "Instalaciones" in Claude.ai Chat with an energy
consumption PDF as shared context. When switching to Claude Code to build a feature
that depends on that data, they must re-upload the file manually — even though both
tabs are open in the same desktop app under the same account.

Environment

  • Claude desktop app (Windows)
  • Claude Code tab + Claude.ai Chat tab, same account

---





### Proposed Solution

## Expected behavior
Files and project context added to a Claude.ai Chat project should be accessible 
from Claude Code sessions linked to the same project, without requiring the user 
to duplicate uploads.

## Why this matters
Many users work with both interfaces simultaneously — Chat for discovery/analysis, 
Code for implementation. Forcing re-uploads breaks the workflow and creates 
redundancy, especially for large or frequently updated reference files.

## Example use case
A user maintains a project called "Instalaciones" in Claude.ai Chat with an energy 
consumption PDF as shared context. When switching to Claude Code to build a feature 
that depends on that data, they must re-upload the file manually — even though both 
tabs are open in the same desktop app under the same account.

## Environment
- Claude desktop app (Windows)
- Claude Code tab + Claude.ai Chat tab, same account

### Alternative Solutions

_No response_

### Priority

Low - Nice to have

### Feature Category

CLI commands and flags

### Use Case Example

see above

### Additional Context

None

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗