{"version":"2.1.311","anchor":"bash-redirect-check-treats-0-only-fd-strings-as-stdin-in-saf","canonical_anchor":"bash-redirect-check-treats-0-only-fd-strings-as-stdin-in-saf","heading":"Read-only command check treats 00<file redirects like 0<file","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bash-redirect-check-treats-0-only-fd-strings-as-stdin-in-saf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Read-only command check treats `00<file` redirects like `0<file`\n\nClaude Code now treats input redirects written with several zeros, such as 00\n\n**What**\n\nBefore running a shell command without asking, Claude Code checks whether the command only reads things. Part of that check looks at input redirects. In `0<file`, a file is fed into the command's standard input, which is the input stream numbered 0. The check used to accept only the number `0` there. It now also accepts any run of zeros, such as `00<file` or `000<file`, and treats them the same way. This only applies when a further condition in the check also holds.\n\n**Why**\n\nCommands written with these redirects can now count as read-only, which can mean fewer permission prompts for them.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}