Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
Unclear What specific checks use bypassImmune or localProjectionOnly, and what calls these new helpers, is not stated.
What
Two new helper functions were added on top of Claude Code's existing circuit-breaker registry (a mechanism that can disable checks under certain conditions): one checks whether any breaker for a given check has bypassImmune set to true, and the other checks whether one has localProjectionOnly set to true. Both use a shared collector that gathers a check's own circuit-breaker settings plus any additional ones listed under it.
Why
This lets other code ask, for a given check, whether it's immune to being bypassed or whether it should only apply locally rather than being reported elsewhere, which suggests finer control over how individual checks can be overridden or scoped.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat specific checks use bypassImmune or localProjectionOnly, and what calls these new helpers, is not stated.
