{"version":"2.1.295","anchor":"plugin-hooks-are-tagged-personal-when-the-plugin-is-a-person","canonical_anchor":"plugin-hooks-are-tagged-personal-when-the-plugin-is-a-person","heading":"Hooks from personal plugins are now marked as personal","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-hooks-are-tagged-personal-when-the-plugin-is-a-person","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Hooks from personal plugins are now marked as personal\n\nHooks that come from a plugin Claude Code treats as personal now carry a personal marker\n\n**Unclear.** What makes a plugin count as personal, and what the marker changes, is not known.\n\n**What**\n\nA hook is a command or script that runs automatically at a set point, such as before a tool runs. Plugins, which are add-on packages for Claude Code, can bring their own hooks. When Claude Code collects those hooks, each one now carries a personal marker if its plugin passes a check for being a personal plugin. Before, hooks from plugins had no such marker.\n\n**Why**\n\nThis suggests plugins are now sorted into personal ones and others, which could affect how their hooks are trusted or reported.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}