{"version":"2.1.311","anchor":"bash-output-redirection-deny-check-runs-a-pre-pass-for-targe","canonical_anchor":"bash-output-redirection-deny-check-runs-a-pre-pass-for-targe","heading":"Extra permission check for shell commands that write output to files","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-output-redirection-deny-check-runs-a-pre-pass-for-targe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Extra permission check for shell commands that write output to files\n\nBefore a shell command runs, Claude Code now checks more of its redirects to files and can refuse it or ask you first\n\n**Unclear.** Which redirect targets the new pass covers is not known.\n\n**What**\n\nA redirect is the part of a shell command, such as `>`, that sends the command's output into a file. Before running a shell command, Claude Code checks it against your permission rules. It now runs an extra pass over the command's redirects whose targets meet a certain test:\n\n- if any redirect is denied, the command is refused at once\n\n- if a safety check says you should be asked, that is recorded along with its details\n\nPreviously this pass over redirects only ran when Claude Code already had a list of redirects to check against deny rules.\n\n**Why**\n\nThis could change which shell commands that write to files are refused outright or stop to ask you first.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}