Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Stricter shell command checks with a new runsTextHeld option

Shell command safety checks gain a runsTextHeld option, stricter Python -P/-I checks and parsing fixes for run, foreach, -x, --exec and -s

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

Unclear Nothing says when the stricter check is switched on.

What

Before Claude Code runs a shell command, it analyses the command to decide whether it is safe to run without asking you. Several of these checks changed.

  • A new option, runsTextHeld, is added to the command analysis. It is on unless explicitly set to false, and sits next to other checks such as forNameDo and rubyAttachedPattern.
  • For Python commands run with -P or -I, when runsTextHeld is set, code passed with -c that mentions exec, eval or execfile is flagged, as are programs fed in through standard input. Before, -P or -I ended the check with nothing further examined. Other interpreters keep their existing behaviour.
  • The part that reads command prefixes for run, foreach, -x and --exec now looks at the correct list of words.
  • The shell -s check now tests a path with a helper instead of only checking whether it starts with /, ~ or $.

Why

These changes affect whether certain commands are run automatically or need your approval. Some Python commands that previously passed may now ask for permission.

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 doubtNothing says when the stricter check is switched on.

See this entry in the whole of v2.1.314 →

Feedback