{"version":"2.1.321","anchor":"bash-command-name-normalization-extended-to-cp-and-mv","canonical_anchor":"bash-command-name-normalization-extended-to-cp-and-mv","heading":"cp and mv are recognised as tee is, whatever their case or .exe suffix","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bash-command-name-normalization-extended-to-cp-and-mv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### cp and mv are recognised as tee is, whatever their case or .exe suffix\n\nClaude Code now recognises cp and mv in shell commands regardless of letter case or a .exe ending, as it already did for tee\n\n**Unclear.** Which checks rely on this matching for cp and mv is not settled.\n\n**What**\n\nWhen Claude Code looks at a shell command, it tidies the command name before matching it, ignoring letter case and a trailing .exe. This used to apply only to tee. It now also applies to cp (copy files) and mv (move files), so `CP`, `cp.exe` and `cp` are treated alike.\n\n**Why**\n\nThis likely affects how cp and mv are matched in permission or safety checks, so a different spelling of the command is not treated as a different command.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}