claude-code - 💡(How to fix) Fix Feature request: Share conversation history between CLI and desktop app [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#53286Fetched 2026-04-26 05:19:36
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×1cross-referenced ×1labeled ×1

Fix Action

Fix / Workaround

Current Workaround

RAW_BUFFERClick to expand / collapse

Problem

The Claude Code CLI and desktop app maintain completely separate session states with no cross-client synchronization. When switching between the two clients, all conversation context is lost.

Proposed Solution

Sync conversation history across clients (CLI ↔ desktop app) so users can pick up where they left off regardless of which client they're using.

Use Case

Working on a project via CLI, then continuing the same session in the desktop app (or vice versa) without losing context.

Current Workaround

The file-based memory system (~/.claude/projects/.../memory/) partially addresses this by persisting structured key facts across sessions, but it doesn't preserve full conversation history.

Additional Context

This would be especially useful for long-running projects where conversation context carries significant value.

extent analysis

TL;DR

Implementing cross-client synchronization of conversation history between the Claude Code CLI and desktop app is likely to resolve the issue of lost context when switching between clients.

Guidance

  • Investigate the current file-based memory system (~/.claude/projects/.../memory/) to understand its limitations and potential for extension to store full conversation history.
  • Design a synchronization mechanism that can handle differences in session state between the CLI and desktop app, ensuring seamless transitions between clients.
  • Consider the implications of storing and syncing potentially large amounts of conversation history, including performance and storage concerns.
  • Evaluate the need for a centralized storage solution or a distributed approach to manage conversation history across clients.

Example

No specific code example can be provided without further details on the existing implementation, but a potential approach might involve using a standardized data format for conversation history and a synchronization protocol to ensure data consistency across clients.

Notes

The solution will depend on the specific requirements and constraints of the Claude Code ecosystem, including security, performance, and user experience considerations. The proposed solution should balance the need for seamless context switching with the potential complexity and overhead of cross-client synchronization.

Recommendation

Apply a workaround by enhancing the existing file-based memory system to store and synchronize full conversation history, as this seems to be the most direct path to addressing the user's need for context continuity across clients.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Feature request: Share conversation history between CLI and desktop app [1 comments, 2 participants]