{"version":"2.1.292","anchor":"hook-registration-gains-an-istold-kind","canonical_anchor":"hook-registration-gains-an-istold-kind","heading":"Internal groundwork for a second kind of hook","tier":"soon","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/hook-registration-gains-an-istold-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Internal groundwork for a second kind of hook\n\nClaude Code's internal hook machinery now accepts a second kind of hook, labelled \"told\", that only wires up error handling\n\n**What**\n\nThe part of Claude Code that sets up certain internal hooks (pieces of code that run at set points while Claude Code works) now accepts a second kind. These are labelled \"told\" instead of \"hook\", and only their error-handling path is connected. Before, every hook was set up the same way.\n\n**Why**\n\nThis looks like preparation for a new kind of hook. It does not yet change anything you can configure.\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}