Claude Code v2.1.281 ·
Windows CONIN$/CONOUT$ names rejected as path segments and working names
CONIN$ and CONOUT$ are now rejected as parts of file paths and as working names, ignoring case, extension and trailing spaces
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WindowsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
CONIN$ and CONOUT$ are special names on Windows that refer to the console rather than to files. They are now rejected in two places:
- As a part of a file path, alongside the other names already treated as unsafe on Windows.
- As a working name, where they fail with
WORKING_NAME_NOT_PLAIN.
The match ignores upper or lower case, any file extension and trailing spaces, so conout$.txt is caught too.
Why
A folder or file with one of these names does not behave like an ordinary file on Windows, so these names are now stopped before they are used.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what a working name is used for.
See this entry in the whole of v2.1.281 →
