Claude Code Remote Control Sessions Now Stay in the Folder They Started In
Claude CodeClaude Code 2.1.321 changes Remote Control sessions to keep the folder they were started in. A connected client can no longer move a session to another folder.
Key Takeaways
- Remote Control sessions now keep their starting folder.
- A connected client can no longer move a session to a different folder.
- The folder defines the trust boundary, including file access, permission rules and project settings.
- This is a behavior change: any workflow that moved a session from the client must now start a new session.
- The change reduces what a remote client can authorize, since it cannot widen the session's reach.
- It arrived alongside other Remote Control fixes in 2.1.321, such as queued messages no longer interrupting a running turn.
A session cannot be moved by the client
Remote Control lets a phone, the web or the desktop app connect to a Claude Code session running on a developer's computer. Claude Code 2.1.321 changes how such a session handles its working folder: it keeps the folder it was started in, and a connected client can no longer move it to another folder.
Why it matters
The folder a session starts in decides which files the agent can read and write, which permission rules and trust decisions apply, and where project settings come from. If a connected client could change that folder, a client could point the session at a directory the user never approved. Locking the folder keeps the trust boundary where the person who started the session set it. Developers who want a session in a different folder start a new one there.