{"version":"2.1.284","anchor":"bash-path-detection-handles-backslash-newline-continuations","canonical_anchor":"bash-path-detection-handles-backslash-newline-continuations","heading":"Shell command checks now spot home-folder paths split across lines","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/bash-path-detection-handles-backslash-newline-continuations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Shell command checks now spot home-folder paths split across lines\n\nClaude Code now joins backslash-continued lines before looking for ~ paths in shell commands, so a split path is still recognised\n\n**What**\n\nIn a shell command, a backslash at the end of a line joins it to the next line. Claude Code now joins such lines before checking a command for paths that start with `~`, which means your home folder. It does the same before checking for variable assignments at the start of a command. A `~\/path` split across two lines is now recognised.\n\n**Why**\n\nBefore, splitting a command across lines could hide a home-folder path from the checks that decide whether a command needs your permission.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}