{"version":"2.1.299","anchor":"path-permission-check-now-compares-inode-identity","canonical_anchor":"path-permission-check-now-compares-inode-identity","heading":"Path permission rules now check that both paths are the same file","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/path-permission-check-now-compares-inode-identity","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Path permission rules now check that both paths are the same file\n\nWhen a path matches a permission rule only indirectly, Claude Code now checks both paths point to the very same file on disk\n\n**Unclear.** What the further condition for operations other than deleting requires is not stated.\n\n**What**\n\nPermission rules can allow Claude Code to work on certain paths. When a path matches a rule but not letter for letter, Claude Code now looks up both the rule's path and the target path. It allows the match only if both point to the same file, meaning the same disk (device) and the same file number the system uses to identify it (the inode). Operations other than deleting must also meet a further condition.\n\nWhen Claude Code reads a file it now also collects that file's device, file number and modification times.\n\n**Why**\n\nThis makes it harder for a shortcut or a second name for a file, such as a symlink, to slip past a path rule.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}