Feature Request: Cross-device session continuity — connect to active Claude Code sessions from any Claude client

[zhiqitao]

Summary

Allow users to connect to an active Claude Code session from any Claude client — mobile app, claude.ai web, another laptop, or any other device — with full conversation sync across all of them.

Motivation

OpenAI Codex recently shipped a "connect from phone" feature that lets users continue a Codex session from the ChatGPT iOS app. This is genuinely useful for:

• Uploading photos, screenshots, or documents from your phone (e.g. a photo of a whiteboard, a handwritten diagram, a receipt) directly into an ongoing coding session
• Reviewing progress or providing input while away from your primary machine
• Seamless context switching between devices without losing session state

But the opportunity is bigger than just phone-to-desktop. Claude's ecosystem spans claude.ai web, mobile apps, Claude Code CLI, and IDE extensions. These should all be able to share session state.

Proposed Feature

Universal session continuity across all Claude clients:

• A Claude Code session started on one machine should be joinable from:
  • Claude.ai web (via a dedicated "Claude Code" tab or session view)
  • Claude iOS / Android app
  • Another laptop running Claude Code or claude.ai
  • IDE extensions (VS Code, JetBrains)
• All participants see the same conversation history in real time (synced)
• Any client can send messages, upload files/images, or review tool outputs
• File/photo uploads from mobile go directly into the active session context

User Experience Vision

1. Start a Claude Code session on your laptop as usual
2. On your phone, open the Claude app → tap "Claude Code" tab → see your active sessions
3. Tap to join → you're now in the same session, can read the conversation, send messages, or upload a photo
4. Back on your laptop, the photo appears in context and Claude Code can act on it immediately
5. Same flow works from claude.ai web or a second laptop

Why This Matters

Claude Code sessions involve rich context — file trees, long conversations, tool outputs. Today that context is siloed to one terminal window. Making it universally accessible would:

• Remove the friction of context-switching between devices
• Enable collaborative sessions (pair programming, async review)
• Let users contribute richer input (photos, voice, documents) from wherever they are

This would be a meaningful differentiator and a natural fit given Anthropic's multi-surface presence across web, mobile, and CLI.

Related

• Similar to OpenAI Codex's "connect from phone" feature (announced May 2025)
• Complements existing Claude Code IDE integrations

[github-actions]

Found 3 possible duplicate issues:

1. Cross-device session continuity: account-scoped session sync #55473
2. [FEATURE] Claude Code multi device, chat and progress sync system #49657
3. [FEATURE] Allow resuming Claude Code sessions across devices #47926

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[kcarriedo]

+1 — the "context siloed to one terminal" framing is the right diagnosis. The web/CLI/mobile split is the visible symptom, but the underlying issue is that there's no canonical home for session state other than the terminal process itself, so anything cross-surface ends up reconstructing context lossily.

Two patterns that have helped in adjacent setups while waiting for native support:

1. Externalize the durable parts of context into the repo. A .claude/state/ directory checked into a long-lived branch (or a gist) holding the running task list, decisions log, and last few file diffs lets you hop machines by git pull && claude rather than literally moving terminal state. Doesn't solve the live tool-output stream, but it covers ~80% of what people actually want when they say "continue on phone."

2. Treat the supervisor process from 2.1.139 as the integration point. claude daemon run keeps background sessions alive across terminal closes — if you start sessions from a host that has the daemon enabled and remote-control on, the mobile app can already attach to those, which is the "device A starts, device B continues" workflow in 90% of cases. The gap is more about starting a session remotely than continuing one.

Worth distinguishing in the feature request between "resume from anywhere" (largely solvable today via daemon + remote-control) vs. "start from anywhere" (genuinely missing) — they have very different design implications for state storage and auth.

[cagriy]

I've got a similar request but, somewhat akin to this one, adding a comment to avoid duplicates:

"Claude agents" command is great, letting us control multiple Claude code sessions running on the same computer. It would be fantastic if it worked across computers, giving me full access to all sessions under my account, remote or local.

I am aware of remote control, but it is clunky.

[tcmartin24]

Adding a strong +1 from a daily agent user, specifically because OpenAI Codex has now set the expected baseline here.

The target UX should not require users to run a separate daemon/server or manually manage bridge URLs. If I am using Claude Code through Claude Desktop, I should be able to enable one global remote-control setting, then open the Claude mobile app and see/start/resume/control my Claude Code sessions from there.

Concretely:

• Claude Desktop should expose active Claude Code sessions to Claude mobile automatically after a single global opt-in.
• Mobile should be able to start new sessions and reconnect to existing sessions.
• This should work without a separate manual daemon, server, or per-session setup step.
• The experience should be at least as seamless as OpenAI Codex's current mobile/session-continuity flow, because that is now the product comparison users will make.

Right now Claude feels behind Codex on this workflow. Remote Control is the right direction, but the product-level expectation is: enable once in Desktop, then manage sessions from mobile/web as first-class clients.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.