{"version":"2.1.295","anchor":"hooks-worker-plugin-api-notify-and-blamedwalk","canonical_anchor":"hooks-worker-plugin-api-notify-and-blamedwalk","heading":"Hook plugins gain a notify method","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/hooks-worker-plugin-api-notify-and-blamedwalk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Hook plugins gain a notify method\n\nThe context given to hook plugins now has a notify method that sends a message tagged with where the hook came from\n\n**Unclear.** It is not known whether plugin authors can call the new notify method.\n\n**What**\n\nHooks are scripts Claude Code runs automatically at certain points, and plugins can supply them. The context those plugins work with now has a `notify` method that sends a message tagged with the hook's origin. It reports that there is nowhere to show the message. The code that registers plugins also takes a new argument.\n\n**Why**\n\nThis widens what hook plugins can do.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}