{"version":"2.1.290","anchor":"redirects-using-fd-variable-assignment-are-now-flagged-too-c","canonical_anchor":"redirects-using-fd-variable-assignment-are-now-flagged-too-c","heading":"Bash redirects like {fd}>file now ask for your approval","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/redirects-using-fd-variable-assignment-are-now-flagged-too-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Bash redirects like `{fd}>file` now ask for your approval\n\nShell redirects that store a file number in a variable, such as `{fd}>file`, are now treated as too complex to run without asking\n\n**What**\n\nBefore Claude Code runs a shell command, it checks the command to decide whether it is safe to run without asking you. It now also treats a redirect whose target is a variable name, such as `{fd}>file`, as too complex to judge. Claude Code asks for your permission before running such a command, and gives the reason that it modifies a shell variable as a side effect.\n\n**Why**\n\nA redirect written this way changes a shell variable as well as sending output to a file. Asking first closes a way for a command to change shell variables without a permission prompt.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}