Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Delete-command checks now look again at commands that set variables

The check on inline shell commands runs a second pass for commands starting with export, declare, typeset, readonly or local

You'll notice Improvements
JSON All of v2.1.311
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.311,
ImprovementsSection of the release
What

Claude Code checks inline shell commands, the terminal commands it writes and runs for you, and can ask you before running ones that delete files. That check now runs a second pass when the command uses one of these words, which set shell variables:

The Bash permission checks also gain two new reasons for a decision, assigned-variable and loop-later-pass. Both are counted as results of reading the command without running it.

Setting the CLAUDE_CODE_DISABLE_INLINE_SHELL_RM_PROMPT environment variable turns this check off.

Why

Permission checks on commands that set variables, and on commands with loops, now look more closely, so a delete hidden behind a variable is more likely to be caught before it runs.

See this entry in the whole of v2.1.311 →

Feedback