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

Status Fixed / completed

Maintainer reply ✓ Yes — bcherny

Activity 5 comments · opened Jun 28, 2026 · closed Aug 16, 2026

💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

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.

View original on GitHub ↗

4 Comments

github-actions[bot] · 2 months ago

Found 3 possible duplicate issues:

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 · 2 months ago

This is a real friction point for solo developers working across machines. The core gap is that Claude Code's session model is machine-local by design (sessions are tied to ~/.claude/projects/ on the host running the repo), which makes cross-device visibility hard to add without lifting the whole execution context.

A few things that might partially address this in the near term, depending on your setup:

If both machines share the same git remote, you can start a new session on the second machine in the same project directory -- it won't have the conversation history but will have full repo context. Not ideal, but it is the current supported path.
For read-only session history across devices, syncing the ~/.claude/projects/ directory via a private git repo (not a cloud drive, which has the locking issues you mentioned) can work if you do it manually and never have both machines active simultaneously.

The feature request for a network-attach or account-based session roster makes sense as a longer-term ask -- something like a session index that lives with the account, not the machine, even if execution stays local.

I've run into a version of this building long-running background agent cycles: session state needs to be durable and accessible across process restarts, which is why we ended up writing cycle records to a filesystem state store rather than relying on the in-memory session. The pattern of separating "session identity" from "execution context" might be the right framing for what you're asking for here.

github-actions[bot] · 14 days ago

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

bcherny collaborator · 13 days ago

This is what Remote Control is for. Start a session on each machine with claude remote-control (or claude rc, or /rc inside a session), then open https://claude.ai/code from any browser or the Claude mobile app: all your machines' Remote Control sessions show up in one list, and each one keeps running locally with its own filesystem, tools, and MCP servers. Setup and details: https://code.claude.com/docs/en/remote-control