{"version":"2.1.309","anchor":"zero-byte-file-check-now-requires-a-single-hard-link","canonical_anchor":"zero-byte-file-check-now-requires-a-single-hard-link","heading":"Empty read-only placeholder files with extra hard links are no longer matched","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/zero-byte-file-check-now-requires-a-single-hard-link","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Empty read-only placeholder files with extra hard links are no longer matched\n\nClaude Code now treats an empty, read-only file as a placeholder only when no other hard link points to it\n\n**Unclear.** It is not clear what Claude Code does with files it treats as placeholders, so the effect on your files is unknown.\n\n**What**\n\nClaude Code checks whether a file is an empty, read-only placeholder. That check now has one more condition: only one name may point to the file. A hard link is a second name for the same file on disk, and an empty file that has one or more of them no longer counts as a placeholder.\n\n**Why**\n\nThe check is narrower now, so fewer files match it.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}