Source Intelligence
Follow Discord

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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Permission circuit breakers now have a capability table

You'll notice
Useful3 Signal0
Permissions

Peer-machine isolation prompts now still appear even when you're running in bypass-permissions mode.

bypassPermissions
What

The four circuit-breaker kinds are described by a table of two booleans consumed by new predicates, replacing hard-coded special cases. isolatePeerMachines prompts now survive bypassPermissions mode, and they no longer route through classifier approval.

Details
  • kinds covered: dangerousRemoval, backgroundOperator, suspiciousWindowsPath, isolatePeerMachines
  • the table holds bypassImmune and classifierRouted per kind
  • previously bypass-permissions immunity was hard-coded to dangerousRemoval, and classifier routing applied to every circuit breaker
  • backgroundOperator and suspiciousWindowsPath keep classifier-approval routing
Evidence

bypassImmune

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.223 →