tengu_hipaa_history_retention_prune
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.257, including the newest one read.
HIPAA-configured organizations get an extra retention pass that prunes stale entries from local history files.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.257.
In the changelogs
4Releases whose published page names tengu_hipaa_history_retention_prune.
-
v2.1.295
Cleanup of old session data now also clears leftover seed-admin folders
The routine that clears old session data now first removes leftover
claude-seed-adminfolders, after checking they are safe to deletegate cited by this entry
-
v2.1.283
Cleanup of old session data keeps what a synced checkout still needs
The routine that clears old session data now empties a checkout's trash but keeps the git links a synced checkout still depends on
gate cited by this entry, found in this entry's text
-
v2.1.259
History retention prune rewritten to a two-pass, integrity-verified streaming scan
History pruning now scans lock-free and verifies the file hasn't changed, deferring the prune instead of erroring if it has.
gate cited by this entry
-
v2.1.257
Optional HIPAA history-retention pruning
HIPAA-configured organizations get an extra retention pass that prunes stale entries from local history files.
gate cited by this entry
Gate readings
4| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.295 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.283 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.259 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.257 read on another version | Not enough to say | no value returned | no value returned | on |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
6| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-12T20:35:04Z | v2.1.302 to v2.1.322 |
| this account | on | 2026-09-10T21:47:12Z | 2026-11-12T20:35:04Z | v2.1.268 to v2.1.322 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-10T00:55:04Z | 2026-10-17T05:10:04Z | v2.1.267 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | on | 2026-09-10T00:55:04Z | 2026-09-10T17:40:05Z | v2.1.267 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
1The earliest release whose published evidence quoted tengu_hipaa_history_retention_prune was v2.1.257, 1 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
60One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.