Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Bash read-only check now accepts timeout-wrapped commands and which

Commands wrapped in timeout, and the which command with known flags, can now pass the Bash read-only check without a permission prompt

Group of 2 You'll notice Improvements
JSON All of v2.1.319
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash SafetyArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release

Unclear It is not clear what condition turns the unwrapping on, so whether it is active by default.

What

Claude Code runs a read-only check on shell commands. A command that passes is treated as safe and can run without asking for your permission. This release lets more commands pass that check:

  • timeout <N>[smhd] wrappers: a leading wrapper such as timeout 10 is stripped off, and the command inside it is checked instead. The unwrapping runs only when an internal check (F6e()) passes. It is not done for [[, alias, cd, help, history or type. If stripping the wrapper changes the first word of the command, the command is rejected.
  • which: now counts as a safe read-only command when it uses only the allowed flags -a, -s, --all, --skip-dot, --version and --help. Any other flag, or an argument the check marks as dangerous, makes it fail. Before, which was not on the safe list at all.

Why

Commands such as timeout 10 ls or which python may stop asking for permission. Anything outside these narrow rules still goes through the normal permission prompt.

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 what condition turns the unwrapping on, so whether it is active by default.

See this entry in the whole of v2.1.319 →

Feedback