{"version":"2.1.323","anchor":"plugin-hooks-load-new-needs-another-claude-code-version-c","canonical_anchor":"plugin-hooks-load-new-needs-another-claude-code-version-c","heading":"Missing managed plugin log names a Claude Code version mismatch as a cause","tier":"notice","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-hooks-load-new-needs-another-claude-code-version-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Missing managed plugin log names a Claude Code version mismatch as a cause\n\nWhen a managed plugin's hooks cannot load, the log now says the plugin or one it needs may require another Claude Code version\n\n**What**\n\nManaged plugins are plugins your organisation sets up for you. When one was never put in place on your computer, the log listed possible causes: its marketplace was not registered, its catalog was not loaded, or it was never fetched. It now adds that the plugin, or a plugin it depends on, may need another Claude Code version. The message about missing hooks, which are scripts a plugin runs at set moments, is also simpler.\n\n**Why**\n\nIt makes the cause clearer when hooks from a managed plugin fail to load.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}