You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release
Unclear It is unclear whether print counted as read-only at all before, so plain print commands may be newly allowed or simply unchanged.
What
Claude 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:
an argument that looks like a flag or starts with $
a quote escaped with a backslash
glob characters, such as *, outside quotes
an argument matching a particular pattern Claude Code looks for
Why
This is a permission tightening. Some print commands that used to run without a prompt may now ask for your approval first.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear whether `print` counted as read-only at all before, so plain `print` commands may be newly allowed or simply unchanged.
