{"version":"2.1.284","anchor":"same-file-check-can-return-unknown-so-liveness-becomes-i","canonical_anchor":"same-file-check-can-return-unknown-so-liveness-becomes-i","heading":"Unclear file identity now counts as unknown rather than a mismatch","tier":"internal","area":"File Operations","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/same-file-check-can-return-unknown-so-liveness-becomes-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Unclear file identity now counts as unknown rather than a mismatch\n\nWhen Claude Code cannot tell whether two paths are the same file, the result is now reported as indeterminate instead of not live\n\n**Unclear.** What this live or not-live check protects, possibly git worktrees, is not settled.\n\n**What**\n\nClaude Code sometimes compares two paths to see whether they point at the same file, using the inode, the id number a filesystem gives each file. The comparison now has three results: same, different or unknown. When only one of the two paths reports a usable inode, the result is unknown, and the check that relies on it answers \"indeterminate\" instead of \"not live\". Previously it fell back to comparing the paths and gave a firm yes or no.\n\n**Why**\n\nOn filesystems with unreliable inode numbers, Claude Code no longer declares something gone just because it could not confirm the match.\n\n- Area: File Operations\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}