Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
Internal ChangesKind: in v2.1.277,
Internal ChangesSection of the release
What
When a plugin's hooks module (the file defining its custom hooks) doesn't get loaded, Claude Code logs why. Previously the message used a fixed phrasing naming just the plugin and its source; now it uses a generated identifier that names the specific module instead. This applies across all three cases: the rollout flag being off, a duplicate plugin name, and disableAllHooks being set.
Why
More specific log output makes it easier to tell exactly which hooks module was skipped and why, especially for plugins that define more than one.
