{"version":"2.1.248","anchor":"plugin-sync-gets-per-account-buckets-and-defers-deletions-wh","canonical_anchor":"plugin-sync-gets-per-account-buckets-and-defers-deletions-wh","heading":"Plugin sync gets per-account buckets and defers deletions while plugins are loaded","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plugin-sync-gets-per-account-buckets-and-defers-deletions-wh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plugin sync gets per-account buckets and defers deletions while plugins are loaded\n\nPlugin syncing gets per-account storage and won't delete a plugin loaded in your session.\n\n**What**\n\nPlugin syncing now uses the same per-account storage directory and quarantine behaviour as skills, and it no longer deletes plugin directories while the synced plugin set is loaded in the current session. Those removals are recorded and counted, then applied later, so a plugin cannot be deleted out from under a running session.\n\n**Details**\n\n- If no storage bucket resolves, the round returns early; if the bucket directory exists but is not marked for that account, it is moved to a trash root first.\n- Deferral is driven by session state (whether the synced plugin set is currently open), not by a feature flag, and is cleared when that set closes. A log line carries the deferred-removal count.\n- Downloads can now carry a version number that overrides the recorded plugin entry.\n\n**Evidence**\n\n`plugins_sync_removal_deferred_loaded`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}