Under the hood
Useful2 Signal3
Sync now treats a refusal as a distinct result and tracks credentials per file during pushes.
What's wrong with this entry?
Anonymous. No account, no email.
What
Sync call paths were rewired so that a refusal is a first-class result alongside failed and deferred, worker push counts kept credentials separately, the file listing pass takes clean-filter blob ids and a cancellation signal, and the sync-start notice branch was restructured.
Evidence
dir_sync_worker_push_credential_kept
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.239
CLAUDE_CODE_DIR_SYNC_GITselects a git-based engine for cloud file syncBoth mention directory
-
v2.1.239
Directory sync skips files under a git content filter
Both mention directory
-
v2.1.239
Deleted files in a synced directory go to a session trash instead of being unlinked
Both mention directory