{"version":"2.1.295","anchor":"plugin-hook-dispatch-carries-origin","canonical_anchor":"plugin-hook-dispatch-carries-origin","heading":"Plugin hooks now receive where an event came from","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/plugin-hook-dispatch-carries-origin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Plugin hooks now receive where an event came from\n\nEvents sent to plugin hooks, such as permission checks on tools, now include where they came from\n\n**What**\n\nPlugins are add-on packages that extend Claude Code, and hooks are points where a plugin's code is called. Events passed to plugin hooks, including the permission check for a tool, now carry where the event came from. The event details are also put together before the hooks run. A plugin can still only make a tool's permission stricter, never looser.\n\n**Why**\n\nThis lays groundwork for telling hooks apart by where they came from. Nothing about what plugins are allowed to do has loosened.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}