{"version":"2.1.265","anchor":"hook-registry-gains-commanddescribe-as-a-core-hook-event","canonical_anchor":"hook-registry-gains-commanddescribe-as-a-core-hook-event","heading":"Hook registry gains command.describe as a core hook event","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/hook-registry-gains-commanddescribe-as-a-core-hook-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Hook registry gains command.describe as a core hook event\n\nClaude Code adds a new internal hook event called command.describe\n\n**Unclear.** What functionality actually uses the new command.describe hook is not established by this finding.\n\n**What**\n\nClaude Code's internal hook system (the machinery that lets different parts of the app react to events) now includes a new core event named `command.describe`, alongside existing ones like `agent.offer`, `tool.describe`, `session.start`, and the `turn.start`\/`turn.step`\/`turn.complete` events.\n\n**Why**\n\nThis is internal plumbing rather than something a reader interacts with directly. It suggests Claude Code now has a defined point for describing commands, similar to how it already describes tools, but the finding doesn't say what consumes this event yet.\n\n- Area: Hooks\n- Names: `command.describe`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}