{"version":"2.1.311","anchor":"output-redirection-check-collects-all-targets-and-prefers-sa","canonical_anchor":"output-redirection-check-collects-all-targets-and-prefers-sa","heading":"Output redirect checks now look at every target before asking","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/output-redirection-check-collects-all-targets-and-prefers-sa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Output redirect checks now look at every target before asking\n\nWhen a command writes to several files, Claude Code now checks every target and asks about one needing a safety check first\n\n**Unclear.** Whether redirects to \/dev\/null still go through without a prompt is not shown.\n\n**What**\n\nA redirect is the part of a shell command that sends output into a file, such as `> out.txt`. Before running a command, Claude Code checks where its redirects write. It used to stop at the first target it would not allow. It now looks at every target and then picks which question to ask you:\n\n- If any target needs a safety check, a stricter prompt for risky actions, Claude Code asks about that one straight away\n\n- Otherwise it asks about the first target that needs your approval\n\nThe early step that skipped redirects to `\/dev\/null`, a place that throws output away, is no longer part of this check.\n\n**Why**\n\nWhen several redirects in one command are blocked, a prompt that needs a safety check now comes before any other.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}