{"version":"2.1.289","anchor":"plugin-hook-warning-text-changes-for-unapplied-hooks","canonical_anchor":"plugin-hook-warning-text-changes-for-unapplied-hooks","heading":"Warnings for plugin hooks that were not applied no longer say \"skipped\"","tier":"notice","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/plugin-hook-warning-text-changes-for-unapplied-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Warnings for plugin hooks that were not applied no longer say \"skipped\"\n\nA plugin hook that was not applied now gets a warning reading \" hook: \" instead of \" hook skipped: \"\n\n**Unclear.** When a hook counts as not applied rather than skipped is not stated.\n\n**What**\n\nWhen a plugin hook is not applied, Claude Code's warning now reads `<event> hook: <reason>`, for example naming the event such as `PreToolUse`. A hook is plugin code that runs at a certain moment, such as before a tool runs. Previously the warning said `<event> hook skipped: <reason>`. Other hook warnings still say \"skipped\". Claude Code avoids showing the same warning twice, and the label is now part of how it tells warnings apart.\n\n**Why**\n\nThe wording is more accurate for a hook that was not skipped but simply not applied.\n\n- Area: Plugin Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}