What
The file sync that copies your project's files to a cloud session and brings changes back (called dir-sync) was reworked.
- A first upload that was cut off is now announced again. When the session is created and an announcement token already exists, sync reuses it instead of always making a new one, and there is a new re-announce step when the first send fails.
- A new held message explains that the cloud session has none of the project's files yet.
- Pulling changes back can now follow an earlier chain of uploads (
getLink) before the latest bundle. - A new warning says when the cloud session's file record is in a newer sync format than your version of Claude Code can read.
- A failure to create the lock folder now has its own message, and there is a new message for when git cannot read HEAD (the commit your project is currently on).
Why
Before, most of these cases fell back to one general message saying the cloud session's file record could not be read. Now a restart or retry during the first upload is handled, and when sync does fail the message says which part went wrong. The members suggest this means fewer cases of a cloud session quietly starting with no files.