{"version":"2.1.280","anchor":"symlinks-now-reported-as-their-own-irregular-file-reason","canonical_anchor":"symlinks-now-reported-as-their-own-irregular-file-reason","heading":"Symlinks now reported as their own \"irregular\" file reason","tier":"notice","area":"File Handling","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/symlinks-now-reported-as-their-own-irregular-file-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Symlinks now reported as their own \"irregular\" file reason\n\nFile-access errors now report symlinks specifically as \"a link\" instead of a generic irregular-file message\n\n**What**\n\nWhen Claude Code checks whether a file path is usable and finds it isn't a plain file, it now distinguishes symbolic links from other cases. A symlink is now reported with the reason `\"a link\"` instead of the generic message used for other irregular files.\n\n**Why**\n\nThis gives a clearer, more specific explanation when a tool can't use a path because it's a symlink, rather than lumping it in with other unusable file types.\n\n- Area: File Handling\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}