Windows device paths and network automount roots are now refused in more places, like memory files and edits.
What's wrong with this entry?
Paths in Windows NT object-namespace form (\??\, GLOBALROOT, DosDevices, Device) and network automount roots (/net/<host>, /Network/) are now rejected alongside UNC shares when loading memory files, applying edits, adopting a remote session's working directory, resuming a session home, and resolving a workflow script path.
- The workflow error text was broadened to name all three shapes.
Network (UNC, NT-namespace, or automount) paths are not allowed for workflow scriptPath
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Look-alike character table widened, and ASCII letters protected
Both mention path safety
-
v2.1.235
Remote settings can be primed from local storage instead of probing disk
Both mention path
-
v2.1.242
Claude checks a checkout's git configuration before running git in it
Both mention safety