{"version":"2.1.286","anchor":"hooks-dialog-now-opens-on-a-flat-list-of-configured-hooks","canonical_anchor":"hooks-dialog-now-opens-on-a-flat-list-of-configured-hooks","heading":"The \/hooks menu now opens on a list of your hooks","tier":"use","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/hooks-dialog-now-opens-on-a-flat-list-of-configured-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### The \/hooks menu now opens on a list of your hooks\n\n`\/hooks` now opens on a list of every configured hook with its event, source, command and matcher, with the event list one step away\n\n**What**\n\nHooks are commands that run automatically at certain moments, such as when Claude uses a tool. The first screen of `\/hooks` is now a list of every hook you have, grouped under its event, showing:\n\n- where the hook comes from\n\n- the command it runs\n\n- its matcher, the rule that chooses which tools it applies to\n\nAn All events row opens the old list of events, now titled Hook events. Pressing Esc from a hook you opened from the list returns you to the list. When you have no hooks, the subtitle reads no hooks yet, or managed hooks only if your organization set them.\n\nBefore, `\/hooks` opened on the list of events with a count of hooks for each. The menu is still read-only: to add or change a hook, edit settings.json or ask Claude.\n\n**Why**\n\nYou see all your hooks at once instead of opening each event to find them.\n\n- Area: Hooks\n- Names: `\/hooks`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5"}