{"version":"2.1.323","anchor":"plugins-engine-range-check-notice-and-chrome-opt-in-notice","canonical_anchor":"plugins-engine-range-check-notice-and-chrome-opt-in-notice","heading":"Plugins needing another Claude Code version are skipped with a warning","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugins-engine-range-check-notice-and-chrome-opt-in-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugins needing another Claude Code version are skipped with a warning\n\nA plugin that needs a different Claude Code version is now not loaded, with a warning pointing to `\/plugin`\n\n**What**\n\nA plugin can say which Claude Code versions it works with. Several new notices:\n\n- A plugin whose required version does not match yours is not loaded, and a warning says so and points to `\/plugin`.\n\n- Automatic updates for such a plugin are marked as blocked by the version requirement.\n\n- A startup notice appears when your organisation's policy denies Claude in Chrome.\n\n- When a language server (a helper that gives code intelligence for a language) fails to start, a warning is added to the conversation.\n\n**Why**\n\nYou now see why a plugin or the browser extension is not working, instead of it silently doing nothing.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}