You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
What
When Claude deletes or replaces a file in a cloud session, Claude Code moves your local copy of it aside on your machine rather than throwing it away, and tells you so. That notice now adds that your copy is kept there for at least your cleanup period, names the cleanupPeriodDays setting that controls it, and gives the default number of days.
Why
The moved copies are not kept forever. The notice now tells you they are eventually cleaned up and which setting decides when.
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.
Added sinceA small documentation edit on Plugin loading reference touched a line naming cleanupPeriodDays after this was published.| `installed_plugins.set-aside.<date>.<hash>.json` and `installed_plugins.unreadable.<date>.<hash>.kept` | Dated copies Claude Code keeps before it drops install records that no version of Claude Code can use or rebuilds an unreadable `ins…plugins/loadingsee the edit
Confirmed sinceAnthropic's documentation has since written up cleanupPeriodDays, on Deploy managed settings.| Every other key | Takes the value from the highest-ranked source that sets it | `model`, `cleanupPeriodDays` |managed-settingssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up cleanupPeriodDays, on Deploy managed settings.