[Feature] Offer to run the session on the machine that hosts a network-mounted working folder
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Problem
I opened a Claude Code session in the desktop app on Mac A and chose a working folder that lives on Mac B, mounted over SMB. Every command (flutter, git, Gradle) then ran on Mac A and read/wrote files over the network. That caused file-lock hangs (Flutter's Swift Package Manager lock, Gradle included-build locks, orphaned .git/index.lock) and slow builds, and the session had to invent workarounds such as copying sources to a local folder before each test run.
Mac B also has Claude installed and is signed in to the same account. Running the session on Mac B and driving it from Mac A with Remote Control avoids all of this, but nothing pointed me to that setup. I only found out after asking why implementation was slow.
Proposed Solution
Suggestion
- Detect that the chosen working folder is on a network mount and identify the host serving it.
- Check whether that host is one of the devices signed in to the same Claude account.
- If it is, ask: "This folder lives on <host>. Run the session there instead?" On yes, start the session on that host with its local path and connect it to the current window via Remote Control, so the local window is only for chatting and giving instructions.
Benefit
Work runs on the disk that actually holds the files: no network file locks, faster builds and tests, and users don't have to discover Remote Control on their own to get there.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Performance and speed
Use Case Example
_No response_
Additional Context
_No response_