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

Circuit breakers carry declared traits instead of hard-coded name checks

You'll notice
Useful3 Signal0
Permissions Notable

Peer-machine isolation prompts now survive bypass permissions mode and are never auto-approved.

isolatePeerMachinesbypassPermissions
What

Permission circuit breakers are now described by a trait table, which changes which of them survive bypass mode and which can be auto-approved by the classifier.

Details
  • each breaker maps to { bypassImmune, classifierRouted }
  • dangerousRemoval is both; backgroundOperator and suspiciousWindowsPath are classifier-routed only
  • isolatePeerMachines: { bypassImmune: !0, classifierRouted: !1 }, so peer-machine isolation prompts survive bypassPermissions mode and are never auto-approved by the classifier
  • call sites that tested circuitBreaker === "dangerousRemoval" or just circuitBreaker !== void 0 now consult the traits
  • whether the isolatePeerMachines breaker fires at all is still controlled by the isolatePeerMachines setting
Evidence

isolatePeerMachines: { bypassImmune: !0, classifierRouted: !1 }

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 →