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-breaker permission reasons moved to a registry; isolatePeerMachines is now bypass-immune

Use it now
Useful3 Signal0
Permissions Notable not in their notes

Cross-machine file transfer denials can no longer be bypassed once you enable peer isolation.

isolatePeerMachines
What

Permission code no longer hardcodes a single circuit-breaker name when deciding what cannot be bypassed, and cross-machine isolation denials now survive the bypass path.

Details
  • A table marks each circuit breaker as bypassImmune / classifierRouted: dangerousRemoval, backgroundOperator, suspiciousWindowsPath, isolatePeerMachines. Previously only dangerousRemoval was checked directly.
  • The isolatePeerMachines file-transfer denial now stamps circuitBreaker: "isolatePeerMachines" on its decision reason, which makes it bypass-immune in the multi-cd ask path.
  • The isolatePeerMachines setting still has to be enabled for that breaker to fire at all.
Evidence

isBypassImmuneCircuitBreaker

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 →