The retention sweep is the routine that clears out old session data. When it cleans a session folder, it now empties that checkout's trash first and counts what it removed and any errors. If newer trash is being kept, one entry is cut down to just its git objects/info/alternates chain instead of being deleted. A git alternates file points to another place where git stores shared data. Before, every non-reserved entry was deleted outright. The sweep also gains three further cleanup steps.
The history prune still depends on the server setting tengu_hipaa_history_retention_prune, which is on unless it is switched off remotely.
This stops the cleanup from breaking a synced checkout whose git alternates still point into the session folder.
tengu_hipaa_history_retention_prune On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.283: on
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.283. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear what the three new cleanup steps remove, or which entry is kept.