Cross-client session continuity (mobile ↔ VS Code ↔ CLI)

Summary

Currently, remote-control sessions (mobile app), VS Code extension, and CLI maintain completely isolated contexts. Each client spawns its own Claude process with its own conversation history and state. There is no way to continue a session started on one client from another.

Use case

1. Start a task from phone via remote-control while away from desk
2. Get back to the desk and want to continue the same session in VS Code or terminal CLI — without losing context or asking Claude to re-read everything
3. Vice versa: start in VS Code, step away, continue from phone

Current workaround

The only option is to commit intermediate results in one session and manually re-establish context in another. This loses the conversation history, plan state, and any uncommitted work-in-progress reasoning.

Proposed behavior

A way to hand off or resume a session across clients. For example:

• claude --resume <session-id> working across all clients (CLI, VS Code extension, mobile via remote-control)
• A shared session registry that all clients can read from
• Or at minimum, the ability to export/import session context between clients

Environment

• Claude Code CLI 2.1.81
• macOS, claude remote-control via launchd
• VS Code extension