{"version":"2.1.321","anchor":"plugin-data-folder-is-set-aside-instead-of-deleted","canonical_anchor":"plugin-data-folder-is-set-aside-instead-of-deleted","heading":"Plugin data can be set aside in a dated folder instead of deleted","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/plugin-data-folder-is-set-aside-instead-of-deleted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Plugin data can be set aside in a dated folder instead of deleted\n\nClaude Code can now move a plugin's data folder into a timestamped `.set-aside` folder rather than deleting it, leaving a marker if anything stays\n\n**Unclear.** When Claude Code sets plugin data aside, and whether it does so by default, is not shown.\n\n**What**\n\nPlugins are add-ons that extend Claude Code, and each can keep its own data folder. Claude Code now has a way to set that folder aside instead of deleting it:\n\n- It moves the folder into a `.set-aside` folder inside `data`, in a subfolder named with the date and time.\n\n- If the whole folder cannot be moved at once, it moves the contents one item at a time.\n\n- If anything is left behind, it writes a marker file named `left-behind.<id>.txt`.\n\n- A separate check lists folders that are holding things and folders that were left behind.\n\n**Why**\n\nRemoving a plugin need no longer destroy its data for good, so you can get it back from the `.set-aside` folder.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}