{"version":"2.1.301","anchor":"pretooluse-hook-results-carry-hookpluginid","canonical_anchor":"pretooluse-hook-results-carry-hookpluginid","heading":"PreToolUse hook results now record which plugin they came from","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/pretooluse-hook-results-carry-hookpluginid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### PreToolUse hook results now record which plugin they came from\n\nResults from PreToolUse hooks now carry the ID of the plugin that supplied the hook as a separate value\n\n**What**\n\nA hook is a script or command you set up to run automatically at certain points. A `PreToolUse` hook runs before a tool call, which is a request by Claude to use a tool such as editing a file, and it can block that call.\n\nWhen Claude Code reads the result of a `PreToolUse` hook, it now picks out the ID of the plugin the hook came from and keeps it separate, instead of passing it along mixed in with the rest of the result.\n\n**Why**\n\nThis lets Claude Code tell which plugin a hook belongs to.\n\n- Area: Hooks\n- Names: `PreToolUse`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}