{"version":"2.1.288","anchor":"bash-permission-cd-compound-read-check-refactored-with-a-ne","canonical_anchor":"bash-permission-cd-compound-read-check-refactored-with-a-ne","heading":"Commands that change folder and only read files can skip the permission prompt","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/bash-permission-cd-compound-read-check-refactored-with-a-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Commands that change folder and only read files can skip the permission prompt\n\nA new check allows `cd && read-only command` without asking when the folder is a plain path, reads stay in allowed paths and output goes only to \/dev\/null\n\n**Unclear.** It is not known whether the new allow check is used yet.\n\n**What**\n\nClaude Code asks for permission before running some shell commands. It has a new check for commands that change folder with `cd` and then only read files. Such a command is allowed when:\n\n- The `cd` target is written out as a plain path.\n\n- Every file read stays inside the paths you allowed.\n\n- Any output redirection goes only to `\/dev\/null`.\n\nThe message shown when a command reads a file by a relative path after `cd` is also shorter. It now says such a read can't be checked against the keys and sign-in files this computer keeps.\n\n**Why**\n\nThis may mean fewer permission prompts for simple commands such as `cd src && ls`.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}