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 #84

Claude Code v2.1.223 ·

Permission circuit breakers now have a capability table

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

You'll notice 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,
ImprovementsSection of the release
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.

Read from
Names in the bundlebypassPermissions
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