{"version":"2.1.295","anchor":"command-substring-matcher-no-longer-collapses-whitespace","canonical_anchor":"command-substring-matcher-no-longer-collapses-whitespace","heading":"Matching a command inside a longer command now respects spacing","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/command-substring-matcher-no-longer-collapses-whitespace","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Matching a command inside a longer command now respects spacing\n\nLooking for one command inside a longer command line no longer ignores extra spaces, so commands that differ only in spacing stop matching\n\n**Unclear.** It is not established whether this check is used for permission rules.\n\n**What**\n\nClaude Code has a check that looks for one shell command inside a longer command line, treating spaces and characters such as `;`, `&`, `|`, brackets and `<` `>` as boundaries between words. Before, it squeezed runs of spaces and tabs down to single spaces in both strings before comparing. It now compares the text exactly as written, so two commands that differ only in spacing no longer match.\n\n**Why**\n\nIf this check is used for permission rules, those rules become stricter: a command typed with unusual spacing may no longer match a rule written with normal spacing.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}