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 ·

Bash approval checks gain a second pass and new reasons for asking

Claude Code's Bash permission check now runs a second pass in some cases and can ask about variables or loops it cannot check in advance

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
2Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release

Unclear It is not clear which parts of this check are new behaviour and which are existing checks reorganised, so it is unclear how often approval prompts change.

What

Before Claude runs a shell command through the Bash tool, Claude Code checks whether the command needs your approval. That check now works in more steps.

  • A second pass runs only when the first pass either triggered or refused.
  • A new reason covers a command that uses a variable set earlier in the same command. It reads: "A variable set in this command can't be checked before it runs".
  • Another reason covers loops: only the first pass of a loop can be checked, and later passes may run something else.
Why

This could change when a shell command asks for your approval, and the new reasons explain why some commands cannot be checked ahead of time.

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 not clear which parts of this check are new behaviour and which are existing checks reorganised, so it is unclear how often approval…

See this entry in the whole of v2.1.311 →

Feedback