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.315,
ImprovementsSection of the release
What
Before running a shell command, Claude Code checks it for risky patterns. Until now these checks flagged only paths written out literally that were relative or inside the working directory, which is the folder Claude Code is working in. They now also flag values that could name a file in that folder. One example is a variable set to a relative value. Another is a relative path that follows a variable.
The extra check covers:
environment variable assignments at the start of a command
git -c options
the --shell option of su and runuser
A command flagged this way gives the reason "which may name a file in the working directory".
Why
Some commands that build a path from a variable were allowed before. They may now stop and ask for your permission, or be held back.
