{"version":"2.1.317","anchor":"bash-parser-option-to-allow-backslash-escaped-blanks","canonical_anchor":"bash-parser-option-to-allow-backslash-escaped-blanks","heading":"Shell command checks gain an option for backslash-escaped spaces","tier":"soon","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bash-parser-option-to-allow-backslash-escaped-blanks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Shell command checks gain an option for backslash-escaped spaces\n\nThe shell command checker has an option, off by default, that changes how it rejects commands with backslash-escaped spaces\n\n**What**\n\nBefore running a shell command, Claude Code analyses it and rejects some forms, including commands that contain backslash-escaped whitespace (a space written as `\\ `). That rejection used to rely on a single pattern. There is now an option that switches it to a different pattern. The option is off by default.\n\n**Why**\n\nWhen the option is used, it could change which shell commands are approved without asking you.\n\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}