Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

A broader classifier for destructive shell commands

A broader detector for destructive shell commands exists, but nothing visibly uses its verdict.

Nothing to try yet In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PermissionsArea: what it touches
In DevelopmentKind: in v2.1.242,
What probably matters to youSection of the release

A destructive-command scorer that recurses into sh -c and eval is present with no visible consumer.

What

A new module scores Bash commands as destructive, covering cases that simple pattern matching misses, and recursing into sh -c, eval and backtick subcommands. It carries no flag of its own, and where its verdict is consumed is not visible in the added code, so it may not affect any prompt you see yet.

Details
  • Flags rm, git reset, clean, checkout, restore and stash written with quoting or brace expansion, git push with force-like refspecs or --delete, find -delete, shred, git clean -f without a dry run, xargs and -exec wrappers around those, and git -c alias..
  • Strips wrapper prefixes such as sudo, env, nice, timeout, command and busybox, splits pipelines while ignoring redirections and VAR= assignments, and re-checks nested commands up to a depth limit.
  • Input that is too long or nested too deeply is treated as risky by default.
Evidence

/(^|[;&|\n(][ \t]*)shred\s/`

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →

Feedback