{"version":"2.1.265","anchor":"windows-reserved-name-protection-extended-to-generic-identif","canonical_anchor":"windows-reserved-name-protection-extended-to-generic-identif","heading":"Windows-reserved-name protection extended to generic identifier sanitizer","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/windows-reserved-name-protection-extended-to-generic-identif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Windows-reserved-name protection extended to generic identifier sanitizer\n\nThe general-purpose name sanitizer now avoids producing Windows-reserved names like CON or NUL\n\n**What**\n\nClaude Code's general-purpose function for cleaning up identifiers, such as those used for artifact or file names, now checks whether the cleaned-up result matches a name Windows reserves for devices (`CON`, `PRN`, `AUX`, `NUL`, `COM1`-`COM9`, `LPT1`-`LPT9`). If it does, an underscore is added to the front of the name.\n\n**Why**\n\nWindows treats these names specially and can fail to create a file or folder with one of them, so this prevents Claude Code from generating an identifier that would break on Windows.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}