Unclear It is not clear which remote switch controls whether this attach-and-sync path is available.
What
The text around keeping a local folder in sync with a cloud session (a Claude Code session running remotely, started for example with --cloud) changed.
- A new consent question, "Keep this folder in sync with the cloud session?", appears when attaching a folder. It explains that sync runs both ways and includes uncommitted changes, that your edits are never overwritten, that
.claudeand.mcp.jsonare never written on your machine, and that the answer also applies toclaude --cloud. It adds "Your answer applies to every worktree of this repository." - The note Claude gets in the cloud session when your files arrive now says that where Claude created a file at the same path as one of yours, your file is the one there now. Before, it said anything Claude created meanwhile was still there beside your files.
- Three notes Claude could get while waiting are gone: two saying your machine had gone quiet (asleep or offline) and one saying the upload was given up. In their place a length limit of 24 is used when building a quoted list.
Why
You are asked before a folder is kept in sync and told what will and will not be written locally. Inside the cloud session, Claude is told plainly that a file it made may have been replaced by yours at the same path, so it does not assume its own version survived.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear which remote switch controls whether this attach-and-sync path is available.