A desktopSessionCleanupPeriodDays setting and release-marker logic are present; nothing shows it running.
What
Cleanup code reads a desktopSessionCleanupPeriodDays setting, where 0 disables it, looks for a per-transcript release marker file, and decides between releasing the session for cleanup now or holding it for a grace period based on whether the marker says the session was deleted or archived.
Details
Evidence
var U = ".desktop-released.json"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundledesktopSessionCleanupPeriodDays
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up desktopSessionCleanupPeriodDays, on Configure server-managed settings.
* An invalid `cleanupPeriodDays` or `desktopSessionCleanupPeriodDays` value stays in the cached copy and is never applied.server-managed-settings see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up desktopSessionCleanupPeriodDays, on Configure server-managed settings.
Anthropic's release notes agree
Fixed Claude Desktop and Cowork sessions disappearing after 30 days: the transcript cleanup now keeps desktop-written sessions while they…
The name it cites is new in this build
New in this build: desktopSessionCleanupPeriodDays