Share conversation context from Claude.ai to Claude Code

[Rahillasne]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

When planning a project or feature in Claude.ai (web/desktop), I often go through multiple iterations of brainstorming, architecture decisions, and technical planning. Once I'm ready to implement, I have to manually copy-paste context or re-explain everything when I switch to Claude Code. This breaks the flow between planning and building, and Claude Code loses all the nuanced context from the planning conversation.

Proposed Solution

Add a "Send to Claude Code" button or export option in Claude.ai conversations. This would package the conversation context (or a summary of it) into a format Claude Code can import. Ideally:

One-click export from Claude.ai
Import command in Claude Code like /import-context or a flag like claude --from-chat
Claude Code would then have full awareness of the planning discussion and can pick up where the conversation left off

Alternative Solutions

Currently I copy-paste key parts of the conversation into a markdown file or manually summarize the plan in Claude Code's initial prompt. This is tedious and loses nuance.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I'm building something, and I spend 30 minutes in Claude.ai planning my multi-agent architecture, discussing tradeoffs, and finalizing the approach. Now I want to actually build it. I click "Send to Claude Code," open my terminal, run claude --continue or similar, and Claude Code already knows the full plan and starts implementing without me re-explaining anything.

Additional Context

No response

[sudoxreboot]

This is critical for anyone who uses both claude.ai and Claude Code.

Current workflow is broken:

1. Plan/brainstorm in claude.ai (has memory, good for exploration)
2. Ready to implement → switch to Claude Code
3. Claude Code has zero context from the planning phase
4. Manually re-explain everything or copy-paste walls of text
5. Lose nuance, waste time, break flow

What should happen:

claude --from-web <conversation-id>
# or
claude --with-context "my project planning session"

Claude Code starts with full context from the web conversation.

Implementation options:

1. Direct integration - Claude Code can query claude.ai conversation API
2. Export/import - claude.ai exports context file, Claude Code imports
3. Shared backend - Both products read from same context store

If none of these are feasible short-term:

Update ToS to permit subscribers to build their own bridges. We'll extract our own context and feed it to Claude Code. Just don't ban us for accessing our own data.

The web UI has memory but is unstable. Claude Code is stable but has no memory. Let us combine the best of both.

[sreeram-venkitesh]

+1

[ZataraMar]

Definitely needed!

[powerobject]

Hello Claude Team,

Please do NOT implement export/import (results in silos) — need only live read access to chat history and artifacts for always current and single source of truth.

The inability of Claude Code to connect to the same database that Claude.ai connects to using same user creds is a HUGE shortcoming and frustration.

Ten years from now, we will be joking to our kids, “Back in my day, I paid $200/month for Max 20x, had 60+ conversations with detailed architecture specs, database schemas, biz models, security patterns... Claude Code Opus 4.5 in 2026 still did not integrate with our chats/artifacts on Claude.ai at all using same account creds and it was all manual wading through of long, maxed out, overwhelming chats and copy/pasting which is quite the opposite of what AI is supposed to help us with. We'd scroll through conversations so long the browser would lag. Copy-paste code blocks one at a time. Manually maintain CLAUDE.md files like some kind of digital scrapbook. And if you forgot which chat had that one critical decision about session token handling? Good luck — here's a search box that returns 50 results."

That's like what used to be printing out MapQuest directions or manually typing URLs from TV commercials.

All of that institutional knowledge exists right here in my conversations. And Claude Code can't see any of it without me playing human middleware that wastes too much precious time.

The irony:

Anthropic is building AI to reduce tedious manual work... while requiring tedious manual work to use their own products together.

The frustration:

"I'm literally building automation software while manually copying context between your tools."

Claude Code should have live read access to Claude.ai chat history and artifacts

Problem Statement

Claude Code and Claude.ai are completely disconnected despite:
Same authenticated user, Anthropic account credentials, same $200/month Max plan
Claude Code already connects to external services via MCP
Connecting to Anthropic's own conversation API should be trivial

When I open Claude Code, it has zero knowledge of the extensive architectural discussions, design decisions, code reviews, and artifacts I've created in Claude.ai. I'm paying for one Claude, but getting two strangers who don't talk to each other.

When I switch to Claude Code to implement these designs, I have to manually wade through long, maxed-out conversations, copy-paste context, and maintain CLAUDE.md files like a digital scrapbook. This is exactly the kind of tedious manual work AI is supposed to eliminate.

Proposed Solution:
Live read access — not export/import.

Claude Code already:

• Authenticates against the same Anthropic account
• Supports MCP connections to external services (Google Drive, Slack, Asana, etc.)

Connecting to Anthropic's own conversation API should be simpler than connecting to third-party services:

Expose chat history via internal MCP server or API endpoint
Claude Code can query: "What did we decide about session token handling?"
Live access — always current, single source of truth

Why NOT export/import (re: Issue #13843)

Export/import creates unnecessary data silos:

• Point-in-time snapshots that immediately become stale
• Manual sync overhead pushed onto the user
• Data duplication with no single source of truth
• Violates basic architectural principles we'd reject in any production system

I can already search my Claude.ai chat history from within Claude.ai using conversation_search and recent_chats tools. The capability exists — it's just walled off from Claude Code for no apparent technical reason.

The Ask

1. Give Claude Code read access to the authenticated user's Claude.ai conversation history
2. Allow searching by keywords, topics, date ranges (same as Claude.ai's existing tools)
3. Allow searching through and reading artifacts content from past conversations
4. No export files, no manual sync — live access to the same data

Environment

• Plan: Max ($100-200/month)
• Primary use: Enterprise application development
• Claude.ai usage: Heavy — architectural planning, design reviews, documentation
• Claude Code usage: Implementation of designs discussed in Claude.ai

Please do prioritize this severe pain-point issue and implement it in your NEXT release, if possible.

---

Related issues: #14228, #13843

[mikedambrogia]

I griped about this in web Help yesterday, and was informed "This design is intentional across all our platforms - each interface maintains separate conversation histories for privacy and organization purposes."

Really poor Ux, all the chats are in my account, how can there possibly be a permissions problem? And don't all the conversations store in the same data store/history? Pretty sure I've been throttled on the code side and had the throttle timeout appear on the web side... Why the silo'ing then?

+eleventy-five on this "feature"

[selviarora]

built a tool for this if anyone wants to try it: https://github.com/selviarora/claude-context-bridge

chrome extension with a button on claude.ai. saves the conversation locally and exposes it to claude code via mcp

check it out :)