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.273 ·

New hardBlockUnder tier for tool and compliance policies

Tool and HIPAA compliance settings gain a stricter hardBlockUnder enforcement tier beyond the existing deny list

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

Tool and HIPAA compliance settings gain a stricter hardBlockUnder enforcement tier beyond the existing deny list

What

  • Several HIPAA compliance settings (Memory sync, Projects, Team onboarding, Peer messaging) now carry a hardBlockUnder: ["hipaa"] property alongside the existing deniedUnder, marking a stricter enforcement tier separate from ordinary denial.
  • A new lookup table is built by collecting each tool's hardBlockUnder configuration, pairing each named threshold with the tool it applies to. The related deny-on-cache-miss list was also simplified to be built directly from each tool's configuration instead of a fixed base list plus filtering.

Why This adds a stricter "hard block" enforcement level on top of the existing deny mechanism, letting specific settings and tools be blocked outright under certain compliance thresholds (like HIPAA) rather than just denied through the normal path.

Read from
Names in the bundlehardBlockUnder
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 conditions or values `hardBlockUnder` actually enforces isn't given in the finding.

See this entry in the whole of v2.1.273 →

Feedback