Cloud settings sync leaves unchanged files alone and reports oversized files

What

When you start a cloud session, Claude Code can send settings files from your machine to it. This release changes how those files are written and how failures are reported.

• The part that writes uploaded files takes a new option. With it set, a file already on disk with the same bytes is not written again. A file whose content differs is kept and counted separately.
• New counters record this: unchangedOnDiskCount and keptChangedFileCount, reported in sync telemetry (usage reporting) as unchanged_on_disk_count and kept_changed_file_count.
• A new too_large result marks a failure flagged tooLarge. Before, the only failure results were aborted, failed and timed out.
• New helpers spot files that look like they hold a credential, such as a password or key, and work out a size limit for sending files inline, allowing for base64-style encoding plus 1024 extra.
• The warning shown reads "Settings from this machine were not sent to the cloud session (…)".

Why

Before, the file was always written. Now an existing file is not overwritten when it is identical, and one that differs is kept rather than replaced. If a settings file is too big to send, you get a separate failure that says so.