Feature Request: Integration between Claude Code and Claude Chat 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

Currently, Claude Code and Claude Chat are completely separate systems with no way to share context:

Claude Chat: I use it for strategic discussions, architectural decisions, brainstorming, and planning for my projects. Over time, I accumulate valuable context and decisions there.

Claude Code: I use it for actual code execution, file editing, and implementation within VS Code.

The problem is that Claude Code has no access to the discussions and decisions I've made in Claude Chat. This forces me to either:

1. Manually copy/paste context between the two (tedious and error-prone)
2. Repeat explanations and decisions I've already made in Chat
3. Maintain separate documentation files just to bridge the gap

Proposed Solution

Allow Claude Code to optionally connect to my Claude Chat account and access:

• Project context from Claude Chat Projects
• Conversation history related to the current codebase
• Key decisions and notes I've saved in Chat

This could be implemented as:

• A /sync command to pull context from Claude Chat
• Automatic detection of related Claude Chat Projects based on the repository
• A setting to link a Claude Code workspace to a Claude Chat Project

Benefits

• Seamless workflow: Discuss strategy in Chat, execute in Code - with shared context
• No repeated explanations: Claude Code would already know the architectural decisions made in Chat
• Better productivity: Eliminates manual context transfer between products

Alternative Solutions

1. Manually copy/paste context between the two (tedious and error-prone)
2. Repeat explanations and decisions I've already made in Chat
3. Maintain separate documentation files just to bridge the gap

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

I'm building a medical practice management SaaS ("Core Consultório"). My typical workflow:

In Claude Chat: I discuss architectural decisions like "Should we use React Query or Redux for state management?", "What's the best approach for the patient billing integration?", debate pros/cons, and reach conclusions.

In Claude Code: I say "Implement the billing integration" - but Claude Code has no idea about the decisions I made in Chat. I have to re-explain everything: the chosen approach, the reasons, the constraints we discussed.

The friction: Every time I switch from planning (Chat) to execution (Code), I lose context. After months of development, I have hundreds of valuable conversations in Chat that Claude Code cannot access.

Ideal scenario: I open Claude Code and say "Implement the billing integration we discussed" - and it already knows the approach, constraints, and decisions from my Chat history.

Additional Context

Many developers use Claude Chat for high-level discussions and Claude Code for implementation. Bridging these two products would significantly improve the developer experience and make the Anthropic ecosystem more cohesive.

Note: I'm not a developer by training - I'm a physician building a SaaS for my medical practice. Claude has been essential for me to build real software without a traditional programming background. However, the disconnect between Chat (where I plan and learn) and Code (where I execute) creates significant friction. For non-developers like me, who can't easily build workarounds, this integration would be transformative.