{"version":"2.1.309","anchor":"bash-read-only-analysis-now-treats-the-print-builtin-as-ne","canonical_anchor":"bash-read-only-analysis-now-treats-the-print-builtin-as-ne","heading":"Some print commands are no longer treated as safe read-only commands","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/bash-read-only-analysis-now-treats-the-print-builtin-as-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Some `print` commands are no longer treated as safe read-only commands\n\nClaude Code's Bash safety check now has rules for `print`, and certain argument shapes make it ask for permission instead of running automatically\n\n**Unclear.** It is unclear whether `print` counted as read-only at all before, so plain `print` commands may be newly allowed or simply unchanged.\n\n**What**\n\nClaude Code checks shell commands to decide whether they only read things and can run without asking you. That check now has its own rules for the shell's `print` command, next to the existing rules for `jobs` and `set`. A `print` command is not treated as read-only when it has any of these:\n\n- an argument that looks like a flag or starts with `$`\n\n- a quote escaped with a backslash\n\n- glob characters, such as `*`, outside quotes\n\n- an argument matching a particular pattern Claude Code looks for\n\n**Why**\n\nThis is a permission tightening. Some `print` commands that used to run without a prompt may now ask for your approval 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"}