{"version":"2.1.288","anchor":"plugin-hook-forwarding-refusal-message-moved-to-a-shared-con","canonical_anchor":"plugin-hook-forwarding-refusal-message-moved-to-a-shared-con","heading":"Message about plugin hooks on another machine is now stored in one place","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plugin-hook-forwarding-refusal-message-moved-to-a-shared-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Message about plugin hooks on another machine is now stored in one place\n\nThe error message about plugin hooks running on another machine is now kept in one place, with no change in behaviour\n\n**Unclear.** Whether the wording of the message itself changed was not checked.\n\n**What**\n\nClaude Code can print an error message saying a plugin's hooks run on another machine. Hooks are your own commands that run automatically at set moments. That message used to be written out separately in each place it appeared and is now kept in one place. The logic around it is unchanged.\n\n**Why**\n\nThis should make no difference to what you see or what Claude Code does.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}