Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

A broader classifier for destructive shell commands

Not switched on
Useful2 Signal4
Permissions

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

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 →