{"version":"2.1.238","anchor":"zsh-cmd-process-substitution-no-longer-takes-the-fast-permis","canonical_anchor":"zsh-cmd-process-substitution-no-longer-takes-the-fast-permis","heading":"zsh =(CMD) process substitution no longer takes the fast permission path","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/zsh-cmd-process-substitution-no-longer-takes-the-fast-permis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### zsh `=(CMD)` process substitution no longer takes the fast permission path\n\nZsh `=(cmd)` process substitution is now treated as too tricky to auto-approve, so permissions ask.\n\n**What**\n\nCommands using zsh's `=(CMD)` process substitution are now classified as too complex to analyse, so they fall out of the fast permission path and are handled conservatively instead of being misread.\n\n**Details**\n\n- Applies to text starting with `=(` inside `[[ ]]` tests, and to regex operands containing an unquoted `=(` after a start, `|`, `||` or `&&` boundary.\n- A new scanner tracks quoting, escaping and paren depth to spot the construct.\n- Unconditional in the command analyser.\n\n**Evidence**\n\n`contains zsh =(CMD) process substitution`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}