Access local Claude Code sessions from another machine (multi-device session access)

Problem

Local Claude Code sessions live on disk per machine (~/.claude/projects/...) and aren't reachable from another device. Working across two PCs (e.g. a home laptop and a work PC), each with project-bound local sessions, means physically switching laptops or remoting in via RDP/SSH. There's no way to view or continue another machine's local sessions from one place.

Request

A way to attach to / browse / continue a local Claude Code instance running on another machine over the network (LAN or via account), so a single device can manage local sessions from multiple machines in one view — without giving up the per-machine local repo/environment context.

Use case

A solo developer with a home laptop and a work PC, each holding project-bound local sessions, wants one machine to act as the control point for both — without losing the local execution context that ties each session to its machine's repos and environment.

Current workarounds (and why they fall short)

• Cloud / web sessions — solves multi-device access, but gives up the local execution context entirely.
• RDP / SSH into the other machine — keeps sessions local, but you're managing two separate sessions in two windows, not one unified view.
• Syncing ~/.claude/projects/ via a cloud drive — fragile and unsupported; conflicts when both machines run concurrently.