{"version":"2.1.280","anchor":"files-changed-on-the-users-machine-notice-guards-against","canonical_anchor":"files-changed-on-the-users-machine-notice-guards-against","heading":"\"Files changed on the user's machine\" notice guards against null updatedInPlace","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/files-changed-on-the-users-machine-notice-guards-against","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### \"Files changed on the user's machine\" notice guards against null updatedInPlace\n\nThe 'files changed on disk' notice no longer misfires when the changed-file count is null\n\n**What**\n\nThe message that tells Claude when files changed on disk while it was working now treats a `null` value for the count of files updated in place as \"nothing to report,\" the same as zero or a negative number, instead of only handling zero and negative cases.\n\n**Why**\n\nThis prevents the \"files changed on the user's machine\" notice from being shown or mishandled when the underlying count is missing rather than a real number.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}