What
Paths beginning \??\ (the NT object manager namespace, and spellings that normalise to it) are now treated as suspicious. They trigger the same manual-approval ask as other odd Windows path forms, are rejected by the network-path check, and are caught during general path normalization, which previously only recognised the \\?\ device form.
Details
- The ask text is unchanged: "which contains a suspicious Windows path pattern that requires manual approval", recorded under the circuit breaker name "suspiciousWindowsPath".
- The file-upload guard used by Claude in Chrome inherits the new check and throws on a "suspicious path spelling".
Evidence
/^[\\/]\?\?[\\/]/
Strings lifted out of the shipped bundle, so the claim above can be checked against them.