{"version":"2.1.282","anchor":"new-warning-when-a-cloud-file-sync-ignore-rule-cannot-be-mat","canonical_anchor":"new-warning-when-a-cloud-file-sync-ignore-rule-cannot-be-mat","heading":"Cloud file sync warns when an ignore rule cannot be applied exactly as written","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-warning-when-a-cloud-file-sync-ignore-rule-cannot-be-mat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud file sync warns when an ignore rule cannot be applied exactly as written\n\nSyncing files to a cloud session now warns when ignore-file rules had to be widened or re-include rules were skipped\n\n**Unclear.** It is not known whether cloud-session file sync is available to everyone or held back for some accounts.\n\n**What**\n\nWhen Claude Code syncs a folder to a cloud session, it follows ignore files (gitignore-style lists of files to leave out). Some rules cannot be matched exactly as written. Claude Code now warns about them, naming the file and line numbers:\n\n- A rule it had to widen is reported with the wider form it is applied as, noting that this leaves out at least what the rule did and possibly more.\n\n- A re-include rule (one starting with `!`) is reported as not applied, so whatever other rules leave out there stays left out.\n\nThe warning lists up to three rules and then a count of the rest, and appears again whenever its wording changes. Claude Code also now says when a broken rule file leaves a whole folder out of sync, and posts a notice once that file no longer keeps the folder out.\n\n**Why**\n\nIf you use cloud sessions with detailed ignore rules, you now learn that sync may be leaving out more than you expect, where before this happened silently.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}