{"version":"2.1.321","anchor":"powershell-permission-checks-harden-against-unicode-lookalik","canonical_anchor":"powershell-permission-checks-harden-against-unicode-lookalik","heading":"PowerShell commands with lookalike characters that could reach network paths now need approval","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/powershell-permission-checks-harden-against-unicode-lookalik","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### PowerShell commands with lookalike characters that could reach network paths now need approval\n\nOn Windows, PowerShell arguments that could become network or device paths after character conversion now require your approval\n\n**What**\n\nOn Windows, Claude Code checks PowerShell commands before running them to see whether an argument points at a network path (a UNC path, an address like `\\\\server\\share`) or a device. Before, this was a single pattern check. It now asks for your approval in two further cases:\n\n- An argument that could name a network or device path once Windows converts its characters, for example fullwidth slashes that look like ordinary ones.\n\n- An argument that may be read as a network (UNC) path, which could trigger network requests.\n\nThese checks apply on Windows only.\n\n**Why**\n\nLookalike characters could previously slip past the network-path check, because Windows turns them into ordinary ones only after the check has run. These cases now stop and ask instead of running unprompted.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}