{"version":"2.1.274","anchor":"plugin-sync-now-tolerates-unsettled-remote-managed-plugin-co","canonical_anchor":"plugin-sync-now-tolerates-unsettled-remote-managed-plugin-co","heading":"Plugin sync now tolerates unsettled remote managed-plugin config","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/plugin-sync-now-tolerates-unsettled-remote-managed-plugin-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Plugin sync now tolerates unsettled remote managed-plugin config\n\nPlugin config sync no longer drops managed plugin entries when remote policy settings haven't caught up yet\n\n**What**\n\nWhen Claude Code syncs its `installed_plugins.json` file, it now checks whether a plugin's remote-managed policy has simply not settled yet, and if so, keeps that plugin's managed entry instead of dropping it as orphaned. It logs a specific message, \"Remote managed settings not settled; keeping managed record(s) for...\", in this case.\n\n**Why**\n\nThis avoids incorrectly discarding managed plugin records due to a temporary lag in remote policy settings, which could otherwise cause plugins to appear unmanaged or missing.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}