{"version":"2.1.304","anchor":"plugin-seeding-gate-now-depends-on-a-new-plan-based-check","canonical_anchor":"plugin-seeding-gate-now-depends-on-a-new-plan-based-check","heading":"Default plugin setup now depends on whether the account is on a Pro or Max plan","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/plugin-seeding-gate-now-depends-on-a-new-plan-based-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Default plugin setup now depends on whether the account is on a Pro or Max plan\n\nWhether Claude Code sets up plugins by default now also checks for a Pro or Max plan and an empty remote settings response\n\n**Unclear.** Which plugins are affected, and what a Pro, Max, Team or Enterprise user now sees differently, is not shown.\n\n**What**\n\nClaude Code has a step that decides whether to set up plugins for an account by default when neither the host program nor a managed setting supplies them. That decision now includes a new check, which requires all of these:\n\n- the account's plan is Pro or Max\n\n- the remote settings response came back empty\n\n- the remote settings request has been answered\n\nBefore, this step had no plan check. A related check that previously returned true for Team or Enterprise accounts now returns false when a second plan value is also Team or Enterprise.\n\n**Why**\n\nIn practice, which accounts get plugins set up by default can now differ when the remote settings fetch returns nothing.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}