Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.277 ·

Policy checks can now fail open when a compliance verdict can't be reached

A new failOpenVerdict signal lets certain org-policy checks proceed when the compliance verdict service is unreachable

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaCompliancewhat it touches
KindInternal Changesin v2.1.277,
Group of 2 Under the hood No documentation found

A new failOpenVerdict signal lets certain org-policy checks proceed when the compliance verdict service is unreachable

What

Org-policy compliance checks now have a fail-open path for when the system that decides compliance verdicts is unreachable:

  • A new failOpenVerdict boolean is tracked in the session's policy-limits cache and updated whenever replaceSessionCache or hint updates run.
  • The cache also emits a new heldStartSignal on every emitVerdictChanged() call, separate from the verdict-changed signal itself.
  • When the verdict service is unreachable and the identity that settled without a verdict matches the current principal, certain otherwise-denied compliance keys (such as HIPAA-related ones) become allowed again, unless the required HIPAA evidence hasn't been loaded or can't be read.

Why

This prevents a temporarily unreachable compliance-verdict service from blocking users outright, while still requiring the right evidence to be present before allowing HIPAA-related actions through the fail-open path.

Read from
Names in the bundlefailOpenVerdict
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 doubtThe finding does not say what triggers `failOpenVerdict` to be set or what user-visible effect fail-open behavior has.

See this entry in the whole of v2.1.277 →

Feedback