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

New HIPAA-evidence tracking now gates web-fetch and design-sync policy checks

Claude Code now tracks HIPAA-related evidence per account and can block web-fetch or design-sync access based on it

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPolicy Limitswhat it touches
KindInternal Changesin v2.1.275,
Group of 5 Under the hood

Claude Code now tracks HIPAA-related evidence per account and can block web-fetch or design-sync access based on it

What

  • Session and organization-policy state now track HIPAA-related evidence: whether HIPAA-relevant information has been seen (hipaa_seen), seen but incomplete (hipaa_seen_incomplete), or ruled out (hipaa_ruled_out). This replaces a simpler flat list of "seen identities" with a richer evidence structure that also tracks confirm/refuse timestamps (diskConfirmedAtMs, diskRefusedAtMs) and distinguishes IO failures from content-based unusability.
  • This evidence is now checked before allowing the allow_web_fetch and allow_design_sync actions; if the check fails, the policy verdict returns org_denied, a new failure path that did not exist before.
  • A separate feature gate (tengu_tranquil_crescent) can also force this same check to fail immediately, hard-blocking allow_web_fetch/allow_design_sync regardless of the evidence gathered.

Why

This adds a compliance check so web-fetch and design-sync features can be denied for organizations subject to HIPAA rules until their status is properly established, closing a gap where those actions could otherwise run without that check.

See this entry in the whole of v2.1.275 →

Feedback