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_fetchandallow_design_syncactions; if the check fails, the policy verdict returnsorg_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-blockingallow_web_fetch/allow_design_syncregardless 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.
tengu_tranquil_crescent Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.275: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you
placeholder