{"version":"2.1.242","anchor":"plugin-install-flags-when-new-tools-need-a-refresh-to-take-e","canonical_anchor":"plugin-install-flags-when-new-tools-need-a-refresh-to-take-e","heading":"Plugin install flags when new tools need a refresh to take effect","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plugin-install-flags-when-new-tools-need-a-refresh-to-take-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Plugin install flags when new tools need a refresh to take effect\n\nPlugin installs now flag \"installed but not applied\" when language-server tools change too.\n\n**What**\n\nAfter installing plugins, Claude Code checks whether the change alters the available tools, now including language-server tools as well as added and removed MCP servers. If so, the install message is annotated with \"installed but not applied\" and the app is marked as needing a refresh.\n\n**Details**\n\n- The bookkeeping that records what was warned about or forced moved into a finally block, so it is always written even if the check fails.\n\n**Evidence**\n\n`installed but not applied`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}