{"version":"2.1.301","anchor":"plugin-sync-turn-start-check-can-be-skipped-via-a-gate","canonical_anchor":"plugin-sync-turn-start-check-can-be-skipped-via-a-gate","heading":"A turn can start without waiting for plugin sync when a remote switch allows it","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/plugin-sync-turn-start-check-can-be-skipped-via-a-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### A turn can start without waiting for plugin sync when a remote switch allows it\n\nAt the start of each turn, Claude Code can now skip waiting for plugin sync if a remotely controlled switch says so\n\n**Unclear.** Which switch allows skipping the wait, and whether it is on by default, is not known.\n\n**What**\n\nAt the start of each turn (one exchange where you send a message and Claude answers), Claude Code checks whether your plugins need to be brought up to date, a step called plugin sync. That check is now split into two steps. One decides whether a sync is due. The other decides whether Claude Code may skip waiting for the sync.\n\nThe skip is controlled by a switch that Anthropic's servers can turn on. If Claude Code cannot read that switch, it does not skip the wait. Before, checking and starting the sync happened together in one step.\n\n**Why**\n\nWhen the switch is on, a turn can begin before plugin sync has finished instead of waiting for it.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}