{"version":"2.1.295","anchor":"prompt-hook-check-gains-an-installed-mode","canonical_anchor":"prompt-hook-check-gains-an-installed-mode","heading":"The hook check when you send a prompt can now just ask whether hooks exist","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/prompt-hook-check-gains-an-installed-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### The hook check when you send a prompt can now just ask whether hooks exist\n\nThe hook check Claude Code runs when you press Enter can now test only whether any hooks are installed\n\n**Unclear.** It is not stated where the new \"installed\" check is used, or whether it changes when sending a prompt waits for hooks.\n\n**What**\n\nHooks are your own commands that Claude Code runs at set moments, including when you submit a prompt. When you press Enter, Claude Code reads your hooks before sending. That check now has two modes. The default works as before. A new \"installed\" mode only checks whether any hooks are set up at all.\n\n**Why**\n\nThis may change when sending a prompt has to wait for hooks to be read.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}