{"version":"2.1.283","anchor":"hooks-menu-lists-the-hook-type-as-metadata-instead-of-a-typ","canonical_anchor":"hooks-menu-lists-the-hook-type-as-metadata-instead-of-a-typ","heading":"Hook type shown as a separate detail in the hooks list","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/hooks-menu-lists-the-hook-type-as-metadata-instead-of-a-typ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Hook type shown as a separate detail in the hooks list\n\nEntries in the hooks list now show each hook's type as a separate detail instead of a [type] prefix on the label\n\n**Unclear.** It is inferred, not confirmed, that this list is the one opened by `\/hooks`.\n\n**What**\n\nA hook is a command or action you configure to run automatically at certain points in a Claude Code session. In the list of hooks, each entry used to begin with its type in square brackets, such as `[command]`. The type is now shown as a separate detail beside the entry, and the label itself no longer carries the prefix.\n\n**Why**\n\nThis only changes how the list looks. The hooks themselves behave as before.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}