{"version":"2.1.265","anchor":"bash-permission-check-now-lets-a-bare-cd-plus-further-sa","canonical_anchor":"bash-permission-check-now-lets-a-bare-cd-plus-further-sa","heading":"Bash permission check now lets a bare 'cd <safe-subdir>' (plus further safe commands) skip the outside-working-directory block","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-permission-check-now-lets-a-bare-cd-plus-further-sa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash permission check now lets a bare 'cd <safe-subdir>' (plus further safe commands) skip the outside-working-directory block\n\nA bare `cd ` followed by other safe commands no longer triggers the outside-working-directory permission check\n\n**What**\n\nWhen Claude Code checks whether a bash command needs extra permission because it runs outside your working directory, it now recognizes a specific safe pattern: a compound command (several commands chained together) that starts with `cd`, `chdir`, or `pushd` to a plain relative directory name. The directory can't contain wildcards, environment variables, `..`, or other shell special characters, and it must already be a directory you're allowed to read. Every command chained after it must also be safe and already permitted.\n\nWhen all of that holds, Claude Code skips the extra \"outside working directory\" permission prompt entirely.\n\n**Why**\n\nThis cuts down on unnecessary permission prompts for a common, harmless pattern: changing into a subdirectory you already have access to and then running further already-permitted commands there. It only applies on non-Windows systems.\n\n- Area: Permissions\n- Names: `cd`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}