{"version":"2.1.311","anchor":"prompt-type-hooks-accepted-in-settings-hook-parsing","canonical_anchor":"prompt-type-hooks-accepted-in-settings-hook-parsing","heading":"Settings can now hold prompt-type hooks as well as command hooks","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/prompt-type-hooks-accepted-in-settings-hook-parsing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Settings can now hold prompt-type hooks as well as command hooks\n\nClaude Code's hook settings reader now recognises prompt-type hooks, keeping their continue-on-block and status-message options\n\n**Unclear.** It is not established whether prompt-type hooks loaded this way actually run.\n\n**What**\n\nHooks are actions Claude Code runs automatically at set points, for example before a tool runs. When Claude Code reads hooks from your settings, it now checks first whether each one is a prompt-type hook. Before, it only recognised command hooks.\n\n- A prompt-type hook is recorded as `prompt` and keeps its `continue_on_block` and `status_message` options.\n\n- A hook whose `if` condition is not valid is dropped.\n\n- Anything that is not a prompt hook is read as a command hook, as before.\n\n**Why**\n\nThis may let prompt-type hooks be loaded from your settings file.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}