Big sync downloads now resume after a token expires mid-transfer instead of restarting.
What's wrong with this entry?
When Claude Code downloads a file directly during a directory sync, a token expiring partway through no longer restarts or corrupts the transfer. Bytes already received are kept, a fresh read token is fetched, and the download resumes from where it stopped.
- New read tokens are only issued while the transfer is actually making progress, so a stuck download cannot loop forever.
- The file's etag is checked to be unchanged between attempts; if the file changed on the server the download does not silently splice two versions.
- A stall timeout parameter was added.
- Giving up produces a warning naming exactly how many bytes of the file had arrived.
dir-sync: direct download gave up after ${A} read tokens at ${O.received} of ${r.size} bytes
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory