{"version":"2.1.281","anchor":"file-sync-skip-reason-for-files-blocked-by-host-config-and","canonical_anchor":"file-sync-skip-reason-for-files-blocked-by-host-config-and","heading":"File sync: skip reason for files blocked by host config, and a --cloud hint that says only commits upload","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/file-sync-skip-reason-for-files-blocked-by-host-config-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### File sync: skip reason for files blocked by host config, and a --cloud hint that says only commits upload\n\nFile sync now reports files skipped because of host config, and the `--cloud` fallback hint says only commits will upload\n\n**What**\n\n`--cloud` starts a cloud session, a Claude Code session that runs on Anthropic's servers instead of your machine. File sync copies your local files into it.\n\nThe list of files file sync skipped has a new category, `hostConfig`, for files blocked by host configuration. This is also counted in telemetry as `skipped_host_config`.\n\nWhen `--cloud` cannot sync because the host configuration makes files unreadable, the fallback hint now offers \"to upload this branch's commits without file sync (uncommitted file contents stay here)\". Other failures keep the older wording about \"branch and tracked changes\".\n\n**Why**\n\nIn this case only committed work reaches the cloud session. Changes you have not committed stay on your machine, and the hint now says so."}