[Feature Request] Seamless session sharing between Claude Code and Claude Desktop

Status Open
Reported on v2.0.76
Maintainer reply None cached
Activity 9 comments · opened Dec 31, 2025

Bug Description
Feature Request: Seamless Session Sharing between Claude Code and Claude Desktop

Problem:
Currently, there's no direct way to share conversation context between Claude Code (CLI) and Claude Desktop. Users must manually export to files, upload, or copy-paste - which breaks the flow of work.

Use Cases:

  1. Code → Desktop: Preserve development discussions as permanent history (Code sessions feel volatile)
  2. Desktop → Code: Continue research/planning directly into implementation

Requested Feature:

  • One-click "Share to Desktop" / "Share to Code" button
  • Or a shared conversation history accessible from both interfaces
  • Ideally with selective sharing (share specific messages or summaries)

Why it matters:

  • Claude Code excels at coding but sessions feel temporary
  • Claude Desktop excels at research/brainstorming with persistent history
  • Seamless handoff would create a powerful unified workflow

This would significantly improve the developer experience for users who rely on both tools daily.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.0.76
  • Feedback ID: 9127bd17-ea9f-44e5-91b8-2998c1c30f90

View original on GitHub ↗

9 Comments

sespinosa · 7 months ago

+1 for this, but I'd like to expand the scope beyond just sharing history.

The real power would be live session sharing — controlling a running Claude Code session from other devices in real-time.

Use Cases

  • Switch to Desktop to view images or diagrams
  • Read documents without generating PDFs or installing extra tools
  • Use voice input or dictation from Desktop or mobile
  • Control a running session remotely from your phone or laptop
  • Approve permissions or answer questions while away from your desk
  • Start a long task on your PC and monitor progress from anywhere
  • No need to stay glued to one machine waiting for Claude to finish

Proposed Implementation

Keep it simple: a toggle to make a session available to your other devices.

From Claude Code CLI:

/share on               # Session appears on your linked devices (Desktop, mobile, web)
/share off              # Session is local-only again
/share readonly         # Others can watch but not interact

How it would work:

  • Run /share on and the session instantly appears in Claude Desktop, the mobile app, or claude.ai
  • Your devices are already linked to your Anthropic account — no codes, no QR, no extra setup
  • The host terminal stays in control by default
  • Switch to Desktop when you need rich media, switch to mobile when you step away
  • /share off when you want privacy or to reduce distractions

Once this foundation is in place, sharing sessions with other people (pair programming, mentoring, demos) becomes a natural next step.

👍 Would love to see this prioritized!

chadbyte · 6 months ago

This is exactly what I built.

https://github.com/chadbyte/claude-relay

Your expanded scope — live session sharing, controlling a running session from other devices in real time, approving permissions while away — that's claude-relay.

Run npx claude-relay in your project directory. Open the URL on any device. Every connected device sees the same session live via WebSocket. Type on one, see it on all. Approve from whichever device is closest.

npx claude-relay

No install, no cloud, free and open source.

Crackkart · 5 months ago

Adding my +1 — I use Claude across VS Code agent, claude.ai browser, and Cursor for Laravel development. Cross-surface history would be a game changer for professional workflows.

pierregodard · 5 months ago

The Codex VS Code extension already does this well: local and cloud tasks appear in a unified view, and you can seamlessly move between the browser and the IDE. Start something in the cloud, pick it up locally, or the other way around.

A unified session list across claude.ai, the VS Code extension, and the CLI would be a huge improvement.

rsktash · 5 months ago

But we need connection between claude code cli and claude.ai chat.
Because we need what claude code lacks: the seamless ui mockup generation capability claude.ai chat offers.

slyapustin · 4 months ago

Claude Code in terminal have their own sessions compare to Claude Code from Desktop app.
This is very frustrating. Is there a way to use the same sessions history between both of them?

lukas-1997 · 4 months ago

+1 — I use Claude Code CLI heavily for automated workflows (apartment hunting bot with MCP tools, Chrome automation, Gmail integration) and the inability to review or continue these CLI sessions in the Desktop app is a real pain point. Session history is split across two separate storage locations (~/.claude/sessions/ vs ~/Library/Application Support/Claude/claude-code-sessions/) with no way to bridge them. A unified session view or at minimum a CLI→Desktop transfer command would be extremely valuable for power users running long autonomous sessions.

mcajada · 3 months ago

+1 - If possible with Claude Design as well!

Adamou02 · 20 days ago

Any news about this ? I just lost my entire hisory in the desktop app...
Json file are here but I have to manually import all of them :'(