{"version":"2.1.265","anchor":"bash-path-validation-helpers-gained-an-extra-passthrough-par","canonical_anchor":"bash-path-validation-helpers-gained-an-extra-passthrough-par","heading":"Bash path-validation helpers gained an extra passthrough parameter affecting relative-path-after-cd checks","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-path-validation-helpers-gained-an-extra-passthrough-par","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash path-validation helpers gained an extra passthrough parameter affecting relative-path-after-cd checks\n\nBash safety checks gained a parameter that can skip the 'ask' prompt for reading a relative path after cd\n\n**Unclear.** The finding doesn't specify which call sites now pass the new parameter as true, so it's unclear which real commands actually skip the ask requirement.\n\n**What**\n\nSeveral internal functions that check whether a bash command is safe to run were given a new trailing parameter. When set to true, it skips the requirement to ask for permission before reading a relative path that follows a `cd` in a compound command (like `cd some-dir && cat file.txt`), even when a rule is configured to deny that kind of `Read`.\n\n**Why**\n\nThis changes when Claude Code will pause to ask before reading a file reached via a directory change in the same command, in cases where a deny rule for `Read` is otherwise in place. The finding does not say which callers now pass true for this new parameter, so it's unclear which specific commands are affected in practice.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}