Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Share conversation history between claude.ai and Claude Code for the same account [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52641•Fetched 2026-04-24 06:01:43
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
jSFBayjSFBay
Participants
github-actions[bot]github-actions[bot]jSFBayjSFBay
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

Claude Code (VS Code / CLI) and claude.ai are completely separate products with no shared memory or conversation history, even when the user is logged into the same Anthropic account. This forces users to re-establish context every time they switch between interfaces, and work done in one session is invisible to the other.

Request: Allow Claude Code to access claude.ai conversation history (or a shared memory store) tied to the authenticated account, so context is not lost when switching between products. At minimum, allow users to export a claude.ai conversation in a format Claude Code can import.

extent analysis

TL;DR

Implementing a shared memory store or API to access conversation history between Claude Code and claude.ai can help retain context when switching between products.

Guidance

  • Investigate the feasibility of creating a shared memory store or API that both products can access, tied to the user's Anthropic account.
  • Explore the possibility of exporting claude.ai conversations in a format that Claude Code can import, as a minimum viable solution.
  • Consider the security and privacy implications of sharing conversation history between products.
  • Evaluate the potential benefits of a unified user experience across Claude Code and claude.ai.

Notes

The implementation details of the shared memory store or API are unclear and may require further discussion and design.

Recommendation

Apply workaround: Implement a feature to export claude.ai conversations in a format that Claude Code can import, as a temporary solution until a more integrated approach can be developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#tensor shape#autograd error#model save/load#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING