{"version":"2.1.267","anchor":"plugin-hooks-now-report-a-tier-coreprependuser","canonical_anchor":"plugin-hooks-now-report-a-tier-coreprependuser","heading":"Plugin hooks now report a tier (core\/prepend\/user)","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/plugin-hooks-now-report-a-tier-coreprependuser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Plugin hooks now report a tier (core\/prepend\/user)\n\nPlugin hooks now report a tier of core, prepend, or user\n\n**What**\n\nWhen Claude Code looks up plugin hooks (scripts that run automatically at certain points), the result now includes a `tier` field, computed as `\"core\"`, `\"prepend\"`, or otherwise `\"user\"`. Plugin hook metadata now carries `{plugin, tier, hook, generation}` instead of just `{plugin, hook, generation}`.\n\n**Why**\n\nThis lets Claude Code distinguish hooks that are built-in (\"core\"), inserted ahead of others (\"prepend\"), or defined by the user, which likely matters for how hooks are ordered or prioritized when several apply.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}