Unclear It is not clear whether folder sync with cloud sessions is available to every user.
What
Claude Code can keep a folder on your computer in step with a cloud session, which is a Claude Code session running on a remote machine. Several parts of that sync changed:
- Bringing Claude's commits from the cloud into your local branch has a new failure case. After two attempts on the same round of changes, you are told that git could not merge Claude's commits into this checkout's index. The index is the staging area git uses to track what goes into the next commit.
- Notices about failed reads and downloads during sync now say the step is tried again with your next message or Claude's next change. They used to say "trying again at the next result".
- A snapshot of your folder is now refused when the repository's git attribute settings were not read, or when a source of those settings makes them unreadable.
Why
If you sync a local checkout with a cloud session, sync problems now come with a specific reason and a clear idea of when the next attempt happens.
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 whether folder sync with cloud sessions is available to every user.