Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.223entry #43

Claude Code v2.1.223 ·

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

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

You'll notice Notable Improvements
JSON All of v2.1.223
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.223,
What probably matters to youSection of the release
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.

Read from
Names in the bundleisolatePeerMachinesbypassPermissions
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a permission gap where an agent definition's bypassPermissions mode ignored the org bypass-permissions disable policy

See this entry in the whole of v2.1.223 →

Feedback