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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Dangerous always-allow rules are set aside rather than carried

Under the hood
Useful3 Signal4
Permissions

Always-allow rules matching a dangerous pattern are held aside inactive rather than applied.

What

Permission state now pulls rules matching the dangerous pattern out of the active always-allow list into a separate held list, with a path to put them back, so a session can carry those rules without them taking effect.

Details
  • A companion table records which parts of a session's configuration are stripped this way (allowed_tools, avoid_prompts, permission_mode, working_directory) and which are kept as-is.
Evidence

strippedDangerousRules

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.234 →