{"version":"2.1.284","anchor":"windows-file-identity-check-treats-more-inode-values-as-unus","canonical_anchor":"windows-file-identity-check-treats-more-inode-values-as-unus","heading":"More placeholder file numbers are treated as unusable when identifying files","tier":"internal","area":"File Operations","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/windows-file-identity-check-treats-more-inode-values-as-unus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### More placeholder file numbers are treated as unusable when identifying files\n\nWhen identifying a file by its device and inode numbers, Claude Code now ignores more placeholder inode values, including -1 and 2^64\n\n**Unclear.** Whether this applies only on Windows, and which features rely on this check, is not known.\n\n**What**\n\nClaude Code can tell whether two paths are the same file by pairing a device number with an inode number, a per-file number the filesystem assigns. Some filesystems report a placeholder instead of a real inode number, and Claude Code then does not use it to identify the file.\n\nThe set of placeholders it recognises is larger now:\n\n- 0\n\n- -1\n\n- 0xffffffffffffffff\n\n- 2^64\n\nBefore, only 0 and 0xffffffffffffffff were recognised.\n\n**Why**\n\nOn filesystems that report placeholder numbers, such as some network or Windows drives, different files are less likely to be mistaken for the same file.\n\n- Area: File Operations\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}